@rshono/core 1.0.0-rc.4 → 1.0.0-rc.5

package/dist/index.d.ts

@@ -8,7 +8,7 @@
  *   server components and actions (`getRequestContext`, `redirect`, `notFound`), plus
  *   `onServerError` for reporting the errors the framework catches.
  * - `@rshono/core/client` — hooks and components for `'use client'` modules
- *   (`useNavigation`, `Boundary`, `ErrorBoundary`).
+ *   (`useNavigation`, `AsyncBoundary`, `CatchBoundary`).
  *
  * @packageDocumentation
  */

package/dist/index.js

@@ -8,7 +8,7 @@
  *   server components and actions (`getRequestContext`, `redirect`, `notFound`), plus
  *   `onServerError` for reporting the errors the framework catches.
  * - `@rshono/core/client` — hooks and components for `'use client'` modules
- *   (`useNavigation`, `Boundary`, `ErrorBoundary`).
+ *   (`useNavigation`, `AsyncBoundary`, `CatchBoundary`).
  *
  * @packageDocumentation
  */

package/dist/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AAEH,OAAO,EACL,YAAY,GAab,MAAM,aAAa,CAAC;AAErB,OAAO,EAAE,YAAY,EAA6C,MAAM,aAAa,CAAC;AAItF,kGAAkG;AAClG,sGAAsG;AACtG,mGAAmG","sourcesContent":["/**\n * `@rshono/core` — the build-time surface: route and config declaration plus the types\n * your pages and endpoints are written against. Everything here is safe to\n * import from server code; none of it pulls in runtime machinery.\n *\n * The two companion entry points are runtime-only:\n * - `@rshono/core/server` — {@link https://hono.dev | Hono} request context inside\n *   server components and actions (`getRequestContext`, `redirect`, `notFound`), plus\n *   `onServerError` for reporting the errors the framework catches.\n * - `@rshono/core/client` — hooks and components for `'use client'` modules\n *   (`useNavigation`, `Boundary`, `ErrorBoundary`).\n *\n * @packageDocumentation\n */\n\nexport {\n  defineRoutes,\n  type EndpointRoute,\n  type EndpointServerModule,\n  type ErrorPageInfo,\n  type ErrorPageProps,\n  type FallbackPage,\n  type HTTPMethod,\n  type PageComponent,\n  type PageProps,\n  type PageRoute,\n  type PathParams,\n  type Route,\n  type RouteConfig,\n} from './router.js';\n\nexport { defineConfig, type RshonoConfig, type RspackHookContext } from './config.js';\n\nexport type { DeployTarget } from './deploy/contract.js';\n\n// Hono's own `Context` and `Handler` used to be re-exported from here \"for convenience\". They are\n// Hono's types, `hono` is a peer dependency every app already has, and importing them from two places\n// only raised the question of which one is right — so an endpoint module imports them from `hono`.\n"]}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AAEH,OAAO,EACL,YAAY,GAab,MAAM,aAAa,CAAC;AAErB,OAAO,EAAE,YAAY,EAA6C,MAAM,aAAa,CAAC;AAItF,kGAAkG;AAClG,sGAAsG;AACtG,mGAAmG","sourcesContent":["/**\n * `@rshono/core` — the build-time surface: route and config declaration plus the types\n * your pages and endpoints are written against. Everything here is safe to\n * import from server code; none of it pulls in runtime machinery.\n *\n * The two companion entry points are runtime-only:\n * - `@rshono/core/server` — {@link https://hono.dev | Hono} request context inside\n *   server components and actions (`getRequestContext`, `redirect`, `notFound`), plus\n *   `onServerError` for reporting the errors the framework catches.\n * - `@rshono/core/client` — hooks and components for `'use client'` modules\n *   (`useNavigation`, `AsyncBoundary`, `CatchBoundary`).\n *\n * @packageDocumentation\n */\n\nexport {\n  defineRoutes,\n  type EndpointRoute,\n  type EndpointServerModule,\n  type ErrorPageInfo,\n  type ErrorPageProps,\n  type FallbackPage,\n  type HTTPMethod,\n  type PageComponent,\n  type PageProps,\n  type PageRoute,\n  type PathParams,\n  type Route,\n  type RouteConfig,\n} from './router.js';\n\nexport { defineConfig, type RshonoConfig, type RspackHookContext } from './config.js';\n\nexport type { DeployTarget } from './deploy/contract.js';\n\n// Hono's own `Context` and `Handler` used to be re-exported from here \"for convenience\". They are\n// Hono's types, `hono` is a peer dependency every app already has, and importing them from two places\n// only raised the question of which one is right — so an endpoint module imports them from `hono`.\n"]}

package/dist/runtime/boundaries.d.ts

@@ -1,6 +1,6 @@
 import { Component, type ReactNode } from 'react';
 /**
- * What an {@link ErrorBoundary} / {@link Boundary} renders once a child throws.
+ * What a {@link CatchBoundary} / {@link AsyncBoundary} renders once a child throws.
  * Either a static node, or a render function that also gets a `reset` callback
  * to clear the error and re-render the children (e.g. a "Try again" button).
  *
@@ -9,7 +9,7 @@ import { Component, type ReactNode } from 'react';
  * server component, pass a `ReactNode`.
  */
 export type ErrorFallback = ReactNode | ((error: Error, reset: () => void) => ReactNode);
-export interface ErrorBoundaryProps {
+export interface CatchBoundaryProps {
     /**
      * Rendered in place of the children after one of them throws. Omit it to
      * report the error via `onError` and re-throw to the next boundary out (or
@@ -26,7 +26,7 @@ export interface ErrorBoundaryProps {
     resetKeys?: readonly unknown[];
     children: ReactNode;
 }
-interface ErrorBoundaryState {
+interface CatchBoundaryState {
     error: Error | null;
 }
 /**
@@ -36,39 +36,44 @@ interface ErrorBoundaryState {
  * tearing down the whole page.
  *
  * It's a `'use client'` component (React error boundaries must be), so drop it
- * anywhere in the tree from a server or client component. Use {@link Boundary}
+ * anywhere in the tree from a server or client component. Use {@link AsyncBoundary}
  * when you also want a Suspense loading fallback in the same wrapper.
  *
  * @example
  * ```tsx
- * import { ErrorBoundary } from '@rshono/core/client';
+ * import { CatchBoundary } from '@rshono/core/client';
  *
- * <ErrorBoundary fallback={(error, reset) => (
+ * <CatchBoundary fallback={(error, reset) => (
  *   <div role="alert">
  *     <p>{error.message}</p>
  *     <button onClick={reset}>Try again</button>
  *   </div>
  * )}>
  *   <RiskyWidget />
- * </ErrorBoundary>
+ * </CatchBoundary>
  * ```
  */
-export declare class ErrorBoundary extends Component<ErrorBoundaryProps, ErrorBoundaryState> {
-    state: ErrorBoundaryState;
-    static getDerivedStateFromError(error: Error): ErrorBoundaryState;
+export declare class CatchBoundary extends Component<CatchBoundaryProps, CatchBoundaryState> {
+    state: CatchBoundaryState;
+    static getDerivedStateFromError(error: Error): CatchBoundaryState;
     componentDidCatch(error: Error): void;
-    componentDidUpdate(prev: ErrorBoundaryProps): void;
+    componentDidUpdate(prev: CatchBoundaryProps): void;
     reset: () => void;
     render(): ReactNode;
 }
-export interface BoundaryProps {
-    /** Suspense fallback, shown while the children (or their data) are still loading. */
-    loading?: ReactNode;
+export interface AsyncBoundaryProps {
+    /**
+     * Suspense fallback, shown while the children (or their data) are still
+     * loading. Required — a loading state is the reason to reach for this over
+     * {@link CatchBoundary}, so showing nothing is an explicit `loading={null}`
+     * rather than something you get by leaving the prop off.
+     */
+    loading: ReactNode;
     /** Error fallback, shown if a child throws. See {@link ErrorFallback}. */
     error?: ErrorFallback;
     /** Called with the caught error. */
     onError?: (error: Error) => void;
-    /** Clears the error fallback when any value changes — see {@link ErrorBoundaryProps.resetKeys}. */
+    /** Clears the error fallback when any value changes — see {@link CatchBoundaryProps.resetKeys}. */
     resetKeys?: readonly unknown[];
     children: ReactNode;
 }
@@ -77,26 +82,25 @@ export interface BoundaryProps {
  * section of a page. It always renders the same shape:
  *
  * ```tsx
- * <ErrorBoundary fallback={error}>
+ * <CatchBoundary fallback={error}>
  *   <Suspense fallback={loading}>{children}</Suspense>
- * </ErrorBoundary>
+ * </CatchBoundary>
  * ```
  *
  * so `error` catches anything the children throw (including while suspended) and
- * `loading` shows until they resolve. Both fallbacks are optional: omit
- * `loading` and nothing shows while loading; omit `error` and thrown errors
- * propagate to the next boundary out (or the global error page) rather than
- * being caught here.
+ * `loading` shows until they resolve. `error` is optional: omit it and thrown
+ * errors propagate to the next boundary out (or the global error page) rather
+ * than being caught here.
  *
  * @example
  * ```tsx
- * import { Boundary } from '@rshono/core/client';
+ * import { AsyncBoundary } from '@rshono/core/client';
  *
- * <Boundary loading={<Spinner />} error={(e, reset) => <Retry onClick={reset} />}>
+ * <AsyncBoundary loading={<Spinner />} error={(e, reset) => <Retry onClick={reset} />}>
  *   <SlowServerComponent />
- * </Boundary>
+ * </AsyncBoundary>
  * ```
  */
-export declare function Boundary({ loading, error, onError, resetKeys, children }: BoundaryProps): ReactNode;
+export declare function AsyncBoundary({ loading, error, onError, resetKeys, children }: AsyncBoundaryProps): ReactNode;
 export {};
 //# sourceMappingURL=boundaries.d.ts.map

package/dist/runtime/boundaries.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"boundaries.d.ts","sourceRoot":"","sources":["../../src/runtime/boundaries.tsx"],"names":[],"mappings":"AAEA,OAAO,EAAE,SAAS,EAAY,KAAK,SAAS,EAAE,MAAM,OAAO,CAAC;AAa5D;;;;;;;;GAQG;AACH,MAAM,MAAM,aAAa,GAAG,SAAS,GAAG,CAAC,CAAC,KAAK,EAAE,KAAK,EAAE,KAAK,EAAE,MAAM,IAAI,KAAK,SAAS,CAAC,CAAC;AAEzF,MAAM,WAAW,kBAAkB;IACjC;;;;OAIG;IACH,QAAQ,CAAC,EAAE,aAAa,CAAC;IACzB,8DAA8D;IAC9D,OAAO,CAAC,EAAE,CAAC,KAAK,EAAE,KAAK,KAAK,IAAI,CAAC;IACjC;;;;OAIG;IACH,SAAS,CAAC,EAAE,SAAS,OAAO,EAAE,CAAC;IAC/B,QAAQ,EAAE,SAAS,CAAC;CACrB;AAED,UAAU,kBAAkB;IAC1B,KAAK,EAAE,KAAK,GAAG,IAAI,CAAC;CACrB;AAMD;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,qBAAa,aAAc,SAAQ,SAAS,CAAC,kBAAkB,EAAE,kBAAkB,CAAC;IAClF,KAAK,EAAE,kBAAkB,CAAmB;IAE5C,MAAM,CAAC,wBAAwB,CAAC,KAAK,EAAE,KAAK,GAAG,kBAAkB,CAEhE;IAED,iBAAiB,CAAC,KAAK,EAAE,KAAK,GAAG,IAAI,CAGpC;IAED,kBAAkB,CAAC,IAAI,EAAE,kBAAkB,GAAG,IAAI,CAKjD;IAED,KAAK,QAAO,IAAI,CAEd;IAEF,MAAM,IAAI,SAAS,CASlB;CACF;AAED,MAAM,WAAW,aAAa;IAC5B,qFAAqF;IACrF,OAAO,CAAC,EAAE,SAAS,CAAC;IACpB,0EAA0E;IAC1E,KAAK,CAAC,EAAE,aAAa,CAAC;IACtB,oCAAoC;IACpC,OAAO,CAAC,EAAE,CAAC,KAAK,EAAE,KAAK,KAAK,IAAI,CAAC;IACjC,mGAAmG;IACnG,SAAS,CAAC,EAAE,SAAS,OAAO,EAAE,CAAC;IAC/B,QAAQ,EAAE,SAAS,CAAC;CACrB;AAED;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACH,wBAAgB,QAAQ,CAAC,EAAE,OAAc,EAAE,KAAK,EAAE,OAAO,EAAE,SAAS,EAAE,QAAQ,EAAE,EAAE,aAAa,GAAG,SAAS,CAM1G"}
+{"version":3,"file":"boundaries.d.ts","sourceRoot":"","sources":["../../src/runtime/boundaries.tsx"],"names":[],"mappings":"AAEA,OAAO,EAAE,SAAS,EAAY,KAAK,SAAS,EAAE,MAAM,OAAO,CAAC;AAa5D;;;;;;;;GAQG;AACH,MAAM,MAAM,aAAa,GAAG,SAAS,GAAG,CAAC,CAAC,KAAK,EAAE,KAAK,EAAE,KAAK,EAAE,MAAM,IAAI,KAAK,SAAS,CAAC,CAAC;AAEzF,MAAM,WAAW,kBAAkB;IACjC;;;;OAIG;IACH,QAAQ,CAAC,EAAE,aAAa,CAAC;IACzB,8DAA8D;IAC9D,OAAO,CAAC,EAAE,CAAC,KAAK,EAAE,KAAK,KAAK,IAAI,CAAC;IACjC;;;;OAIG;IACH,SAAS,CAAC,EAAE,SAAS,OAAO,EAAE,CAAC;IAC/B,QAAQ,EAAE,SAAS,CAAC;CACrB;AAED,UAAU,kBAAkB;IAC1B,KAAK,EAAE,KAAK,GAAG,IAAI,CAAC;CACrB;AAMD;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,qBAAa,aAAc,SAAQ,SAAS,CAAC,kBAAkB,EAAE,kBAAkB,CAAC;IAClF,KAAK,EAAE,kBAAkB,CAAmB;IAE5C,MAAM,CAAC,wBAAwB,CAAC,KAAK,EAAE,KAAK,GAAG,kBAAkB,CAEhE;IAED,iBAAiB,CAAC,KAAK,EAAE,KAAK,GAAG,IAAI,CAGpC;IAED,kBAAkB,CAAC,IAAI,EAAE,kBAAkB,GAAG,IAAI,CAKjD;IAED,KAAK,QAAO,IAAI,CAEd;IAEF,MAAM,IAAI,SAAS,CASlB;CACF;AAED,MAAM,WAAW,kBAAkB;IACjC;;;;;OAKG;IACH,OAAO,EAAE,SAAS,CAAC;IACnB,0EAA0E;IAC1E,KAAK,CAAC,EAAE,aAAa,CAAC;IACtB,oCAAoC;IACpC,OAAO,CAAC,EAAE,CAAC,KAAK,EAAE,KAAK,KAAK,IAAI,CAAC;IACjC,mGAAmG;IACnG,SAAS,CAAC,EAAE,SAAS,OAAO,EAAE,CAAC;IAC/B,QAAQ,EAAE,SAAS,CAAC;CACrB;AAED;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,wBAAgB,aAAa,CAAC,EAAE,OAAO,EAAE,KAAK,EAAE,OAAO,EAAE,SAAS,EAAE,QAAQ,EAAE,EAAE,kBAAkB,GAAG,SAAS,CAM7G"}

package/dist/runtime/boundaries.js

@@ -5,7 +5,7 @@ import { isControlDigest } from './control.js';
 /**
  * `redirect()` and `notFound()` reach the browser as a thrown error carrying a control digest.
  * They are navigation, not failure, so no boundary may absorb one — otherwise a `redirect()` from
- * a component inside a `<Boundary>` would render "something went wrong" instead of navigating.
+ * a component inside a `<CatchBoundary>` would render "something went wrong" instead of navigating.
  * They're re-thrown to the root, where the runtime turns the digest into a real navigation.
  */
 function isControlError(error) {
@@ -21,24 +21,24 @@ function keysChanged(a, b) {
  * tearing down the whole page.
  *
  * It's a `'use client'` component (React error boundaries must be), so drop it
- * anywhere in the tree from a server or client component. Use {@link Boundary}
+ * anywhere in the tree from a server or client component. Use {@link AsyncBoundary}
  * when you also want a Suspense loading fallback in the same wrapper.
  *
  * @example
  * ```tsx
- * import { ErrorBoundary } from '@rshono/core/client';
+ * import { CatchBoundary } from '@rshono/core/client';
  *
- * <ErrorBoundary fallback={(error, reset) => (
+ * <CatchBoundary fallback={(error, reset) => (
  *   <div role="alert">
  *     <p>{error.message}</p>
  *     <button onClick={reset}>Try again</button>
  *   </div>
  * )}>
  *   <RiskyWidget />
- * </ErrorBoundary>
+ * </CatchBoundary>
  * ```
  */
-export class ErrorBoundary extends Component {
+export class CatchBoundary extends Component {
     state = { error: null };
     static getDerivedStateFromError(error) {
         return { error };
@@ -75,27 +75,26 @@ export class ErrorBoundary extends Component {
  * section of a page. It always renders the same shape:
  *
  * ```tsx
- * <ErrorBoundary fallback={error}>
+ * <CatchBoundary fallback={error}>
  *   <Suspense fallback={loading}>{children}</Suspense>
- * </ErrorBoundary>
+ * </CatchBoundary>
  * ```
  *
  * so `error` catches anything the children throw (including while suspended) and
- * `loading` shows until they resolve. Both fallbacks are optional: omit
- * `loading` and nothing shows while loading; omit `error` and thrown errors
- * propagate to the next boundary out (or the global error page) rather than
- * being caught here.
+ * `loading` shows until they resolve. `error` is optional: omit it and thrown
+ * errors propagate to the next boundary out (or the global error page) rather
+ * than being caught here.
  *
  * @example
  * ```tsx
- * import { Boundary } from '@rshono/core/client';
+ * import { AsyncBoundary } from '@rshono/core/client';
  *
- * <Boundary loading={<Spinner />} error={(e, reset) => <Retry onClick={reset} />}>
+ * <AsyncBoundary loading={<Spinner />} error={(e, reset) => <Retry onClick={reset} />}>
  *   <SlowServerComponent />
- * </Boundary>
+ * </AsyncBoundary>
  * ```
  */
-export function Boundary({ loading = null, error, onError, resetKeys, children }) {
-    return (_jsx(ErrorBoundary, { fallback: error, onError: onError, resetKeys: resetKeys, children: _jsx(Suspense, { fallback: loading, children: children }) }));
+export function AsyncBoundary({ loading, error, onError, resetKeys, children }) {
+    return (_jsx(CatchBoundary, { fallback: error, onError: onError, resetKeys: resetKeys, children: _jsx(Suspense, { fallback: loading, children: children }) }));
 }
 //# sourceMappingURL=boundaries.js.map

package/dist/runtime/boundaries.js.map

@@ -1 +1 @@
-{"version":3,"file":"boundaries.js","sourceRoot":"","sources":["../../src/runtime/boundaries.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAC;;AAEb,OAAO,EAAE,SAAS,EAAE,QAAQ,EAAkB,MAAM,OAAO,CAAC;AAC5D,OAAO,EAAE,eAAe,EAAE,MAAM,cAAc,CAAC;AAE/C;;;;;GAKG;AACH,SAAS,cAAc,CAAC,KAAc;IACpC,OAAO,eAAe,CAAE,KAAqC,EAAE,MAAM,CAAC,CAAC;AACzE,CAAC;AAmCD,SAAS,WAAW,CAAC,CAAqB,EAAE,CAAqB;IAC/D,OAAO,CAAC,CAAC,MAAM,KAAK,CAAC,CAAC,MAAM,IAAI,CAAC,CAAC,IAAI,CAAC,CAAC,KAAK,EAAE,CAAC,EAAE,EAAE,CAAC,CAAC,MAAM,CAAC,EAAE,CAAC,KAAK,EAAE,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;AAChF,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,MAAM,OAAO,aAAc,SAAQ,SAAiD;IAClF,KAAK,GAAuB,EAAE,KAAK,EAAE,IAAI,EAAE,CAAC;IAE5C,MAAM,CAAC,wBAAwB,CAAC,KAAY;QAC1C,OAAO,EAAE,KAAK,EAAE,CAAC;IACnB,CAAC;IAED,iBAAiB,CAAC,KAAY;QAC5B,IAAI,cAAc,CAAC,KAAK,CAAC;YAAE,OAAO,CAAC,sCAAsC;QACzE,IAAI,CAAC,KAAK,CAAC,OAAO,EAAE,CAAC,KAAK,CAAC,CAAC;IAC9B,CAAC;IAED,kBAAkB,CAAC,IAAwB;QACzC,MAAM,EAAE,SAAS,EAAE,GAAG,IAAI,CAAC,KAAK,CAAC;QACjC,IAAI,IAAI,CAAC,KAAK,CAAC,KAAK,IAAI,IAAI,CAAC,SAAS,IAAI,SAAS,IAAI,WAAW,CAAC,IAAI,CAAC,SAAS,EAAE,SAAS,CAAC,EAAE,CAAC;YAC9F,IAAI,CAAC,KAAK,EAAE,CAAC;QACf,CAAC;IACH,CAAC;IAED,KAAK,GAAG,GAAS,EAAE;QACjB,IAAI,CAAC,QAAQ,CAAC,EAAE,KAAK,EAAE,IAAI,EAAE,CAAC,CAAC;IACjC,CAAC,CAAC;IAEF,MAAM;QACJ,MAAM,EAAE,KAAK,EAAE,GAAG,IAAI,CAAC,KAAK,CAAC;QAC7B,IAAI,KAAK,KAAK,IAAI,EAAE,CAAC;YACnB,IAAI,cAAc,CAAC,KAAK,CAAC;gBAAE,MAAM,KAAK,CAAC,CAAC,sDAAsD;YAC9F,MAAM,EAAE,QAAQ,EAAE,GAAG,IAAI,CAAC,KAAK,CAAC;YAChC,IAAI,QAAQ,KAAK,SAAS;gBAAE,MAAM,KAAK,CAAC,CAAC,qDAAqD;YAC9F,OAAO,OAAO,QAAQ,KAAK,UAAU,CAAC,CAAC,CAAC,QAAQ,CAAC,KAAK,EAAE,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,QAAQ,CAAC;QACjF,CAAC;QACD,OAAO,IAAI,CAAC,KAAK,CAAC,QAAQ,CAAC;IAC7B,CAAC;CACF;AAcD;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACH,MAAM,UAAU,QAAQ,CAAC,EAAE,OAAO,GAAG,IAAI,EAAE,KAAK,EAAE,OAAO,EAAE,SAAS,EAAE,QAAQ,EAAiB;IAC7F,OAAO,CACL,KAAC,aAAa,IAAC,QAAQ,EAAE,KAAK,EAAE,OAAO,EAAE,OAAO,EAAE,SAAS,EAAE,SAAS,YACpE,KAAC,QAAQ,IAAC,QAAQ,EAAE,OAAO,YAAG,QAAQ,GAAY,GACpC,CACjB,CAAC;AACJ,CAAC","sourcesContent":["'use client';\n\nimport { Component, Suspense, type ReactNode } from 'react';\nimport { isControlDigest } from './control.js';\n\n/**\n * `redirect()` and `notFound()` reach the browser as a thrown error carrying a control digest.\n * They are navigation, not failure, so no boundary may absorb one — otherwise a `redirect()` from\n * a component inside a `<Boundary>` would render \"something went wrong\" instead of navigating.\n * They're re-thrown to the root, where the runtime turns the digest into a real navigation.\n */\nfunction isControlError(error: unknown): boolean {\n  return isControlDigest((error as { digest?: unknown } | null)?.digest);\n}\n\n/**\n * What an {@link ErrorBoundary} / {@link Boundary} renders once a child throws.\n * Either a static node, or a render function that also gets a `reset` callback\n * to clear the error and re-render the children (e.g. a \"Try again\" button).\n *\n * The render-function form only works when the boundary is used from a `'use\n * client'` component — functions can't cross the server→client boundary. From a\n * server component, pass a `ReactNode`.\n */\nexport type ErrorFallback = ReactNode | ((error: Error, reset: () => void) => ReactNode);\n\nexport interface ErrorBoundaryProps {\n  /**\n   * Rendered in place of the children after one of them throws. Omit it to\n   * report the error via `onError` and re-throw to the next boundary out (or\n   * the global error page) instead of handling it here.\n   */\n  fallback?: ErrorFallback;\n  /** Called with the caught error (for logging / reporting). */\n  onError?: (error: Error) => void;\n  /**\n   * When any value in this array changes while the boundary is showing its\n   * fallback, the error is cleared automatically. Pass the current pathname to\n   * recover when the user navigates away: `resetKeys={[useNavigation().url.pathname]}`.\n   */\n  resetKeys?: readonly unknown[];\n  children: ReactNode;\n}\n\ninterface ErrorBoundaryState {\n  error: Error | null;\n}\n\nfunction keysChanged(a: readonly unknown[], b: readonly unknown[]): boolean {\n  return a.length !== b.length || a.some((value, i) => !Object.is(value, b[i]));\n}\n\n/**\n * A general-purpose error boundary. Catches errors thrown while rendering its\n * children — a client island that blew up, or a server component that rejected\n * on a soft navigation — and renders `fallback` in their place instead of\n * tearing down the whole page.\n *\n * It's a `'use client'` component (React error boundaries must be), so drop it\n * anywhere in the tree from a server or client component. Use {@link Boundary}\n * when you also want a Suspense loading fallback in the same wrapper.\n *\n * @example\n * ```tsx\n * import { ErrorBoundary } from '@rshono/core/client';\n *\n * <ErrorBoundary fallback={(error, reset) => (\n *   <div role=\"alert\">\n *     <p>{error.message}</p>\n *     <button onClick={reset}>Try again</button>\n *   </div>\n * )}>\n *   <RiskyWidget />\n * </ErrorBoundary>\n * ```\n */\nexport class ErrorBoundary extends Component<ErrorBoundaryProps, ErrorBoundaryState> {\n  state: ErrorBoundaryState = { error: null };\n\n  static getDerivedStateFromError(error: Error): ErrorBoundaryState {\n    return { error };\n  }\n\n  componentDidCatch(error: Error): void {\n    if (isControlError(error)) return; // a redirect isn't an error to report\n    this.props.onError?.(error);\n  }\n\n  componentDidUpdate(prev: ErrorBoundaryProps): void {\n    const { resetKeys } = this.props;\n    if (this.state.error && prev.resetKeys && resetKeys && keysChanged(prev.resetKeys, resetKeys)) {\n      this.reset();\n    }\n  }\n\n  reset = (): void => {\n    this.setState({ error: null });\n  };\n\n  render(): ReactNode {\n    const { error } = this.state;\n    if (error !== null) {\n      if (isControlError(error)) throw error; // navigation in flight — never show a fallback for it\n      const { fallback } = this.props;\n      if (fallback === undefined) throw error; // no local fallback → propagate to an outer boundary\n      return typeof fallback === 'function' ? fallback(error, this.reset) : fallback;\n    }\n    return this.props.children;\n  }\n}\n\nexport interface BoundaryProps {\n  /** Suspense fallback, shown while the children (or their data) are still loading. */\n  loading?: ReactNode;\n  /** Error fallback, shown if a child throws. See {@link ErrorFallback}. */\n  error?: ErrorFallback;\n  /** Called with the caught error. */\n  onError?: (error: Error) => void;\n  /** Clears the error fallback when any value changes — see {@link ErrorBoundaryProps.resetKeys}. */\n  resetKeys?: readonly unknown[];\n  children: ReactNode;\n}\n\n/**\n * A loading + error boundary in one wrapper — the common case for an async\n * section of a page. It always renders the same shape:\n *\n * ```tsx\n * <ErrorBoundary fallback={error}>\n *   <Suspense fallback={loading}>{children}</Suspense>\n * </ErrorBoundary>\n * ```\n *\n * so `error` catches anything the children throw (including while suspended) and\n * `loading` shows until they resolve. Both fallbacks are optional: omit\n * `loading` and nothing shows while loading; omit `error` and thrown errors\n * propagate to the next boundary out (or the global error page) rather than\n * being caught here.\n *\n * @example\n * ```tsx\n * import { Boundary } from '@rshono/core/client';\n *\n * <Boundary loading={<Spinner />} error={(e, reset) => <Retry onClick={reset} />}>\n *   <SlowServerComponent />\n * </Boundary>\n * ```\n */\nexport function Boundary({ loading = null, error, onError, resetKeys, children }: BoundaryProps): ReactNode {\n  return (\n    <ErrorBoundary fallback={error} onError={onError} resetKeys={resetKeys}>\n      <Suspense fallback={loading}>{children}</Suspense>\n    </ErrorBoundary>\n  );\n}\n"]}
+{"version":3,"file":"boundaries.js","sourceRoot":"","sources":["../../src/runtime/boundaries.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAC;;AAEb,OAAO,EAAE,SAAS,EAAE,QAAQ,EAAkB,MAAM,OAAO,CAAC;AAC5D,OAAO,EAAE,eAAe,EAAE,MAAM,cAAc,CAAC;AAE/C;;;;;GAKG;AACH,SAAS,cAAc,CAAC,KAAc;IACpC,OAAO,eAAe,CAAE,KAAqC,EAAE,MAAM,CAAC,CAAC;AACzE,CAAC;AAmCD,SAAS,WAAW,CAAC,CAAqB,EAAE,CAAqB;IAC/D,OAAO,CAAC,CAAC,MAAM,KAAK,CAAC,CAAC,MAAM,IAAI,CAAC,CAAC,IAAI,CAAC,CAAC,KAAK,EAAE,CAAC,EAAE,EAAE,CAAC,CAAC,MAAM,CAAC,EAAE,CAAC,KAAK,EAAE,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;AAChF,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,MAAM,OAAO,aAAc,SAAQ,SAAiD;IAClF,KAAK,GAAuB,EAAE,KAAK,EAAE,IAAI,EAAE,CAAC;IAE5C,MAAM,CAAC,wBAAwB,CAAC,KAAY;QAC1C,OAAO,EAAE,KAAK,EAAE,CAAC;IACnB,CAAC;IAED,iBAAiB,CAAC,KAAY;QAC5B,IAAI,cAAc,CAAC,KAAK,CAAC;YAAE,OAAO,CAAC,sCAAsC;QACzE,IAAI,CAAC,KAAK,CAAC,OAAO,EAAE,CAAC,KAAK,CAAC,CAAC;IAC9B,CAAC;IAED,kBAAkB,CAAC,IAAwB;QACzC,MAAM,EAAE,SAAS,EAAE,GAAG,IAAI,CAAC,KAAK,CAAC;QACjC,IAAI,IAAI,CAAC,KAAK,CAAC,KAAK,IAAI,IAAI,CAAC,SAAS,IAAI,SAAS,IAAI,WAAW,CAAC,IAAI,CAAC,SAAS,EAAE,SAAS,CAAC,EAAE,CAAC;YAC9F,IAAI,CAAC,KAAK,EAAE,CAAC;QACf,CAAC;IACH,CAAC;IAED,KAAK,GAAG,GAAS,EAAE;QACjB,IAAI,CAAC,QAAQ,CAAC,EAAE,KAAK,EAAE,IAAI,EAAE,CAAC,CAAC;IACjC,CAAC,CAAC;IAEF,MAAM;QACJ,MAAM,EAAE,KAAK,EAAE,GAAG,IAAI,CAAC,KAAK,CAAC;QAC7B,IAAI,KAAK,KAAK,IAAI,EAAE,CAAC;YACnB,IAAI,cAAc,CAAC,KAAK,CAAC;gBAAE,MAAM,KAAK,CAAC,CAAC,sDAAsD;YAC9F,MAAM,EAAE,QAAQ,EAAE,GAAG,IAAI,CAAC,KAAK,CAAC;YAChC,IAAI,QAAQ,KAAK,SAAS;gBAAE,MAAM,KAAK,CAAC,CAAC,qDAAqD;YAC9F,OAAO,OAAO,QAAQ,KAAK,UAAU,CAAC,CAAC,CAAC,QAAQ,CAAC,KAAK,EAAE,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,QAAQ,CAAC;QACjF,CAAC;QACD,OAAO,IAAI,CAAC,KAAK,CAAC,QAAQ,CAAC;IAC7B,CAAC;CACF;AAmBD;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,MAAM,UAAU,aAAa,CAAC,EAAE,OAAO,EAAE,KAAK,EAAE,OAAO,EAAE,SAAS,EAAE,QAAQ,EAAsB;IAChG,OAAO,CACL,KAAC,aAAa,IAAC,QAAQ,EAAE,KAAK,EAAE,OAAO,EAAE,OAAO,EAAE,SAAS,EAAE,SAAS,YACpE,KAAC,QAAQ,IAAC,QAAQ,EAAE,OAAO,YAAG,QAAQ,GAAY,GACpC,CACjB,CAAC;AACJ,CAAC","sourcesContent":["'use client';\n\nimport { Component, Suspense, type ReactNode } from 'react';\nimport { isControlDigest } from './control.js';\n\n/**\n * `redirect()` and `notFound()` reach the browser as a thrown error carrying a control digest.\n * They are navigation, not failure, so no boundary may absorb one — otherwise a `redirect()` from\n * a component inside a `<CatchBoundary>` would render \"something went wrong\" instead of navigating.\n * They're re-thrown to the root, where the runtime turns the digest into a real navigation.\n */\nfunction isControlError(error: unknown): boolean {\n  return isControlDigest((error as { digest?: unknown } | null)?.digest);\n}\n\n/**\n * What a {@link CatchBoundary} / {@link AsyncBoundary} renders once a child throws.\n * Either a static node, or a render function that also gets a `reset` callback\n * to clear the error and re-render the children (e.g. a \"Try again\" button).\n *\n * The render-function form only works when the boundary is used from a `'use\n * client'` component — functions can't cross the server→client boundary. From a\n * server component, pass a `ReactNode`.\n */\nexport type ErrorFallback = ReactNode | ((error: Error, reset: () => void) => ReactNode);\n\nexport interface CatchBoundaryProps {\n  /**\n   * Rendered in place of the children after one of them throws. Omit it to\n   * report the error via `onError` and re-throw to the next boundary out (or\n   * the global error page) instead of handling it here.\n   */\n  fallback?: ErrorFallback;\n  /** Called with the caught error (for logging / reporting). */\n  onError?: (error: Error) => void;\n  /**\n   * When any value in this array changes while the boundary is showing its\n   * fallback, the error is cleared automatically. Pass the current pathname to\n   * recover when the user navigates away: `resetKeys={[useNavigation().url.pathname]}`.\n   */\n  resetKeys?: readonly unknown[];\n  children: ReactNode;\n}\n\ninterface CatchBoundaryState {\n  error: Error | null;\n}\n\nfunction keysChanged(a: readonly unknown[], b: readonly unknown[]): boolean {\n  return a.length !== b.length || a.some((value, i) => !Object.is(value, b[i]));\n}\n\n/**\n * A general-purpose error boundary. Catches errors thrown while rendering its\n * children — a client island that blew up, or a server component that rejected\n * on a soft navigation — and renders `fallback` in their place instead of\n * tearing down the whole page.\n *\n * It's a `'use client'` component (React error boundaries must be), so drop it\n * anywhere in the tree from a server or client component. Use {@link AsyncBoundary}\n * when you also want a Suspense loading fallback in the same wrapper.\n *\n * @example\n * ```tsx\n * import { CatchBoundary } from '@rshono/core/client';\n *\n * <CatchBoundary fallback={(error, reset) => (\n *   <div role=\"alert\">\n *     <p>{error.message}</p>\n *     <button onClick={reset}>Try again</button>\n *   </div>\n * )}>\n *   <RiskyWidget />\n * </CatchBoundary>\n * ```\n */\nexport class CatchBoundary extends Component<CatchBoundaryProps, CatchBoundaryState> {\n  state: CatchBoundaryState = { error: null };\n\n  static getDerivedStateFromError(error: Error): CatchBoundaryState {\n    return { error };\n  }\n\n  componentDidCatch(error: Error): void {\n    if (isControlError(error)) return; // a redirect isn't an error to report\n    this.props.onError?.(error);\n  }\n\n  componentDidUpdate(prev: CatchBoundaryProps): void {\n    const { resetKeys } = this.props;\n    if (this.state.error && prev.resetKeys && resetKeys && keysChanged(prev.resetKeys, resetKeys)) {\n      this.reset();\n    }\n  }\n\n  reset = (): void => {\n    this.setState({ error: null });\n  };\n\n  render(): ReactNode {\n    const { error } = this.state;\n    if (error !== null) {\n      if (isControlError(error)) throw error; // navigation in flight — never show a fallback for it\n      const { fallback } = this.props;\n      if (fallback === undefined) throw error; // no local fallback → propagate to an outer boundary\n      return typeof fallback === 'function' ? fallback(error, this.reset) : fallback;\n    }\n    return this.props.children;\n  }\n}\n\nexport interface AsyncBoundaryProps {\n  /**\n   * Suspense fallback, shown while the children (or their data) are still\n   * loading. Required — a loading state is the reason to reach for this over\n   * {@link CatchBoundary}, so showing nothing is an explicit `loading={null}`\n   * rather than something you get by leaving the prop off.\n   */\n  loading: ReactNode;\n  /** Error fallback, shown if a child throws. See {@link ErrorFallback}. */\n  error?: ErrorFallback;\n  /** Called with the caught error. */\n  onError?: (error: Error) => void;\n  /** Clears the error fallback when any value changes — see {@link CatchBoundaryProps.resetKeys}. */\n  resetKeys?: readonly unknown[];\n  children: ReactNode;\n}\n\n/**\n * A loading + error boundary in one wrapper — the common case for an async\n * section of a page. It always renders the same shape:\n *\n * ```tsx\n * <CatchBoundary fallback={error}>\n *   <Suspense fallback={loading}>{children}</Suspense>\n * </CatchBoundary>\n * ```\n *\n * so `error` catches anything the children throw (including while suspended) and\n * `loading` shows until they resolve. `error` is optional: omit it and thrown\n * errors propagate to the next boundary out (or the global error page) rather\n * than being caught here.\n *\n * @example\n * ```tsx\n * import { AsyncBoundary } from '@rshono/core/client';\n *\n * <AsyncBoundary loading={<Spinner />} error={(e, reset) => <Retry onClick={reset} />}>\n *   <SlowServerComponent />\n * </AsyncBoundary>\n * ```\n */\nexport function AsyncBoundary({ loading, error, onError, resetKeys, children }: AsyncBoundaryProps): ReactNode {\n  return (\n    <CatchBoundary fallback={error} onError={onError} resetKeys={resetKeys}>\n      <Suspense fallback={loading}>{children}</Suspense>\n    </CatchBoundary>\n  );\n}\n"]}

package/dist/runtime/client.d.ts

@@ -1,15 +1,15 @@
 /**
  * `@rshono/core/client` — the browser-side surface, for use from `'use client'`
  * modules: {@link useNavigation} for the current URL and soft navigation, and
- * {@link Boundary} / {@link ErrorBoundary} as components.
+ * {@link AsyncBoundary} / {@link CatchBoundary} as components.
  *
  * Every export is itself a `'use client'` module, so a server component can
- * render {@link Boundary} directly — but the hook needs a client component. In a
+ * render {@link AsyncBoundary} directly — but the hook needs a client component. In a
  * server component, read the same request data from `getRequestContext()` in
  * `@rshono/core/server`.
  *
  * @packageDocumentation
  */
 export { useNavigation, type NavigationRouter, type NavigationState } from './navigation.js';
-export { Boundary, ErrorBoundary, type BoundaryProps, type ErrorBoundaryProps, type ErrorFallback } from './boundaries.js';
+export { AsyncBoundary, CatchBoundary, type AsyncBoundaryProps, type CatchBoundaryProps, type ErrorFallback } from './boundaries.js';
 //# sourceMappingURL=client.d.ts.map

package/dist/runtime/client.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"client.d.ts","sourceRoot":"","sources":["../../src/runtime/client.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH,OAAO,EAAE,aAAa,EAAE,KAAK,gBAAgB,EAAE,KAAK,eAAe,EAAE,MAAM,iBAAiB,CAAC;AAC7F,OAAO,EAAE,QAAQ,EAAE,aAAa,EAAE,KAAK,aAAa,EAAE,KAAK,kBAAkB,EAAE,KAAK,aAAa,EAAE,MAAM,iBAAiB,CAAC"}
+{"version":3,"file":"client.d.ts","sourceRoot":"","sources":["../../src/runtime/client.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH,OAAO,EAAE,aAAa,EAAE,KAAK,gBAAgB,EAAE,KAAK,eAAe,EAAE,MAAM,iBAAiB,CAAC;AAC7F,OAAO,EAAE,aAAa,EAAE,aAAa,EAAE,KAAK,kBAAkB,EAAE,KAAK,kBAAkB,EAAE,KAAK,aAAa,EAAE,MAAM,iBAAiB,CAAC"}

package/dist/runtime/client.js

@@ -1,15 +1,15 @@
 /**
  * `@rshono/core/client` — the browser-side surface, for use from `'use client'`
  * modules: {@link useNavigation} for the current URL and soft navigation, and
- * {@link Boundary} / {@link ErrorBoundary} as components.
+ * {@link AsyncBoundary} / {@link CatchBoundary} as components.
  *
  * Every export is itself a `'use client'` module, so a server component can
- * render {@link Boundary} directly — but the hook needs a client component. In a
+ * render {@link AsyncBoundary} directly — but the hook needs a client component. In a
  * server component, read the same request data from `getRequestContext()` in
  * `@rshono/core/server`.
  *
  * @packageDocumentation
  */
 export { useNavigation } from './navigation.js';
-export { Boundary, ErrorBoundary } from './boundaries.js';
+export { AsyncBoundary, CatchBoundary } from './boundaries.js';
 //# sourceMappingURL=client.js.map

package/dist/runtime/client.js.map

@@ -1 +1 @@
-{"version":3,"file":"client.js","sourceRoot":"","sources":["../../src/runtime/client.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH,OAAO,EAAE,aAAa,EAA+C,MAAM,iBAAiB,CAAC;AAC7F,OAAO,EAAE,QAAQ,EAAE,aAAa,EAAmE,MAAM,iBAAiB,CAAC","sourcesContent":["/**\n * `@rshono/core/client` — the browser-side surface, for use from `'use client'`\n * modules: {@link useNavigation} for the current URL and soft navigation, and\n * {@link Boundary} / {@link ErrorBoundary} as components.\n *\n * Every export is itself a `'use client'` module, so a server component can\n * render {@link Boundary} directly — but the hook needs a client component. In a\n * server component, read the same request data from `getRequestContext()` in\n * `@rshono/core/server`.\n *\n * @packageDocumentation\n */\n\nexport { useNavigation, type NavigationRouter, type NavigationState } from './navigation.js';\nexport { Boundary, ErrorBoundary, type BoundaryProps, type ErrorBoundaryProps, type ErrorFallback } from './boundaries.js';\n"]}
+{"version":3,"file":"client.js","sourceRoot":"","sources":["../../src/runtime/client.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH,OAAO,EAAE,aAAa,EAA+C,MAAM,iBAAiB,CAAC;AAC7F,OAAO,EAAE,aAAa,EAAE,aAAa,EAAwE,MAAM,iBAAiB,CAAC","sourcesContent":["/**\n * `@rshono/core/client` — the browser-side surface, for use from `'use client'`\n * modules: {@link useNavigation} for the current URL and soft navigation, and\n * {@link AsyncBoundary} / {@link CatchBoundary} as components.\n *\n * Every export is itself a `'use client'` module, so a server component can\n * render {@link AsyncBoundary} directly — but the hook needs a client component. In a\n * server component, read the same request data from `getRequestContext()` in\n * `@rshono/core/server`.\n *\n * @packageDocumentation\n */\n\nexport { useNavigation, type NavigationRouter, type NavigationState } from './navigation.js';\nexport { AsyncBoundary, CatchBoundary, type AsyncBoundaryProps, type CatchBoundaryProps, type ErrorFallback } from './boundaries.js';\n"]}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rshono/core",
-  "version": "1.0.0-rc.4",
+  "version": "1.0.0-rc.5",
   "description": "Minimalist web framework — Hono + Rspack + React Server Components",
   "author": "Lasse <lasse@lassetange.com> (https://www.lassetange.com)",
   "license": "ISC",