The Qwik team has released version 2.0 Release Candidate of the resumable JavaScript framework, replacing the HTML comment markers used in v1 for state propagation with compressed script blocks and introducing experimental out-of-order HTML streaming.
In version 1, Qwik embedded comment markers like throughout HTML to flag component boundaries and track which text nodes a signal should update. This approach forced a single ordered write pass and made out-of-order streaming impossible, as a slow fetch would block everything after it. The new version eliminates these comments, instead compressing state and virtual node information into two script blocks at the end of the document.
Qwik is an open-source framework that serialises application state and event listeners into HTML, then lazily loads JavaScript only in response to user interaction. Originally created at Builder.io, it is developed under the MIT license.
On Qwik's internal runs of the js-framework-benchmark, Qwik 2.0 RC posts a weighted geometric mean of 1.23 times slower than vanilla JavaScript, ahead of Vue 3.5 at 1.25 times, Angular 22 at 1.42 times, React 19 with the compiler at 1.53 times, and version 1 itself at 2.59 times. A detailed Classmethod walkthrough by Hiroshi Morishige reported that the server-rendered HTML went from 60 comments to zero, and the JavaScript required before interactivity fell from 59KB to 9KB, although the total bundle size grew.
The new experimental out-of-order streaming allows developers to wrap slow regions in Pending and Catch boundaries. The server sends the rest of the page immediately and streams the real content later in the same response, with a small inline script to swap it into place. The feature is opt-in through configuration.
Other additions include support for async functions in useComputed$, route loaders with their own JSON endpoints and caching options, a worker$ primitive for Web Workers, and reactify$ for embedding Qwik components inside React trees. The team says breaking changes are small and automated by a migration command.
Morishige noted the long wait for v2. In a Reddit discussion predating the RC, one developer described the lack of out-of-order streaming as a significant limitation and argued the team should be more upfront about it. Another commenter suggested that streaming could be added as a future feature. Morishige noted that v2 reached alpha in November 2024 and beta in June 2025, while v1 continued to receive updates through version 1.20.1 in September 2026. He also observed that SvelteKit 3 and Remix 3.0 released stable versions on the same day as the Qwik RC, with the three releases coming within seven hours.
Analysis
Why This Matters
- For developers using Qwik, the 2.0 RC promises faster initial loads and reduced JavaScript overhead, with outsized gains in benchmark comparisons against Vue, Angular, and React.
- The introduction of out-of-order streaming, while experimental, addresses a key limitation cited by the community and could make Qwik more competitive for content-heavy sites.
- The surrounding discussion highlights the tension between rapid iteration and managing developer expectations during a long-running early-access cycle.
Background
Qwik is a resumable JavaScript framework that serialises application state and event listeners into HTML, allowing components to load JavaScript lazily only when the user interacts. Version 1 encoded state updates using HTML comment markers throughout the page body, which led to CPU and memory overhead and prevented out-of-order streaming. The project has been steadily developed since its initial design article for version 2 about two years and eight months ago.
Key Perspectives
Qwik team: Says the breaking changes are small and automated, and emphasises the performance gains from the new state-encoding approach.
Reddit developer (anonymous): Described the absence of out-of-order streaming in v1 as a significant limitation and argued the team should have been more forthcoming about the limitation.
Another Reddit commenter: Suggested that streaming could be added as a future feature, which v2 now includes experimentally.
Developer Hiroshi Morishige: Noted the long wait for v2, with alpha in November 2024 and beta in June 2025, and pointed out that v1 continued to receive updates through September 2026. He also observed that SvelteKit 3 and Remix 3.0 released stable versions on the same day as the Qwik RC.
What to Watch
- The timeline for a stable Qwik 2.0 release, as the RC period begins.
- How developers adopt the out-of-order streaming feature in production, and whether it proves stable and performant.
- The impact of Qwik 2.0 on the broader JavaScript framework landscape, particularly against established players like React, Vue, and Angular.
Checked
12 claims in this story checked against 1 source: 12 supported.
Show each claim
- SupportedQwik 2.0 RC overhauls state encoding and adds experimental out-of-order streaming.InfoQ: “Qwik, the resumable JavaScript framework originally created at Builder.io, has released its 2.0 Release Candidate, targeting a rewrite of how the framework encodes resumable state in server-rendered HTML and introducing experimental out-of-order streaming.”
- SupportedA walkthrough reports that server-rendered HTML went from 60 comments to zero.InfoQ: “A detailed classmethod walkthrough that built the same starter against both versions reported server-rendered HTML went from 60 comments to zero”
- SupportedThe walkthrough reports JavaScript required before interactivity falling from 59KB to 9KB.InfoQ: “with JavaScript required before interactivity dropping from 59KB to 9KB, though total bundle size grew.”
- SupportedQwik 2.0 outperforms v1 in benchmark runs.InfoQ: “On Qwik's internal runs of js-framework-benchmark, v2 posts a weighted geometric mean of 1.23 times slower than vanilla JavaScript, ahead of Vue 3.5 at 1.25x, Angular 22 at 1.42x, React 19 with the compiler at 1.53x, and v1 itself at 2.59x.”
- SupportedThe Qwik team has released version 2.0 Release Candidate.InfoQ: “Qwik, the resumable JavaScript framework originally created at Builder.io, has released its 2.0 Release Candidate”
- SupportedIn v1, Qwik used HTML comment markers to flag component boundaries and text nodes a signal should update.InfoQ: “In v1, Qwik propagated state updates by sprinkling HTML comment markers such as !--qv-- and !--t=8-- throughout the rendered body to flag component boundaries and the text nodes a signal should update.”
- SupportedThe v1 approach forced a single ordered write pass and made out-of-order streaming impossible because a slow fetch blocked everything after it.InfoQ: “That approach forced a single ordered write pass, added CPU and memory overhead, and made out-of-order streaming impossible because a slow fetch blocked everything after it.”
- SupportedIn v2, state and virtual node information is compressed into two script blocks at the end of the document, replacing the comments.InfoQ: “In v2 the comments are gone, with state and virtual node information instead compressed into two script type="qwik/state" and script type="qwik/vnode" blocks at the end of the document.”
- SupportedQwik is an open-source framework that serialises state and event listeners into HTML, then lazily loads component JavaScript in response to user interaction.InfoQ: “Qwik is an open-source resumable framework that serialises state and event listeners into HTML, then lazily loads component JavaScript only in response to user interaction.”
- SupportedQwik was originally created at Builder.io and is MIT licensed.InfoQ: “Qwik, the resumable JavaScript framework originally created at Builder.io”
- SupportedOut-of-order streaming lets developers wrap slow regions in Pending and Catch boundaries; the server sends the rest of the page immediately and streams the real content later in the same response, using a small inline script to swap it into place.InfoQ: “Developers can wrap slow regions in Pending and Catch boundaries so the server sends the rest of the page immediately and streams the real content later in the same response, with a small inline script swapping it into place.”
- SupportedThe streaming APIs are opt-in through configuration.InfoQ: “The APIs are opt-in through vite.config.ts : qwikVite({ experimental: ['pendingBoundary', 'catchBoundary', 'blockSSR'] })”