what stackpulse tracks
Qwik releases from GitHub
StackPulse watches Qwik release notes and keeps the original source link close to every summary.
#stacks/
loading releases…
releases
breaking
security
deprecated
migrations
Instant-loading web apps without effort StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches Qwik release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This release introduces significant improvements to client resume responsiveness, deprecates `useAsync$` in favor of `useComputed$`, and adds an experimental `Show` control-flow component. It also includes numerous bug fixes and optimizations for SSR and state handling.
Developers using `useAsync$`, `createAsync$`, or `AsyncSignal` will need to migrate to `useComputed$`.
Migrate from `useAsync$`, `createAsync$`, and `AsyncSignal` to `useComputed$`.
This release introduces significant breaking changes to the router, including layout rendering for 404 and error pages, opt-in SPA view transitions, and asset relocation. It also adds new features like configurable server request body limits and improved route loader behavior.
Developers using Qwik's router and SSG features are affected by breaking changes and new configurations.
Review breaking changes and update your codebase accordingly, especially for 404 pages and SPA view transitions.
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.
Developers using Qwik Router and route loaders will need to update their code to accommodate the breaking changes.
Review the breaking changes and update your route loaders and caching strategies accordingly.