Change8

@qwik.dev/core@2.0.0-beta.42

Breaking Changes
📦 qwikView on GitHub →
1 breaking2 features🐛 3 fixes🔧 4 symbols

Summary

The `<ErrorBoundary>` component has been moved and is now experimental. Error handling in streaming renders has been improved, and server-origin errors are now redacted in production.

⚠️ Breaking Changes

  • `<ErrorBoundary>` has moved to `@qwik.dev/core` and is now behind the experimental `errorBoundary` flag. The `useErrorBoundary()` hook has been removed.

Migration Steps

  1. Enable the experimental `errorBoundary` flag to use the new `<ErrorBoundary>` component.
  2. Remove usages of the removed `useErrorBoundary()` hook.

✨ New Features

  • `renderToStream` now reports a pre-flush `<ErrorBoundary>` catch via `onBeforeFirstFlush`.
  • The router now sends `Cache-Control: no-store` for pages with pre-flush error boundaries and for error documents.

🐛 Bug Fixes

  • Server-origin errors are now redacted when serializing errored async signals in production.
  • The `Suspense` fallback is now shown when a suspending child is wrapped in an `ErrorBoundary`.
  • A failed handler chunk import is no longer reported twice for streamed containers.

Affected Symbols