← All stories
● Covered by 1 source · 1 reportMedium impact1 neutral

Qwik 2.0 RC Replaces HTML Comment Markers for Faster Reactivity and Out-of-Order Streaming

🔄 Updated 4d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Qwik 2.0 RC replaces HTML comment markers with script blocks for state encoding.
  • The change enables experimental out-of-order HTML streaming.
  • Qwik 2.0 shows significant performance improvements over v1 and other frameworks.
  • JavaScript required before interactivity dropped from 59KB to 9KB.

State Encoding Rewrite

Qwik 2.0 Release Candidate, published as @qwik.dev/core@2.0.0-rc.0, introduces a significant change in how the framework encodes resumable state in server-rendered HTML. Previously, Qwik v1 used HTML comment markers like <!--qv--> and <!--t=8--> to flag component boundaries and text nodes for signal updates. This method enforced a single ordered write pass, incurred CPU and memory overhead, and prevented out-of-order streaming.

New State Management Approach

In Qwik 2.0, these HTML comments are removed. Instead, state and virtual node information are compressed into two new script blocks: <script type="qwik/state"> and <script type="qwik/vnode">, placed at the end of the document. This new approach addresses the limitations of the previous method, allowing for more efficient state propagation.

Performance Improvements

Internal benchmarks show Qwik 2.0 performing faster than its predecessor and several other frameworks. On Qwik's internal js-framework-benchmark runs, v2 is 1.23 times slower than vanilla JavaScript, outperforming Vue 3.5 (1.25x), Angular 22 (1.42x), React 19 with compiler (1.53x), and Qwik v1 (2.59x). A detailed walkthrough indicated that server-rendered HTML went from 60 comments to zero, and JavaScript required before interactivity decreased from 59KB to 9KB, though total bundle size increased.

Experimental Out-of-Order Streaming

Qwik 2.0 introduces experimental out-of-order HTML streaming. Developers can use <Pending> and <Catch> boundaries to wrap slow regions, allowing the server to send the rest of the page immediately and stream the delayed content later within the same response. A small inline script then swaps the content into place. These APIs are opt-in via vite.config.ts using experimental flags like 'pendingBoundary' and 'catchBoundary'.

Additional Features and API Changes

Other updates in Qwik 2.0 include useComputed$ now accepting async functions, replacing <Resource>. Route loaders now have their own JSON endpoints with cacheControl and eTag options for individual browser caching, and <Link> can prefetch data on hover. New primitives like worker$ for Web Workers and reactify$ for embedding Qwik components in React trees are also included. The release also adds server-only *.server.ts files and HMR that preserves signal and store values across edits.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Qwik, a JavaScript framework, released its 2.0 Release Candidate, rewriting how it encodes resumable state in server-rendered HTML by replacing HTML comment markers with script blocks. This change improves performance, enables experimental out-of-order streaming, and reduces JavaScript required for interactivity.