raf-effect-atom 0.2.6 → 0.3.1

package/CHANGELOG.md

@@ -1,19 +1,50 @@
 # Changelog
 
+## [0.3.1](https://github.com/KATT/raf-effect-atom/compare/raf-effect-atom%400.3.0...raf-effect-atom%400.3.1) (2026-10-24)
+
+### Features
+
+* **raf-effect-atom:** add useHandleValue, a handle read that doesn't suspend ([4b083f7](https://github.com/KATT/raf-effect-atom/commit/4b083f7dee91834cda71691f44a1498061f3cfe1))
+
+### Code Refactoring
+
+* name files in kebab-case, PascalCase only for Effect modules ([d76b06a](https://github.com/KATT/raf-effect-atom/commit/d76b06aef3d04d6be6c0b0e086a756234ab3f253))
+
+### Documentation
+
+* **raf-effect-atom:** pass a read's result to a boundary's hook in the README and JSDoc ([fd82e5c](https://github.com/KATT/raf-effect-atom/commit/fd82e5c1f92b3f99dc166140383837b11b695ca7))
+* **raf-effect-atom:** pass the atom to a boundary's hook in the README and JSDoc ([772d349](https://github.com/KATT/raf-effect-atom/commit/772d3494954f64a5c0fc92ebfd146b5f14e16e51))
+
+### Tests
+
+* **raf-effect-atom:** pass a read's result to a boundary's hook ([df11247](https://github.com/KATT/raf-effect-atom/commit/df11247edab69b060c0677059ae24a4d8835c28e))
+* **raf-effect-atom:** read through a boundary's hook with the atom ([de19b85](https://github.com/KATT/raf-effect-atom/commit/de19b8502ef41a8efbd9b50da6e00843cb38f2fd))
+* **raf-effect-atom:** start an Atom.swr over a keyed readable that picks a seed or a live query ([697e785](https://github.com/KATT/raf-effect-atom/commit/697e78550bff0dce02903b963677828786770338))
+
+## [0.3.0](https://github.com/KATT/raf-effect-atom/compare/raf-effect-atom%400.2.6...raf-effect-atom%400.3.0) (2026-10-23)
+
+### ⚠ BREAKING CHANGES
+
+- **raf-effect-atom:** `raf-effect-atom/next` is `raf-effect-atom/rsc`, without `dehydrate`; write `<HydrationBoundary registry={getRegistry()}>` from `raf-effect-atom` instead of `<HydrateAtoms state={await dehydrate()}>`, and import `RegistryProvider` from `raf-effect-atom`.
+
+### Features
+
+- **raf-effect-atom:** import HydrationBoundary from raf-effect-atom in server components, and the RSC verbs from raf-effect-atom/rsc ([bf7fdbc](https://github.com/KATT/raf-effect-atom/commit/bf7fdbcde2e9f785bd276a08117aefa359051b82))
+
 ## [0.2.6](https://github.com/KATT/raf-effect-atom/compare/raf-effect-atom%400.2.5...raf-effect-atom%400.2.6) (2026-10-23)
 
 ### Features
 
-* **raf-effect-atom:** start browser-only reads with prefetchInBrowser ([65f783a](https://github.com/KATT/raf-effect-atom/commit/65f783a0014e44a8aa11ce5e8fa34ab863063403))
+- **raf-effect-atom:** start browser-only reads with prefetchInBrowser ([65f783a](https://github.com/KATT/raf-effect-atom/commit/65f783a0014e44a8aa11ce5e8fa34ab863063403))
 
 ### Documentation
 
-* **www:** keep a search box's text in the URL, and drop the debounce sample ([a3949bf](https://github.com/KATT/raf-effect-atom/commit/a3949bfca4b64e478132f983033b2776e50ba949))
+- **www:** keep a search box's text in the URL, and drop the debounce sample ([a3949bf](https://github.com/KATT/raf-effect-atom/commit/a3949bfca4b64e478132f983033b2776e50ba949))
 
 ### Tests
 
-* **raf-effect-atom:** start a browser-only read from a client-only TanStack route ([69a8bd8](https://github.com/KATT/raf-effect-atom/commit/69a8bd887c34a7aeef51fdd20057ac30aa9e1fbc))
-* **raf-effect-atom:** type a derived atom's handle through it and its wrappers ([a16b587](https://github.com/KATT/raf-effect-atom/commit/a16b587a59dc4827dd18ecb3a3d5bb8f6fdedf0b))
+- **raf-effect-atom:** start a browser-only read from a client-only TanStack route ([69a8bd8](https://github.com/KATT/raf-effect-atom/commit/69a8bd887c34a7aeef51fdd20057ac30aa9e1fbc))
+- **raf-effect-atom:** type a derived atom's handle through it and its wrappers ([a16b587](https://github.com/KATT/raf-effect-atom/commit/a16b587a59dc4827dd18ecb3a3d5bb8f6fdedf0b))
 
 ## [0.2.5](https://github.com/KATT/raf-effect-atom/compare/raf-effect-atom%400.2.4...raf-effect-atom%400.2.5) (2026-10-23)
 

package/README.md

@@ -37,13 +37,13 @@ export async function loader(args: LoaderArgs) {
 }
 ```
 
-A component takes the handle as a prop and reads it with `useAtomResult(source, handle)`, which waits for a streamed result instead of starting the atom again, and returns typed failures. Given a handle instead of an id, it can't start a request of its own. The source can be a family derived from the loader's, such as the one an [`effect-atom-boundary`](https://github.com/KATT/raf-effect-atom/tree/main/packages/effect-atom-boundary) boundary's `wrap` returns, which throws the errors that boundary claims to it:
+A component takes the handle as a prop and reads it with `useAtomResult(source, handle)`, which waits for a streamed result instead of starting the atom again, and returns typed failures. Given a handle instead of an id, it can't start a request of its own. An [`effect-atom-boundary`](https://github.com/KATT/raf-effect-atom/tree/main/packages/effect-atom-boundary) boundary's hook takes the result, throws the errors that boundary claims to it, and returns the rest:
 
 ```tsx
 import { type Handle, useAtomResult } from "raf-effect-atom";
 
 function IssueTitle(props: { readonly issue: Handle<typeof issue> }) {
-	const result = useAtomResult(useIssueBoundary().wrap(issue), props.issue);
+	const result = useIssueBoundary(useAtomResult(issue, props.issue));
 	// Success<Issue, never>: its boundaries claim every failure
 	return <h1>{result.value.title}</h1>;
 }
@@ -52,8 +52,8 @@ function IssueTitle(props: { readonly issue: Handle<typeof issue> }) {
 Each framework has a subpath that gives every server request its own registry and sends it to the browser:
 
 - `raf-effect-atom/tanstack-router`, for TanStack Router and TanStack Start: `setupRouterAtoms({ router, registry })` in `getRouter`, with `Loader.make(registry)` on the router context.
-- `raf-effect-atom/next`, for the App Router: `prefetch`, `ensure` and `fetch` in server components, which pass the handles to client components as props, and `<HydrateAtoms state={await dehydrate()}>` around them. `makeRequestAtoms({ seed })` makes the same functions over a registry seeded from the request, such as with its cookie.
-- `raf-effect-atom/react-router`, for Framework Mode: `atomsMiddleware(atomsContext)` as the root middleware and `clientAtomsMiddleware(atomsContext)` as its client middleware, loaders that return `atoms.dehydrate()` with their handles and double as client loaders, and `HydrationBoundary` in the route component.
+- `raf-effect-atom/rsc`, for React Server Components such as the Next.js App Router: `prefetch`, `ensure` and `fetch` in server components, which pass the handles to client components as props, and `<HydrationBoundary registry={getRegistry()}>` around them. `HydrationBoundary` and `RegistryProvider` come from `raf-effect-atom` itself: server components get the build that takes the request's registry through the `react-server` export condition. `makeRequestAtoms({ seed })` makes the same functions over a registry seeded from the request, such as with its cookie.
+- `raf-effect-atom/react-router`, for Framework Mode: `atomsMiddleware(atomsContext)` as the root middleware and `clientAtomsMiddleware(atomsContext)` as its client middleware, loaders that return `atoms.dehydrate()` with their handles and double as client loaders, and `<HydrationBoundary state={loaderData.atoms}>` in the route component.
 
 In development, `useAtomResult` reports a read that starts an atom nothing started, a request waterfall. `<WaterfallDetection mode="throw">` at the root makes it throw to the nearest error boundary. `useWaterfall(source, ...args)` starts an atom whose input exists only in render, marks it as a known waterfall, and returns its handle.
 

package/dist/Loader.d.mts

@@ -1,4 +1,4 @@
-import { ArgsOf, ErrorOf, Handle, LoadedHandle, Source, SuccessOf } from "./Handle.mjs";
+import { ArgsOf, ErrorOf, Handle, LoadedHandle, Source, SuccessOf } from "./handle.mjs";
 import * as Context from "effect/Context";
 import * as Duration from "effect/Duration";
 import * as Effect from "effect/Effect";
@@ -44,11 +44,10 @@ export declare const LeaseTTL: Context.Reference<Duration.Duration>;
  *   is. Takes a lease either way. The component that reads the handle
  *   suspends until the result settles. On a request registry whose async
  *   seed is still running, it waits for the seed first.
- * - A derived atom that isn't serializable, such as an error boundary's
- *   `wrap(source)`, starts the first serializable atom its
- *   `initialValueTarget` chain points at, the one `useAtomResult` reads it
- *   through: the lease, the handle's key and what the server sends are
- *   that atom's. `ensure` and `fetch` wait for the derived atom's own
+ * - A derived atom that isn't serializable starts the first serializable
+ *   atom its `initialValueTarget` chain points at, the one `useAtomResult`
+ *   reads it through: the lease, the handle's key and what the server sends
+ *   are that atom's. `ensure` and `fetch` wait for the derived atom's own
  *   result.
  *
  * **Gotchas**

package/dist/Loader.mjs

@@ -125,11 +125,10 @@ const rejectDefects = (result) => {
 *   is. Takes a lease either way. The component that reads the handle
 *   suspends until the result settles. On a request registry whose async
 *   seed is still running, it waits for the seed first.
-* - A derived atom that isn't serializable, such as an error boundary's
-*   `wrap(source)`, starts the first serializable atom its
-*   `initialValueTarget` chain points at, the one `useAtomResult` reads it
-*   through: the lease, the handle's key and what the server sends are
-*   that atom's. `ensure` and `fetch` wait for the derived atom's own
+* - A derived atom that isn't serializable starts the first serializable
+*   atom its `initialValueTarget` chain points at, the one `useAtomResult`
+*   reads it through: the lease, the handle's key and what the server sends
+*   are that atom's. `ensure` and `fetch` wait for the derived atom's own
 *   result.
 *
 * **Gotchas**

package/dist/hydration-boundary-react-server.d.mts

@@ -0,0 +1,25 @@
+import { HydrationBoundaryProps } from "./hydration-boundary.mjs";
+import * as React from "react";
+/**
+ * Sends a server component's request registry to the client components
+ * under it.
+ *
+ * **Details**
+ *
+ * With `registry`, it waits for the registry's seed, dehydrates the atoms
+ * started so far, and renders the client `HydrationBoundary` with that
+ * state. React serializes the state's promises with the payload, so a result
+ * still loading streams in when it settles. With `state`, it passes that
+ * state on.
+ *
+ * **Gotchas**
+ *
+ * Call the verbs before rendering it: each boundary sends what its registry
+ * held when it rendered. It throws for a registry that isn't a request
+ * registry, which every request would share.
+ *
+ * @stability unstable
+ * @category components
+ * @since 0.3.0
+ */
+export declare const HydrationBoundary: (props: HydrationBoundaryProps) => Promise<React.ReactNode>;

package/dist/hydration-boundary-react-server.mjs

@@ -0,0 +1,41 @@
+import { dehydrate } from "./Hydration.mjs";
+import { isRequestRegistry, settled } from "./RequestRegistry.mjs";
+import { HydrationBoundary as HydrationBoundary$1 } from "./hydration-boundary.mjs";
+import { jsx } from "react/jsx-runtime";
+// src/hydration-boundary-react-server.tsx
+/**
+* Sends a server component's request registry to the client components
+* under it.
+*
+* **Details**
+*
+* With `registry`, it waits for the registry's seed, dehydrates the atoms
+* started so far, and renders the client `HydrationBoundary` with that
+* state. React serializes the state's promises with the payload, so a result
+* still loading streams in when it settles. With `state`, it passes that
+* state on.
+*
+* **Gotchas**
+*
+* Call the verbs before rendering it: each boundary sends what its registry
+* held when it rendered. It throws for a registry that isn't a request
+* registry, which every request would share.
+*
+* @stability unstable
+* @category components
+* @since 0.3.0
+*/
+const HydrationBoundary = async (props) => {
+	const registry = props.registry;
+	if (registry === void 0) return /* @__PURE__ */ jsx(HydrationBoundary$1, {
+		state: props.state,
+		children: props.children
+	});
+	if (!isRequestRegistry(registry)) throw new Error("raf-effect-atom: HydrationBoundary got a registry that isn't a request registry, which would share results between requests. Pass raf-effect-atom/rsc's getRegistry(), or one makeRequestAtoms made.");
+	await settled(registry);
+	return /* @__PURE__ */ jsx(HydrationBoundary$1, {
+		state: dehydrate(registry),
+		children: props.children
+	});
+};
+export { HydrationBoundary };

package/dist/hydration-boundary.d.mts

@@ -0,0 +1,91 @@
+import * as Hydration from "effect/reactivity/Hydration";
+import * as AtomRegistry from "effect/reactivity/AtomRegistry";
+import * as React from "react";
+/**
+ * Props for `HydrationBoundary`: the request's `registry` in a server
+ * component, or the `state` it dehydrated anywhere else.
+ *
+ * @stability unstable
+ * @category models
+ * @since 0.1.0
+ */
+export type HydrationBoundaryProps = {
+  readonly children?: React.ReactNode | undefined;
+  /**
+   * The request registry of the server component render, such as
+   * `raf-effect-atom/rsc`'s `getRegistry()`. Server components only.
+   */
+  readonly registry: AtomRegistry.AtomRegistry;
+  readonly state?: never;
+} | {
+  readonly children?: React.ReactNode | undefined;
+  readonly registry?: never;
+  /** The state `Hydration.dehydrate` returned on the server. */
+  readonly state?: Iterable<Hydration.DehydratedAtom> | undefined;
+};
+/**
+ * Hydrates the state a server registry dehydrated, streamed results
+ * included.
+ *
+ * **When to use**
+ *
+ * Use where the server's state reaches the React tree through rendering
+ * rather than a router: a server component's registry, or a React Router
+ * loader's data. A router that hydrates before rendering calls
+ * `Hydration.hydrate` instead.
+ *
+ * **Details**
+ *
+ * In a server component, pass the request's `registry`. Server components
+ * get their own build of `HydrationBoundary` through the package's
+ * `react-server` export condition: it waits for the registry's seed,
+ * dehydrates it, and sends the state with the server component's payload,
+ * so results still loading stream in as they settle.
+ *
+ * Anywhere else, pass the `state` a loader dehydrated. Settled values go to
+ * `@effect/atom-react`'s `HydrationBoundary`, which hydrates new atoms
+ * during render and existing ones after commit. Each streamed result is
+ * held until it arrives, so `useAtomResult` waits for it instead of
+ * requesting it again.
+ *
+ * During server rendering, when `state` is the array `dehydrate` returned,
+ * as React Router passes a loader's data to the server render, the children
+ * read the registry it came from instead of a copy. The loaders' atoms are
+ * there, so an `effect-atom-boundary` boundary sees their failures before
+ * its children read them and renders its handler on the server.
+ *
+ * **Gotchas**
+ *
+ * `registry` works only in server components: in a client component it
+ * throws, since a registry can't cross to the browser. In development, it
+ * throws during server rendering when the registry isn't a request
+ * registry, such as `@effect/atom-react`'s default one, which every request
+ * shares: one request's state would reach the others.
+ *
+ * **Example**
+ *
+ * ```tsx
+ * import { HydrationBoundary } from "raf-effect-atom"
+ * import { ensure, getRegistry } from "raf-effect-atom/rsc"
+ *
+ * // A server component
+ * export default async function IssueRoute(props: { params: Promise<{ id: string }> }) {
+ *   const handle = await ensure(issue, Number((await props.params).id))
+ *   return (
+ *     <HydrationBoundary registry={getRegistry()}>
+ *       <IssuePage issue={handle} />
+ *     </HydrationBoundary>
+ *   )
+ * }
+ *
+ * // A React Router route component
+ * <HydrationBoundary state={loaderData.atoms}>
+ *   <IssuePage issue={loaderData.issue} />
+ * </HydrationBoundary>
+ * ```
+ *
+ * @stability unstable
+ * @category components
+ * @since 0.1.0
+ */
+export declare const HydrationBoundary: (props: HydrationBoundaryProps) => React.ReactNode;

package/dist/{ReactHydration.mjs → hydration-boundary.mjs}

@@ -5,7 +5,7 @@ import { isServer, requireRequestRegistry } from "./internal/registry.mjs";
 import { HydrationBoundary, RegistryContext } from "@effect/atom-react";
 import * as React from "react";
 import { jsx } from "react/jsx-runtime";
-// src/ReactHydration.tsx
+// src/hydration-boundary.tsx
 /**
 * Applies a server registry's dehydrated state to the nearest
 * `RegistryContext`, while rendering.
@@ -19,16 +19,24 @@ import { jsx } from "react/jsx-runtime";
 *
 * **When to use**
 *
-* Use where the server's state reaches the React tree as a prop, such as
-* React Server Components props or a React Router loader's data. A router
-* that hydrates before rendering calls `Hydration.hydrate` instead.
+* Use where the server's state reaches the React tree through rendering
+* rather than a router: a server component's registry, or a React Router
+* loader's data. A router that hydrates before rendering calls
+* `Hydration.hydrate` instead.
 *
 * **Details**
 *
-* Settled values go to `@effect/atom-react`'s `HydrationBoundary`, which
-* hydrates new atoms during render and existing ones after commit. Each
-* streamed result is held until it arrives, so `useAtomResult` waits for it
-* instead of requesting it again.
+* In a server component, pass the request's `registry`. Server components
+* get their own build of `HydrationBoundary` through the package's
+* `react-server` export condition: it waits for the registry's seed,
+* dehydrates it, and sends the state with the server component's payload,
+* so results still loading stream in as they settle.
+*
+* Anywhere else, pass the `state` a loader dehydrated. Settled values go to
+* `@effect/atom-react`'s `HydrationBoundary`, which hydrates new atoms
+* during render and existing ones after commit. Each streamed result is
+* held until it arrives, so `useAtomResult` waits for it instead of
+* requesting it again.
 *
 * During server rendering, when `state` is the array `dehydrate` returned,
 * as React Router passes a loader's data to the server render, the children
@@ -38,15 +46,29 @@ import { jsx } from "react/jsx-runtime";
 *
 * **Gotchas**
 *
-* In development, it throws during server rendering when the registry isn't
-* a request registry, such as `@effect/atom-react`'s default one, which
-* every request shares: one request's state would reach the others.
+* `registry` works only in server components: in a client component it
+* throws, since a registry can't cross to the browser. In development, it
+* throws during server rendering when the registry isn't a request
+* registry, such as `@effect/atom-react`'s default one, which every request
+* shares: one request's state would reach the others.
 *
 * **Example**
 *
 * ```tsx
 * import { HydrationBoundary } from "raf-effect-atom"
+* import { ensure, getRegistry } from "raf-effect-atom/rsc"
+*
+* // A server component
+* export default async function IssueRoute(props: { params: Promise<{ id: string }> }) {
+*   const handle = await ensure(issue, Number((await props.params).id))
+*   return (
+*     <HydrationBoundary registry={getRegistry()}>
+*       <IssuePage issue={handle} />
+*     </HydrationBoundary>
+*   )
+* }
 *
+* // A React Router route component
 * <HydrationBoundary state={loaderData.atoms}>
 *   <IssuePage issue={loaderData.issue} />
 * </HydrationBoundary>
@@ -57,6 +79,7 @@ import { jsx } from "react/jsx-runtime";
 * @since 0.1.0
 */
 const HydrationBoundary$1 = (props) => {
+	if (props.registry !== void 0) throw new Error("raf-effect-atom: HydrationBoundary needs `state` here. `registry` works only in server components.");
 	const context = React.useContext(RegistryContext);
 	const state = props.state;
 	const source = isServer() ? sourceOf(state) : void 0;

package/dist/index-react-server.d.mts

@@ -0,0 +1,11 @@
+import { ArgsOf, ErrorOf, Handle, HandleKey, LoadedHandle, Source, SuccessOf } from "./handle.mjs";
+import { Hydration_d_exports } from "./Hydration.mjs";
+import { Loader_d_exports } from "./Loader.mjs";
+import { RequestRegistry_d_exports } from "./RequestRegistry.mjs";
+import { useAtomResult, useHandleValue } from "./use-atom-result.mjs";
+import { HydrationBoundaryProps } from "./hydration-boundary.mjs";
+import { RegistryProvider } from "./registry-provider.mjs";
+import { WaterfallDetection, WaterfallMode, useWaterfall } from "./waterfalls.mjs";
+import "./index-shared.mjs";
+import { HydrationBoundary } from "./hydration-boundary-react-server.mjs";
+export { ArgsOf, ErrorOf, Handle, HandleKey, Hydration_d_exports as Hydration, HydrationBoundary, type HydrationBoundaryProps, LoadedHandle, Loader_d_exports as Loader, RegistryProvider, RequestRegistry_d_exports as RequestRegistry, Source, SuccessOf, WaterfallDetection, WaterfallMode, useAtomResult, useHandleValue, useWaterfall };

package/dist/index-react-server.mjs

@@ -0,0 +1,8 @@
+import { Hydration_exports } from "./Hydration.mjs";
+import { RequestRegistry_exports } from "./RequestRegistry.mjs";
+import { Loader_exports } from "./Loader.mjs";
+import { useAtomResult, useHandleValue } from "./use-atom-result.mjs";
+import { RegistryProvider } from "./registry-provider.mjs";
+import { WaterfallDetection, useWaterfall } from "./waterfalls.mjs";
+import { HydrationBoundary } from "./hydration-boundary-react-server.mjs";
+export { Hydration_exports as Hydration, HydrationBoundary, Loader_exports as Loader, RegistryProvider, RequestRegistry_exports as RequestRegistry, WaterfallDetection, useAtomResult, useHandleValue, useWaterfall };

package/dist/index-shared.d.mts

@@ -0,0 +1,9 @@
+import { ArgsOf, ErrorOf, Handle, HandleKey, LoadedHandle, Source, SuccessOf } from "./handle.mjs";
+import { Hydration_d_exports } from "./Hydration.mjs";
+import { Loader_d_exports } from "./Loader.mjs";
+import { RequestRegistry_d_exports } from "./RequestRegistry.mjs";
+import { useAtomResult, useHandleValue } from "./use-atom-result.mjs";
+import { HydrationBoundaryProps } from "./hydration-boundary.mjs";
+import { RegistryProvider } from "./registry-provider.mjs";
+import { WaterfallDetection, WaterfallMode, useWaterfall } from "./waterfalls.mjs";
+export { ArgsOf, ErrorOf, Handle, HandleKey, Hydration_d_exports as Hydration, type HydrationBoundaryProps, LoadedHandle, Loader_d_exports as Loader, RegistryProvider, RequestRegistry_d_exports as RequestRegistry, Source, SuccessOf, WaterfallDetection, WaterfallMode, useAtomResult, useHandleValue, useWaterfall };

package/dist/index.d.mts

@@ -1,8 +1,10 @@
-import { ArgsOf, ErrorOf, Handle, HandleKey, LoadedHandle, Source, SuccessOf } from "./Handle.mjs";
+import { ArgsOf, ErrorOf, Handle, HandleKey, LoadedHandle, Source, SuccessOf } from "./handle.mjs";
+import { Hydration_d_exports } from "./Hydration.mjs";
 import { Loader_d_exports } from "./Loader.mjs";
 import { RequestRegistry_d_exports } from "./RequestRegistry.mjs";
-import { HydrationBoundary, HydrationBoundaryProps } from "./ReactHydration.mjs";
-import { Hydration_d_exports } from "./Hydration.mjs";
-import { useAtomResult } from "./Hooks.mjs";
-import { WaterfallDetection, WaterfallMode, useWaterfall } from "./Waterfalls.mjs";
-export { ArgsOf, ErrorOf, Handle, HandleKey, Hydration_d_exports as Hydration, HydrationBoundary, HydrationBoundaryProps, LoadedHandle, Loader_d_exports as Loader, RequestRegistry_d_exports as RequestRegistry, Source, SuccessOf, WaterfallDetection, WaterfallMode, useAtomResult, useWaterfall };
+import { useAtomResult, useHandleValue } from "./use-atom-result.mjs";
+import { HydrationBoundary, HydrationBoundaryProps } from "./hydration-boundary.mjs";
+import { RegistryProvider } from "./registry-provider.mjs";
+import { WaterfallDetection, WaterfallMode, useWaterfall } from "./waterfalls.mjs";
+import "./index-shared.mjs";
+export { ArgsOf, ErrorOf, Handle, HandleKey, Hydration_d_exports as Hydration, HydrationBoundary, type HydrationBoundaryProps, LoadedHandle, Loader_d_exports as Loader, RegistryProvider, RequestRegistry_d_exports as RequestRegistry, Source, SuccessOf, WaterfallDetection, WaterfallMode, useAtomResult, useHandleValue, useWaterfall };

package/dist/index.mjs

@@ -1,7 +1,8 @@
 import { Hydration_exports } from "./Hydration.mjs";
 import { RequestRegistry_exports } from "./RequestRegistry.mjs";
 import { Loader_exports } from "./Loader.mjs";
-import { useAtomResult } from "./Hooks.mjs";
-import { HydrationBoundary } from "./ReactHydration.mjs";
-import { WaterfallDetection, useWaterfall } from "./Waterfalls.mjs";
-export { Hydration_exports as Hydration, HydrationBoundary, Loader_exports as Loader, RequestRegistry_exports as RequestRegistry, WaterfallDetection, useAtomResult, useWaterfall };
+import { useAtomResult, useHandleValue } from "./use-atom-result.mjs";
+import { RegistryProvider } from "./registry-provider.mjs";
+import { WaterfallDetection, useWaterfall } from "./waterfalls.mjs";
+import { HydrationBoundary } from "./hydration-boundary.mjs";
+export { Hydration_exports as Hydration, HydrationBoundary, Loader_exports as Loader, RegistryProvider, RequestRegistry_exports as RequestRegistry, WaterfallDetection, useAtomResult, useHandleValue, useWaterfall };

package/dist/internal/{next.mjs → rsc.mjs}

@@ -1,8 +1,7 @@
-import { dehydrate } from "../Hydration.mjs";
-import { make as make$1, settled } from "../RequestRegistry.mjs";
+import { make as make$1 } from "../RequestRegistry.mjs";
 import { make as make$2 } from "../Loader.mjs";
 import * as React from "react";
-// src/internal/next.ts
+// src/internal/rsc.ts
 const renderSignal = () => {
 	return React.cacheSignal();
 };
@@ -14,11 +13,6 @@ const make = (options) => {
 	});
 	const getLoader = React.cache(() => make$2(getRegistry(), { signal: renderSignal() ?? void 0 }));
 	return {
-		dehydrate: async () => {
-			const registry = getRegistry();
-			await settled(registry);
-			return dehydrate(registry);
-		},
 		ensure: (source, ...args) => getLoader().ensure(source, ...args),
 		fetch: (source, ...args) => getLoader().fetch(source, ...args),
 		getRegistry,

package/dist/{ReactRouter.d.mts → react-router.d.mts}

@@ -1,5 +1,4 @@
 import { Loader } from "./Loader.mjs";
-import { RegistryProvider } from "./RegistryProvider.mjs";
 import * as EffectHydration from "effect/reactivity/Hydration";
 import * as AtomRegistry from "effect/reactivity/AtomRegistry";
 /**
@@ -140,5 +139,4 @@ export declare const atomsMiddleware: (context: AtomsContext, options?: AtomsMid
  * @category integrations
  * @since 0.2.1
  */
-export declare const clientAtomsMiddleware: (context: AtomsContext) => <Result>(args: MiddlewareArgs, next: () => Promise<Result>) => Promise<Result>;
-export { RegistryProvider };
+export declare const clientAtomsMiddleware: (context: AtomsContext) => <Result>(args: MiddlewareArgs, next: () => Promise<Result>) => Promise<Result>;

package/dist/{ReactRouter.mjs → react-router.mjs}

@@ -2,20 +2,20 @@ import { dehydrate } from "./Hydration.mjs";
 import { make, settled } from "./RequestRegistry.mjs";
 import { make as make$1 } from "./Loader.mjs";
 import { current } from "./internal/registry.mjs";
-import { RegistryProvider } from "./RegistryProvider.mjs";
 import * as Predicate from "effect/Predicate";
-// src/ReactRouter.ts
+// src/react-router.ts
 /**
 * Connects the loader verbs to React Router's Framework Mode.
 *
 * A root `middleware` gives each server request its own registry, under a
 * router context the app creates. Loaders start atoms with its verbs and
 * return its `dehydrate()` with their data; the route component hydrates it
-* with `HydrationBoundary`, inside the root's `RegistryProvider`. A root
-* `clientMiddleware` puts the browser's registry under the same context, so
-* one function can be both the route's `loader` and its `clientLoader`: after the first
-* page, loaders run in the browser, where `ensure` finds what the registry
-* already holds. Nothing is imported from `react-router`.
+* with `HydrationBoundary`, inside the root's `RegistryProvider`, both from
+* `raf-effect-atom`. A root `clientMiddleware` puts the browser's registry
+* under the same context, so one function can be both the route's `loader`
+* and its `clientLoader`: after the first page, loaders run in the browser,
+* where `ensure` finds what the registry already holds. Nothing is imported
+* from `react-router`.
 *
 * **Example**
 *
@@ -192,7 +192,7 @@ const disposeAfter = (body, registry) => {
 */
 const clientAtomsMiddleware = (context) => (args, next) => {
 	const registry = current();
-	if (registry === void 0) throw new Error("clientAtomsMiddleware found no mounted RegistryProvider: render raf-effect-atom/react-router's RegistryProvider around the app in the root layout.");
+	if (registry === void 0) throw new Error("clientAtomsMiddleware found no mounted RegistryProvider: render raf-effect-atom's RegistryProvider around the app in the root layout.");
 	args.context.set(context, {
 		...make$1(registry, { signal: args.request.signal }),
 		dehydrate: () => [],
@@ -200,4 +200,4 @@ const clientAtomsMiddleware = (context) => (args, next) => {
 	});
 	return next();
 };
-export { RegistryProvider, atomsMiddleware, clientAtomsMiddleware };
+export { atomsMiddleware, clientAtomsMiddleware };

package/dist/{RegistryProvider.d.mts → registry-provider.d.mts}

@@ -24,7 +24,7 @@ import * as React from "react";
  * **Example**
  *
  * ```tsx
- * import { RegistryProvider } from "raf-effect-atom/next" // or "raf-effect-atom/react-router"
+ * import { RegistryProvider } from "raf-effect-atom"
  *
  * export default function RootLayout(props: { children: React.ReactNode }) {
  *   return (

package/dist/{RegistryProvider.mjs → registry-provider.mjs}

@@ -3,9 +3,10 @@ import { make, mount } from "./internal/registry.mjs";
 import { RegistryContext } from "@effect/atom-react";
 import * as React from "react";
 import { jsx } from "react/jsx-runtime";
-// src/RegistryProvider.tsx
+// src/registry-provider.tsx
 /**
-* The registry provider shared by the Next.js and React Router integrations.
+* The registry provider for apps that render the server's state through
+* `HydrationBoundary`, such as React Server Components and React Router.
 *
 * @stability unstable
 * @since 0.1.0
@@ -35,7 +36,7 @@ import { jsx } from "react/jsx-runtime";
 * **Example**
 *
 * ```tsx
-* import { RegistryProvider } from "raf-effect-atom/next" // or "raf-effect-atom/react-router"
+* import { RegistryProvider } from "raf-effect-atom"
 *
 * export default function RootLayout(props: { children: React.ReactNode }) {
 *   return (

package/dist/{Next.d.mts → rsc.d.mts}

@@ -1,13 +1,10 @@
-import { ArgsOf, Handle, LoadedHandle, Source } from "./Handle.mjs";
+import { ArgsOf, Handle, LoadedHandle, Source } from "./handle.mjs";
 import { Loader } from "./Loader.mjs";
 import { Options } from "./RequestRegistry.mjs";
-import { HydrateAtoms } from "./NextClient.mjs";
-import { RegistryProvider } from "./RegistryProvider.mjs";
-import * as EffectHydration from "effect/reactivity/Hydration";
 import * as AtomRegistry from "effect/reactivity/AtomRegistry";
 /**
  * The loader verbs over the request registry of the server render in
- * progress, with its registry and `dehydrate`.
+ * progress, with its registry.
  *
  * @stability unstable
  * @category models
@@ -15,30 +12,28 @@ import * as AtomRegistry from "effect/reactivity/AtomRegistry";
  */
 export interface RequestAtoms extends Loader {
   /**
-   * `Hydration.dehydrate` on the request's registry, for `HydrateAtoms`,
-   * once its seed has settled.
+   * The request registry of the server render in progress, for
+   * `HydrationBoundary`'s `registry`.
    */
-  readonly dehydrate: () => Promise<Array<EffectHydration.DehydratedAtom>>;
-  /** The request registry of the server render in progress. */
   readonly getRegistry: () => AtomRegistry.AtomRegistry;
 }
 /**
- * Creates the verbs, `getRegistry` and `dehydrate` over a request registry
- * that `seed` prepares.
+ * Creates the verbs and `getRegistry` over a request registry that `seed`
+ * prepares.
  *
  * **When to use**
  *
  * Use when the request's atoms need something from the request before they
  * run, such as an RPC protocol that forwards the page request's cookie. Make
  * them once, in a server-only module, and call the verbs on them instead of
- * the ones `raf-effect-atom/next` exports.
+ * the ones `raf-effect-atom/rsc` exports.
  *
  * **Details**
  *
  * The seed runs on each request's registry when a server component first
  * uses it. It can be async, as `headers()` is: `ensure` and `fetch` wait
  * for it, `prefetch` returns its handle at once and starts the atom once the
- * seed resolves, and `dehydrate` waits for both.
+ * seed resolves, and `HydrationBoundary` waits for both.
  *
  * **Example**
  *
@@ -46,7 +41,7 @@ export interface RequestAtoms extends Loader {
  * // src/atoms.server.ts
  * import "server-only"
  * import { headers } from "next/headers"
- * import { makeRequestAtoms } from "raf-effect-atom/next"
+ * import { makeRequestAtoms } from "raf-effect-atom/rsc"
  *
  * export const atoms = makeRequestAtoms({
  *   seed: async (registry) => {
@@ -136,26 +131,4 @@ export declare const fetch: <S extends Source>(source: S, ...args: ArgsOf<S>) =>
  * @category verbs
  * @since 0.2.3
  */
-export declare const run: Loader["run"];
-/**
- * `Hydration.dehydrate` on the request's registry, for `HydrateAtoms`.
- *
- * **Gotchas**
- *
- * Includes the atoms started so far, so call it after the server component's
- * verbs. Each `HydrateAtoms` hydrates what its own `dehydrate()` saw.
- *
- * **Example**
- *
- * ```tsx
- * <HydrateAtoms state={await dehydrate()}>
- *   <Issue issue={handle} />
- * </HydrateAtoms>
- * ```
- *
- * @stability unstable
- * @category dehydration
- * @since 0.1.0
- */
-export declare const dehydrate: () => Promise<Array<EffectHydration.DehydratedAtom>>;
-export { HydrateAtoms, RegistryProvider };
+export declare const run: Loader["run"];

package/dist/{Next.mjs → rsc.mjs}

@@ -1,24 +1,22 @@
-import { make } from "./internal/next.mjs";
-import { HydrateAtoms } from "./NextClient.mjs";
-import { RegistryProvider } from "./RegistryProvider.mjs";
-// src/Next.ts
+import { make } from "./internal/rsc.mjs";
+// src/rsc.ts
 /**
-* Creates the verbs, `getRegistry` and `dehydrate` over a request registry
-* that `seed` prepares.
+* Creates the verbs and `getRegistry` over a request registry that `seed`
+* prepares.
 *
 * **When to use**
 *
 * Use when the request's atoms need something from the request before they
 * run, such as an RPC protocol that forwards the page request's cookie. Make
 * them once, in a server-only module, and call the verbs on them instead of
-* the ones `raf-effect-atom/next` exports.
+* the ones `raf-effect-atom/rsc` exports.
 *
 * **Details**
 *
 * The seed runs on each request's registry when a server component first
 * uses it. It can be async, as `headers()` is: `ensure` and `fetch` wait
 * for it, `prefetch` returns its handle at once and starts the atom once the
-* seed resolves, and `dehydrate` waits for both.
+* seed resolves, and `HydrationBoundary` waits for both.
 *
 * **Example**
 *
@@ -26,7 +24,7 @@ import { RegistryProvider } from "./RegistryProvider.mjs";
 * // src/atoms.server.ts
 * import "server-only"
 * import { headers } from "next/headers"
-* import { makeRequestAtoms } from "raf-effect-atom/next"
+* import { makeRequestAtoms } from "raf-effect-atom/rsc"
 *
 * export const atoms = makeRequestAtoms({
 *   seed: async (registry) => {
@@ -118,25 +116,4 @@ const fetch = atoms.fetch;
 * @since 0.2.3
 */
 const run = atoms.run;
-/**
-* `Hydration.dehydrate` on the request's registry, for `HydrateAtoms`.
-*
-* **Gotchas**
-*
-* Includes the atoms started so far, so call it after the server component's
-* verbs. Each `HydrateAtoms` hydrates what its own `dehydrate()` saw.
-*
-* **Example**
-*
-* ```tsx
-* <HydrateAtoms state={await dehydrate()}>
-*   <Issue issue={handle} />
-* </HydrateAtoms>
-* ```
-*
-* @stability unstable
-* @category dehydration
-* @since 0.1.0
-*/
-const dehydrate = atoms.dehydrate;
-export { HydrateAtoms, RegistryProvider, dehydrate, ensure, fetch, getRegistry, makeRequestAtoms, prefetch, prefetchInBrowser, run };
+export { ensure, fetch, getRegistry, makeRequestAtoms, prefetch, prefetchInBrowser, run };

package/dist/{TanStackRouter.mjs → tanstack-router.mjs}

@@ -5,7 +5,7 @@ import * as Predicate from "effect/Predicate";
 import { RegistryContext } from "@effect/atom-react";
 import * as React from "react";
 import { jsx } from "react/jsx-runtime";
-// src/TanStackRouter.tsx
+// src/tanstack-router.tsx
 /**
 * Connects the loader verbs to TanStack Router and TanStack Start.
 *

package/dist/{Hooks.d.mts → use-atom-result.d.mts}

@@ -1,11 +1,11 @@
-import { ErrorOf, Handle, Source, SuccessOf } from "./Handle.mjs";
+import { ErrorOf, Handle, Source, SuccessOf } from "./handle.mjs";
 import { SettledResult } from "./Loader.mjs";
 import * as Atom from "effect/reactivity/Atom";
 import * as AsyncResult from "effect/reactivity/AsyncResult";
 /**
  * A source with the same arguments and success type as `S`, and any error:
- * the sources whose handles `S` reads, such as the source an error
- * boundary's `wrap(S)` wraps.
+ * the sources whose handles `S` reads, such as the source a derived `S`
+ * points at.
  */
 type Readable<S> = S extends ((...args: infer Args) => Atom.Atom<AsyncResult.AsyncResult<infer A, infer _E>>) ? (...args: Args) => Atom.Atom<AsyncResult.AsyncResult<A, unknown>> : S extends Atom.Atom<AsyncResult.AsyncResult<infer A, infer _E>> ? Atom.Atom<AsyncResult.AsyncResult<A, unknown>> : never;
 /**
@@ -16,8 +16,9 @@ type Readable<S> = S extends ((...args: infer Args) => Atom.Atom<AsyncResult.Asy
  *
  * Use in the component a loader, a server component or `useWaterfall` gave
  * the handle to. The source can be the one the verb started, or one derived
- * from it whose atoms point at its atoms with `initialValueTarget`, such as
- * an error boundary's `wrap(source)`.
+ * from it whose atoms point at its atoms with `initialValueTarget`. To send
+ * some failures to an error boundary, pass the result to the boundary's hook,
+ * such as `useIssueBoundary(useAtomResult(issue, handle))`.
  *
  * **Details**
  *
@@ -38,8 +39,8 @@ type Readable<S> = S extends ((...args: infer Args) => Atom.Atom<AsyncResult.Asy
  *   `initialValueTarget` chain points at: that one is awaited, hydrated and
  *   released, so the derived atom doesn't request it again.
  * - The settled result is returned, typed failures included. A defect is
- *   thrown to the error boundaries above. With no typed failures left, such
- *   as an atom whose boundaries claim all of them, it's typed as a success.
+ *   thrown to the error boundaries above. With no typed failures, it's typed
+ *   as a success.
  * - While a failed atom refreshes, such as after a boundary's `reset`, the
  *   read suspends instead of returning the old failure again.
  *
@@ -64,8 +65,8 @@ type Readable<S> = S extends ((...args: infer Args) => Atom.Atom<AsyncResult.Asy
  * `Atom.transform`'s `initialValueTarget` option points at the end of the
  * target's own chain, which for an AtomRpc query with `reactivityKeys` is an
  * inner atom with no serialization key. A derived atom read here sets
- * `initialValueTarget` to its source itself, as an error boundary's
- * wrapper does, or it requests the source again after hydration.
+ * `initialValueTarget` to its source itself, or it requests the source again
+ * after hydration.
  *
  * **Example**
  *
@@ -86,4 +87,59 @@ type Readable<S> = S extends ((...args: infer Args) => Atom.Atom<AsyncResult.Asy
  * @since 0.1.0
  */
 export declare const useAtomResult: <S extends Source>(source: S, handle: NoInfer<Handle<Readable<S>>>) => [ErrorOf<S>] extends [never] ? AsyncResult.Success<SuccessOf<S>, never> : SettledResult<SuccessOf<S>, ErrorOf<S>>;
+/**
+ * Reads a handle without React Suspense, through the source that made it,
+ * and returns the atom's current result as it is.
+ *
+ * **When to use**
+ *
+ * Use where a component renders every state of the read itself: its loading
+ * state, a failure that stays on the page while the atom refreshes, or a
+ * defect. Otherwise prefer `useAtomResult`, which suspends until the result
+ * settles and sends defects to the error boundaries above.
+ *
+ * **Details**
+ *
+ * - It reads the atom as `useAtomResult` does: through `hydrated`, through
+ *   the serializable atom a derived source points at, and with the same
+ *   development checks on the handle's key and on request waterfalls.
+ * - It returns `Initial` while the atom loads, and while a result the server
+ *   was still loading streams in. It doesn't read the atom until the stream
+ *   settles, so the browser doesn't request it a second time.
+ * - A failure is returned as it is, `waiting` while the atom refreshes, and
+ *   so is a defect.
+ * - Once the component has subscribed to the atom, the loader's lease ends
+ *   and the component keeps the atom mounted.
+ * - A handle `Loader.prefetchInBrowser` returned on the server reads as
+ *   `Initial` there, without starting the atom; the browser's read starts
+ *   it.
+ *
+ * **Gotchas**
+ *
+ * The server renders what the read returns, `Initial` for a result still
+ * loading, and the browser's first render has to match it: render the same
+ * loading state for every `Initial`.
+ *
+ * During server rendering, the registry must be a request registry (see
+ * `RequestRegistry.make`): in development, the hook throws without one.
+ *
+ * **Example**
+ *
+ * ```tsx
+ * import { AsyncResult } from "effect/reactivity"
+ * import { type Handle, useHandleValue } from "raf-effect-atom"
+ *
+ * function IssueTitle(props: { readonly issue: Handle<typeof issue> }) {
+ *   const result = useHandleValue(issue, props.issue)
+ *   return AsyncResult.isSuccess(result) ? <h1>{result.value.title}</h1> : <p>Loading…</p>
+ * }
+ * ```
+ *
+ * @see {@link useAtomResult} for a read that suspends until the result settles
+ *
+ * @stability unstable
+ * @category hooks
+ * @since 0.3.1
+ */
+export declare const useHandleValue: <S extends Source>(source: S, handle: NoInfer<Handle<Readable<S>>>) => AsyncResult.AsyncResult<SuccessOf<S>, ErrorOf<S>>;
 export {};

package/dist/{Hooks.mjs → use-atom-result.mjs}

@@ -1,24 +1,37 @@
 "use client";
-import { stream } from "./internal/pending.mjs";
+import { get, stream } from "./internal/pending.mjs";
 import { hydrated } from "./Hydration.mjs";
 import { keyOf, release } from "./internal/leases.mjs";
 import { atomOf, sourceOf } from "./internal/handles.mjs";
 import { isRequestRegistry } from "./RequestRegistry.mjs";
 import { requireRequestRegistry } from "./internal/registry.mjs";
 import { ModeContext, check } from "./internal/waterfalls.mjs";
+import * as Atom from "effect/reactivity/Atom";
 import * as Predicate from "effect/Predicate";
 import * as Cause from "effect/Cause";
 import * as Option from "effect/Option";
 import * as AsyncResult from "effect/reactivity/AsyncResult";
-import { RegistryContext, useAtomSuspense } from "@effect/atom-react";
+import { RegistryContext, useAtomSuspense, useAtomValue } from "@effect/atom-react";
 import * as React from "react";
-// src/Hooks.ts
+// src/use-atom-result.ts
 /**
-* The read hook for atoms started by loaders and streamed from the server.
+* The read hooks for atoms started by loaders and streamed from the server.
 *
 * @stability unstable
 * @since 0.1.0
 */
+const targetsOf = (atom, handle, hook) => {
+	const target = sourceOf(atom);
+	const started = hydrated(target);
+	const read = target === atom ? hydrated(atom) : atom;
+	const key = keyOf(started);
+	if (process.env.NODE_ENV !== "production" && handle.key !== void 0 && Predicate.isString(key) && handle.key !== key) throw new Error(`raf-effect-atom: ${hook} read the handle of ${handle.key} through a source that makes ${key}. Read a handle through the source that made it.`);
+	return {
+		key,
+		read,
+		started
+	};
+};
 /**
 * Reads a handle through React Suspense, through the source that made it: a
 * result streamed from the server, a hydrated one, or one a loader started.
@@ -27,8 +40,9 @@ import * as React from "react";
 *
 * Use in the component a loader, a server component or `useWaterfall` gave
 * the handle to. The source can be the one the verb started, or one derived
-* from it whose atoms point at its atoms with `initialValueTarget`, such as
-* an error boundary's `wrap(source)`.
+* from it whose atoms point at its atoms with `initialValueTarget`. To send
+* some failures to an error boundary, pass the result to the boundary's hook,
+* such as `useIssueBoundary(useAtomResult(issue, handle))`.
 *
 * **Details**
 *
@@ -49,8 +63,8 @@ import * as React from "react";
 *   `initialValueTarget` chain points at: that one is awaited, hydrated and
 *   released, so the derived atom doesn't request it again.
 * - The settled result is returned, typed failures included. A defect is
-*   thrown to the error boundaries above. With no typed failures left, such
-*   as an atom whose boundaries claim all of them, it's typed as a success.
+*   thrown to the error boundaries above. With no typed failures, it's typed
+*   as a success.
 * - While a failed atom refreshes, such as after a boundary's `reset`, the
 *   read suspends instead of returning the old failure again.
 *
@@ -75,8 +89,8 @@ import * as React from "react";
 * `Atom.transform`'s `initialValueTarget` option points at the end of the
 * target's own chain, which for an AtomRpc query with `reactivityKeys` is an
 * inner atom with no serialization key. A derived atom read here sets
-* `initialValueTarget` to its source itself, as an error boundary's
-* wrapper does, or it requests the source again after hydration.
+* `initialValueTarget` to its source itself, or it requests the source again
+* after hydration.
 *
 * **Example**
 *
@@ -101,12 +115,9 @@ const useAtomResult = (source, handle) => {
 	const atom = atomOf(source, handle.args);
 	requireRequestRegistry(registry, "useAtomResult");
 	if (handle.inBrowser === true && isRequestRegistry(registry)) throw new Error(`raf-effect-atom: ${String(atom)} starts in the browser (Loader.prefetchInBrowser), so the server renders the nearest Suspense boundary's fallback, and the browser renders the boundary.`);
-	const target = sourceOf(atom);
-	const started = hydrated(target);
-	const read = target === atom ? hydrated(atom) : atom;
-	const key = keyOf(started);
-	if (process.env.NODE_ENV !== "production" && handle.key !== void 0 && Predicate.isString(key) && handle.key !== key) throw new Error(`raf-effect-atom: useAtomResult read the handle of ${handle.key} through a source that makes ${key}. Read a handle through the source that made it.`);
-	const streamed = Predicate.isString(key) ? stream(registry, key) : void 0;
+	const targets = targetsOf(atom, handle, "useAtomResult");
+	const { read, started } = targets;
+	const streamed = Predicate.isString(targets.key) ? stream(registry, targets.key) : void 0;
 	if (streamed !== void 0) React.use(streamed);
 	if (process.env.NODE_ENV !== "production" && handle.inBrowser !== true) check(registry, started, React.use(ModeContext));
 	if (read !== started) registry.get(started);
@@ -121,4 +132,94 @@ const useAtomResult = (source, handle) => {
 	if (AsyncResult.isFailure(result) && Option.isNone(Cause.findErrorOption(result.cause))) throw Cause.squash(result.cause);
 	return result;
 };
-export { useAtomResult };
+/** What a read shows while it can't read the atom yet. */
+const loading = Atom.make(AsyncResult.initial(true));
+/**
+* Reads a handle without React Suspense, through the source that made it,
+* and returns the atom's current result as it is.
+*
+* **When to use**
+*
+* Use where a component renders every state of the read itself: its loading
+* state, a failure that stays on the page while the atom refreshes, or a
+* defect. Otherwise prefer `useAtomResult`, which suspends until the result
+* settles and sends defects to the error boundaries above.
+*
+* **Details**
+*
+* - It reads the atom as `useAtomResult` does: through `hydrated`, through
+*   the serializable atom a derived source points at, and with the same
+*   development checks on the handle's key and on request waterfalls.
+* - It returns `Initial` while the atom loads, and while a result the server
+*   was still loading streams in. It doesn't read the atom until the stream
+*   settles, so the browser doesn't request it a second time.
+* - A failure is returned as it is, `waiting` while the atom refreshes, and
+*   so is a defect.
+* - Once the component has subscribed to the atom, the loader's lease ends
+*   and the component keeps the atom mounted.
+* - A handle `Loader.prefetchInBrowser` returned on the server reads as
+*   `Initial` there, without starting the atom; the browser's read starts
+*   it.
+*
+* **Gotchas**
+*
+* The server renders what the read returns, `Initial` for a result still
+* loading, and the browser's first render has to match it: render the same
+* loading state for every `Initial`.
+*
+* During server rendering, the registry must be a request registry (see
+* `RequestRegistry.make`): in development, the hook throws without one.
+*
+* **Example**
+*
+* ```tsx
+* import { AsyncResult } from "effect/reactivity"
+* import { type Handle, useHandleValue } from "raf-effect-atom"
+*
+* function IssueTitle(props: { readonly issue: Handle<typeof issue> }) {
+*   const result = useHandleValue(issue, props.issue)
+*   return AsyncResult.isSuccess(result) ? <h1>{result.value.title}</h1> : <p>Loading…</p>
+* }
+* ```
+*
+* @see {@link useAtomResult} for a read that suspends until the result settles
+*
+* @stability unstable
+* @category hooks
+* @since 0.3.1
+*/
+const useHandleValue = (source, handle) => {
+	const registry = React.useContext(RegistryContext);
+	const atom = atomOf(source, handle.args);
+	requireRequestRegistry(registry, "useHandleValue");
+	const targets = targetsOf(atom, handle, "useHandleValue");
+	const { started } = targets;
+	const streamed = Predicate.isString(targets.key) ? get(registry, targets.key) : void 0;
+	const [, settled] = React.useReducer((count) => count + 1, 0);
+	React.useEffect(() => {
+		if (streamed === void 0) return;
+		let active = true;
+		const rerender = () => {
+			if (active) settled();
+		};
+		streamed.then(rerender, rerender);
+		return () => {
+			active = false;
+		};
+	}, [streamed]);
+	const waiting = streamed !== void 0 || handle.inBrowser === true && isRequestRegistry(registry);
+	if (!waiting) {
+		if (process.env.NODE_ENV !== "production" && handle.inBrowser !== true) check(registry, started, React.use(ModeContext));
+		if (targets.read !== started) registry.get(started);
+	}
+	const result = useAtomValue(waiting ? loading : targets.read);
+	React.useEffect(() => {
+		if (!waiting) release(registry, started);
+	}, [
+		registry,
+		started,
+		waiting
+	]);
+	return result;
+};
+export { useAtomResult, useHandleValue };

package/dist/{Waterfalls.d.mts → waterfalls.d.mts}

@@ -1,4 +1,4 @@
-import { ArgsOf, Handle, Source } from "./Handle.mjs";
+import { ArgsOf, Handle, Source } from "./handle.mjs";
 import { Mode } from "./internal/waterfalls.mjs";
 import * as React from "react";
 /**
@@ -72,9 +72,8 @@ export declare const WaterfallDetection: (props: {
  * - `useAtomResult` doesn't report an atom started this way.
  * - The handle is a prefetched one: its reader suspends until the result
  *   settles, as for a handle from a loader's `prefetch`.
- * - A derived source, such as an error boundary's `wrap(source)`, starts
- *   the serializable atom its `initialValueTarget` chain points at, as
- *   `Loader.prefetch` does.
+ * - A derived source starts the serializable atom its `initialValueTarget`
+ *   chain points at, as `Loader.prefetch` does.
  *
  * **Example**
  *

package/dist/{Waterfalls.mjs → waterfalls.mjs}

@@ -11,7 +11,7 @@ import * as AtomRegistry from "effect/reactivity/AtomRegistry";
 import { RegistryContext } from "@effect/atom-react";
 import * as React from "react";
 import { jsx } from "react/jsx-runtime";
-// src/Waterfalls.tsx
+// src/waterfalls.tsx
 /**
 * Request waterfalls: the escape hatch for atoms only a render can start,
 * and the development check that finds the others.
@@ -76,9 +76,8 @@ const WaterfallDetection = (props) => process.env.NODE_ENV === "production" ? pr
 * - `useAtomResult` doesn't report an atom started this way.
 * - The handle is a prefetched one: its reader suspends until the result
 *   settles, as for a handle from a loader's `prefetch`.
-* - A derived source, such as an error boundary's `wrap(source)`, starts
-*   the serializable atom its `initialValueTarget` chain points at, as
-*   `Loader.prefetch` does.
+* - A derived source starts the serializable atom its `initialValueTarget`
+*   chain points at, as `Loader.prefetch` does.
 *
 * **Example**
 *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "raf-effect-atom",
-  "version": "0.2.6",
+  "version": "0.3.1",
   "description": "Render-as-you-fetch for Effect Atom: start atoms from route loaders and stream them into the browser, typed failures intact",
   "keywords": [
     "effect",
@@ -33,10 +33,13 @@
   "type": "module",
   "sideEffects": false,
   "exports": {
-    ".": "./dist/index.mjs",
-    "./next": "./dist/Next.mjs",
-    "./react-router": "./dist/ReactRouter.mjs",
-    "./tanstack-router": "./dist/TanStackRouter.mjs"
+    ".": {
+      "react-server": "./dist/index-react-server.mjs",
+      "default": "./dist/index.mjs"
+    },
+    "./react-router": "./dist/react-router.mjs",
+    "./rsc": "./dist/rsc.mjs",
+    "./tanstack-router": "./dist/tanstack-router.mjs"
   },
   "peerDependencies": {
     "@effect/atom-react": "^4.0.6",
@@ -58,7 +61,7 @@
     "@types/react-dom": "19.3.0",
     "@vitest/coverage-v8": "5.0.5",
     "effect": "4.0.6",
-    "effect-atom-boundary": "0.1.2",
+    "effect-atom-boundary": "0.3.0",
     "happy-dom": "21.0.4",
     "react": "19.3.1",
     "react-dom": "19.3.1",

package/dist/NextClient.d.mts

@@ -1,32 +0,0 @@
-import { HydrationBoundaryProps } from "./ReactHydration.mjs";
-import * as React from "react";
-/**
- * Hydrates the state a server component dehydrated with `await dehydrate()`,
- * streamed results included.
- *
- * **Details**
- *
- * React serializes the state's promises with the server component's
- * payload, so a result still loading streams in when it settles, and
- * `useAtomResult` waits for it instead of requesting it again.
- *
- * **Example**
- *
- * ```tsx
- * import { dehydrate, ensure, HydrateAtoms } from "raf-effect-atom/next"
- *
- * export default async function IssuePage(props: { params: Promise<{ id: string }> }) {
- *   const handle = await ensure(issue, Number((await props.params).id))
- *   return (
- *     <HydrateAtoms state={await dehydrate()}>
- *       <Issue issue={handle} />
- *     </HydrateAtoms>
- *   )
- * }
- * ```
- *
- * @stability unstable
- * @category components
- * @since 0.1.0
- */
-export declare const HydrateAtoms: (props: HydrationBoundaryProps) => React.ReactNode;

package/dist/NextClient.mjs

@@ -1,44 +0,0 @@
-"use client";
-import { HydrationBoundary } from "./ReactHydration.mjs";
-import { jsx } from "react/jsx-runtime";
-// src/NextClient.tsx
-/**
-* The client components of `raf-effect-atom/next`.
-*
-* @stability unstable
-* @since 0.1.0
-*/
-/**
-* Hydrates the state a server component dehydrated with `await dehydrate()`,
-* streamed results included.
-*
-* **Details**
-*
-* React serializes the state's promises with the server component's
-* payload, so a result still loading streams in when it settles, and
-* `useAtomResult` waits for it instead of requesting it again.
-*
-* **Example**
-*
-* ```tsx
-* import { dehydrate, ensure, HydrateAtoms } from "raf-effect-atom/next"
-*
-* export default async function IssuePage(props: { params: Promise<{ id: string }> }) {
-*   const handle = await ensure(issue, Number((await props.params).id))
-*   return (
-*     <HydrateAtoms state={await dehydrate()}>
-*       <Issue issue={handle} />
-*     </HydrateAtoms>
-*   )
-* }
-* ```
-*
-* @stability unstable
-* @category components
-* @since 0.1.0
-*/
-const HydrateAtoms = (props) => /* @__PURE__ */ jsx(HydrationBoundary, {
-	state: props.state,
-	children: props.children
-});
-export { HydrateAtoms };

package/dist/ReactHydration.d.mts

@@ -1,58 +0,0 @@
-import * as Hydration from "effect/reactivity/Hydration";
-import * as React from "react";
-/**
- * Props for `HydrationBoundary`.
- *
- * @stability unstable
- * @category models
- * @since 0.1.0
- */
-export interface HydrationBoundaryProps {
-  readonly children?: React.ReactNode | undefined;
-  /** The state `Hydration.dehydrate` returned on the server. */
-  readonly state?: Iterable<Hydration.DehydratedAtom> | undefined;
-}
-/**
- * Hydrates the state a server registry dehydrated, streamed results
- * included.
- *
- * **When to use**
- *
- * Use where the server's state reaches the React tree as a prop, such as
- * React Server Components props or a React Router loader's data. A router
- * that hydrates before rendering calls `Hydration.hydrate` instead.
- *
- * **Details**
- *
- * Settled values go to `@effect/atom-react`'s `HydrationBoundary`, which
- * hydrates new atoms during render and existing ones after commit. Each
- * streamed result is held until it arrives, so `useAtomResult` waits for it
- * instead of requesting it again.
- *
- * During server rendering, when `state` is the array `dehydrate` returned,
- * as React Router passes a loader's data to the server render, the children
- * read the registry it came from instead of a copy. The loaders' atoms are
- * there, so an `effect-atom-boundary` boundary sees their failures before
- * its children read them and renders its handler on the server.
- *
- * **Gotchas**
- *
- * In development, it throws during server rendering when the registry isn't
- * a request registry, such as `@effect/atom-react`'s default one, which
- * every request shares: one request's state would reach the others.
- *
- * **Example**
- *
- * ```tsx
- * import { HydrationBoundary } from "raf-effect-atom"
- *
- * <HydrationBoundary state={loaderData.atoms}>
- *   <IssuePage issue={loaderData.issue} />
- * </HydrationBoundary>
- * ```
- *
- * @stability unstable
- * @category components
- * @since 0.1.0
- */
-export declare const HydrationBoundary: (props: HydrationBoundaryProps) => React.ReactNode;