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 changes to error handling with `<ErrorBoundary>`, now part of `@qwik.dev/core` behind an experimental flag. It also includes improvements to error reporting and handling in production, along with fixes for error serialization and suspense fallback behavior.
Developers using `<ErrorBoundary>` or `useErrorBoundary()` are affected by these changes.
Update your code to use the new `<ErrorBoundary>` implementation and remove any references to `useErrorBoundary()`.
This release introduces significant changes to error handling with the `<ErrorBoundary>` component moving to `@qwik.dev/core` and updates to `renderToStream` for pre-flush error reporting. Additionally, `Cache-Control: no-store` is now sent for error documents.
Developers using `useErrorBoundary()` or relying on the previous `<ErrorBoundary>` implementation are affected.
Update your code to use the new `<ErrorBoundary>` implementation from `@qwik.dev/core` and remove any references to `useErrorBoundary()`.