@playstack/errors-react

@playstack/errors-react connects an application-owned @playstack/errors reporter to React component trees.

Install

npm install @playstack/core @playstack/errors @playstack/errors-react react

Compose it at the React root

import { ErrorsBoundary, ErrorsProvider } from '@playstack/errors-react'

export function ApplicationRoot() {
  return (
    <ErrorsProvider errors={errors}>
      <ErrorsBoundary
        fallback={({ error, reset }) => (
          <ErrorScreen error={error} onRetry={reset} />
        )}
        resetKey={router.location.key}
        development={import.meta.env.DEV}
        captureOptions={{ tags: { boundary: 'application-root' } }}
        onReset={() => queryClient.clear()}
      >
        <App />
      </ErrorsBoundary>
    </ErrorsProvider>
  )
}

useErrors() returns the exact reporter supplied to the closest provider, so event handlers and effects use the same capture policy as render boundaries.

Provider properties

Boundary properties

Observer failures cannot replace the original render error or strand the fallback. A manual reset() and a resetKey change use the same recovery path.

Bridge boundary

This adapter has no separate persistence or transport bridge. Its only outside-in dependency is the ErrorReporter passed to ErrorsProvider; the fallback and reset behavior remain application components and callbacks.

The package does not configure drivers, initialize vendor SDKs, read ambient environment variables, or import a router. React 18 or 19 and all @playstack/* peers stay application-owned at the same fixed version.

API entry points and requirements

Reference snapshot: @playstack/errors-react@0.1.0-beta.1. Import only the entry point your runtime needs. Paths below are relative to the installed package; use Go to Definition in your editor to inspect exact parameters, return types and overloads. Do not import the declaration-file paths directly.

Node.js engine requirement: >=20. This is not a claim that every entry point works in browsers or Workers.

Peer dependencies

Keep existing framework versions that satisfy these ranges. Install optional peers only when using the corresponding adapter. The package manager resolves ordinary dependencies separately.

For a complete first program, start with Getting started. For API lookup and partial-example conventions, see Reading the reference. Provider failures, lifecycle requirements and application responsibilities remain described in the guide above; types alone do not establish production safety.