●Change8

Migrating to Qwik @qwik.dev/router@2.0.0-beta.29

Version @qwik.dev/router@2.0.0-beta.29 introduces 1 breaking change. This guide details how to update your code.

Released: 3/15/2026

1
Breaking Changes
3
Migration Steps
7
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

route configuration objectheadeTagcacheKeyrouteConfigclearSsrCacheuseHttpStatus

Breaking Changes

●Issue #1

The route configuration object structure has changed, moving to a trie structure and removing the `menus` property. This change is stated not to impact users, but configuration handling might need review if relying on the old structure.

Migration Steps

  1. 1
    If you were relying on the structure of the route configuration object, review changes related to the removal of `menus` and the new trie structure.
  2. 2
    Consider migrating page-level configurations (`head`, `eTag`, `cacheKey`) to the unified `routeConfig` export.
  3. 3
    If using custom error handling, note that `404.tsx` is now visible in dev mode, and you can define status-specific error pages.

Release Summary

This release introduces significant performance improvements via in-memory SSR caching and eTag support, alongside a major refactoring of route configuration structure. It also enhances custom error page handling.

Need More Details?

View the full release notes and all changes for Qwik @qwik.dev/router@2.0.0-beta.29.

View Full Changelog