Today we are excited to announce Qwik v1 Release Candidate! This is a major milestone for our team, and we are grateful for the support of our community.
This removes a lot of manual performance optimizations needed in other frameworks, which leads to a much better developer experience. Speaking of DX, Qwik is designed to be familiar, minimal, and straightforward to use. That’s why it uses the well-known JSX syntax, functional components with hooks API style, and is reactive by utilizing signals.
RC (Release Candidate) means that:
- The API is feature complete.We’ve reached all the goals we set out for building applications with Qwik. There are no plans to add or change any more APIs or features before v1.
- We are not aware of any significant issues which would keep you from succeeding in building amazingly performant production web apps and websites with it.
- We need your feedback: RC is a period where we want even more feedback from the community to iron out any surprises that would keep v1 from being stable and provide a delightful developer experience.
Qwik (and Qwik City) are packed with many cool features, but here are some that we are incredibly proud of and would like to highlight.
- Performance at scale: Qwik applications stay performant even as their complexity grows over time. Sure, any hello-world app, with little to no interactivity, can be fast, but as features are added, Qwik retains consistent startup performance through resumability. and it does that - automatically!
- Edge first + middleware: Qwik adapters bring Qwik to all major edge providers in a deployment-agnostic way. No lock-in here. Easily deploy the same application with many providers.
- Directory-based routing: Qwik City is designed with convention-based routing. File-based routing is a familiar feature in today's meta-frameworks. Qwik extends file-based routing with an easy way to compose middleware.
- Ecosystem: our awesome community members have already created many integrations with popular tools like Storybook, Cypress, nx, auth.js, vitest, vanilla-extract, and there is also a native and accessible UI component library soon to be released (qwik-ui). We are adding more integrations in the next couple of months — yep, things are moving qwikly! ;)
- Qwik-react: it is possible to use React inside a qwik application, but without the cost of hydration. This could bridge the gap for developers coming from the React ecosystem and save time by directly importing React components into a Qwik application (Qwik-angular and Qwik-vue are in the works as well! 🤩).
Between now and the v1 release, we will focus on polishing, paying special attention to the documentation, and getting started. And, of course, we’ll fixing any surprise bugs which may come up.
Special thanks to the awesome Qwik community for helping us test Qwik during its development. Qwik has gone through growing pains; however, our lovely community members were able to provide us with useful feedback to make it better. It is because of you that Qwik is where it is today.
We would LOVE to hear what you think. Please share it with us on our discord channel — and if you’re not part of it, come and experience first-hand how amazing and friendly our Qwik community members are.