what stackpulse tracks
Qwik releases from GitHub
StackPulse watches Qwik release notes and keeps the original source link close to every summary.
#stacks/qwik/framework
Qwik release notes, breaking changes, and upgrade notes.
Instant-loading web apps without effort StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
releases
5
breaking
1
security
0
deprecated
0
migrations
1
upgrade risk
Breaking changes and deprecations
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Source-backed next steps
Migration steps and recommended actions are only shown when the upstream release notes support them.
# latest_releases
source-backed@qwik.dev/router@2.0.0-beta.37highbreakingmigrationfeatureprereleaseJun 9, 2026
@qwik.dev/router@2.0.0-beta.37
This release introduces significant breaking changes to route loaders, including the transition to AsyncSignals and changes to caching behavior. New features include support for `eTag`, `cacheKey`, and `search` parameters in route loaders.
affected
Developers using Qwik Router and route loaders will need to update their code to accommodate the breaking changes.
action
Review the breaking changes and update your route loaders and caching strategies accordingly.
release_signals
-Route loaders are now AsyncSignals, and `value.failed` is no longer used to indicate a loader failure.
-`routeLoader$` cannot read action state any more, so that they are cacheable and predictable.
-Qwik Router no longer retrieves `q-data.json` files on every SPA navigation.
-`cacheKey` functions now get `(requestEv: RequestEvent, eTag: string)` as arguments, instead of `(status: number, eTag: string, pathname: string)`.
+Route loaders now accept `eTag` to shortcut data retrieval when the data has not changed.
+Route loaders support a `cacheKey` and `eTag` property, similar to SSR `pageConfig`.
+Route loaders accept `search` to only allow certain query parameters to trigger the loader.
+Route loaders now redirect in their JSON response instead of using HTTP redirect.
+Expose `RequestEvent.internalRequest` for framework-internal JSON requests.
migration_steps3 steps
- 01Update route loaders to use AsyncSignals and handle errors via `error` instead of `value.failed`.
- 02Remove caching rules for `q-data.json` files and adapt to the new `q-loader-${hash}.${manifestHash}.json` format.
- 03Update `cacheKey` functions to accept `(requestEv: RequestEvent, eTag: string)` arguments.