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. The RC was published on 1st October 2026 as @qwik.dev/core@2.0.0-rc.0, around two years and eight months after the initial Towards Qwik 2.0 design article.
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. 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. 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.
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. A detailed classmethod walkthrough that built the same starter against both versions reported server-rendered HTML went from 60 comments to zero, with JavaScript required before interactivity dropping from 59KB to 9KB, though total bundle size grew.
Out-of-order HTML streaming has also been added n experimental mode. 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. The APIs are opt-in through vite.config.ts:
qwikVite({ experimental: ['pendingBoundary', 'catchBoundary', 'blockSSR'] })
useComputed$ now accepts async functions, replacing <Resource>, and route loaders gain their own JSON endpoints with cacheControl and eTag options so the browser can cache them individually and <Link> can prefetch data on hover. Other additions include a worker$ primitive for Web Workers, reactify$ for embedding Qwik components inside React trees, server-only *.server.ts files, and HMR that preserves signal and store values across edits.
In a Reddit discussion predating the v2 RC, one developer called the lack of out-of-order streaming a significant limitation and argued that the Qwik team should be more upfront about it. Another commenter suggested that streaming could be a future feature. In his Classmethod walkthrough, Hiroshi Morishige noted the long wait for v2, it reached alpha in November 2024 and beta in June 2025, while v1 continued to receive updates through 1.20.1 in September 2026. He also noted that SvelteKit 3 and Remix 3.0 released stable versions on the same day as Qwik's RC, with the three releases published within seven hours. Qwik 2 and SvelteKit 3 use Vite 8; Remix 3 is independent of Vite.
The team says the breaking changes are small and automated by pnpm qwik migrate-v2, which also handles the move to the new @qwik.dev/core and @qwik.dev/router package names. New projects can scaffold with pnpm create qwik@rc, and the RC can be explored via next.qwik.dev/examples or the online playground.
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. The project is MIT licensed and developed openly on GitHub.