Overview
Qwik is a web framework centered on resumability: the browser continues from state produced on the server instead of eagerly re-executing the whole application. Interaction code is split so that only the pieces needed by the user are loaded on demand.
Features and best fit
Based on official documentation; not hands-on tested · Content checked:
Resume instead of hydrating the entire application
Qwik preserves server execution state so the browser can continue from that point while reducing the amount of application work performed during startup.
Load interaction code when it becomes necessary
Precision lazy loading breaks behavior into small units and prioritizes the code needed for the user's current interaction.
For applications where startup JavaScript is a key performance concern
It is a candidate for sites and applications that want to limit initial JavaScript execution even as content and interactive features grow.
Sources: [2]
Main is Qwik v2 beta, separate from the v1 branch
The current main branch is v2 beta and the README points v1 users to the v1 branch. Do not apply beta APIs and documentation directly to an existing v1 project.
Official sources
- [1]QwikDev/qwik repository(2026-09-21)
- [2]Qwik README(2026-09-21)
- [3]Qwik resumability concept(2026-09-21)
- [4]Qwik progressive loading concept(2026-09-21)
- [5]@qwik.dev/core package(2026-09-21)
- [6]Qwik MIT license(2026-09-21)
Supplemental curator note
As of September 21, 2026, main is the Qwik v2 beta line and `@qwik.dev/core` is 2.0.0-beta.43. The README directs v1 users to the `v1` branch. Decide which line you are evaluating before adopting examples or documentation so v1 and v2 beta guidance are not mixed.
Try it in 3 steps
- 1
Create a Qwik v2 beta project
This follows the current main README for Qwik v2 beta. Use the v1 branch and matching documentation when evaluating the v1 line.
npm create qwik@beta - 2
Enter the generated project
Change into the project directory selected during the scaffold prompts.
cd <project-directory> - 3
Start the development server
Run the local application and inspect the development workflow built around resumability and on-demand code loading.
npm start
Growth
Growth trends · Last 30 days
22,070 Stars
Trend data is still being collected.
Development activity
Last 90 days · weekly
- Commits (last 30 days)
- 259
- Open PRs
- 37
Development activity is still being collected.
Built with
Categories and tags
Categories
GitHub data
GitHub dataView detailed GitHub data
GitHub Topics
- javascript
- web
- framework
- hacktoberfest
- Stars
- 22,070
- Forks
- 1,402
- Watchers
- 131
- Open issues
- 85
- Contributors
- 433
- Primary language
- TypeScript
- License
- MIT
- Repository last updated
- Sep 20, 2026
Related information
Write a related articleShare a guide or use case for this OSS in Markdown. Articles are published after administrator approval.
Explore next
- Nuxt60,885 Stars
3 shared tag(s) · 1 shared category(s) · Same language
A Vue framework for websites and full-stack applications using SSR, SSG, and hybrid rendering.
TypeScript - Docusaurus66,308 Stars
3 shared tag(s) · Same language
A React-based static-site foundation for documentation, blogs, custom pages, and localization.
TypeScript - Angular101,020 Stars
2 shared tag(s) · 2 shared category(s) · Same language
A TypeScript-first web application platform integrating components, DI, routing, forms, SSR, and CLI tooling.
TypeScript - Vue 2212,485 Stars
2 shared tag(s) · 1 shared category(s) · Same language
The legacy Vue repository, EOL since the end of 2023 and directing users to Vue 3.
TypeScript - Astro62,723 Stars
2 shared tag(s) · 1 shared category(s) · Same language
A framework for content-driven websites with lightweight output and optional UI integrations.
TypeScript
Report incorrect information
Tell us if any listing information is incorrect or outdated.