raf-effect-atom 0.3.2 → 0.3.3

package/CHANGELOG.md

@@ -1,10 +1,16 @@
 # Changelog
 
+## [0.3.3](https://github.com/KATT/raf-effect-atom/compare/raf-effect-atom%400.3.2...raf-effect-atom%400.3.3) (2026-10-24)
+
+### Bug Fixes
+
+* **raf-effect-atom:** name the fixes when useAtomResult throws for a browser-only handle on the server ([40b94d0](https://github.com/KATT/raf-effect-atom/commit/40b94d07947b65bb06d278cf47c855f4b8afdc78))
+
 ## [0.3.2](https://github.com/KATT/raf-effect-atom/compare/raf-effect-atom%400.3.1...raf-effect-atom%400.3.2) (2026-10-24)
 
 ### Bug Fixes
 
-* **raf-effect-atom:** take no lease on an atom a mounted component reads ([899d0b7](https://github.com/KATT/raf-effect-atom/commit/899d0b7c70f6836c41c4416b0c2063c1ccf3d8b2))
+- **raf-effect-atom:** take no lease on an atom a mounted component reads ([899d0b7](https://github.com/KATT/raf-effect-atom/commit/899d0b7c70f6836c41c4416b0c2063c1ccf3d8b2))
 
 ## [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)
 

package/dist/use-atom-result.d.mts

@@ -63,6 +63,12 @@ type Readable<S> = S extends ((...args: infer Args) => Atom.Atom<AsyncResult.Asy
  * `RequestRegistry.make`), or a module-level registry would share results
  * between requests: in development, the hook throws without one.
  *
+ * On the server, the hook throws for a handle `Loader.prefetchInBrowser`
+ * returned, so React renders the nearest Suspense boundary's fallback and
+ * reports the error. With no boundary between the read and the route, the
+ * server can't render the page. `useHandleValue` returns `Initial` there
+ * instead.
+ *
  * `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

package/dist/use-atom-result.mjs

@@ -87,6 +87,12 @@ const targetsOf = (atom, handle, hook) => {
 * `RequestRegistry.make`), or a module-level registry would share results
 * between requests: in development, the hook throws without one.
 *
+* On the server, the hook throws for a handle `Loader.prefetchInBrowser`
+* returned, so React renders the nearest Suspense boundary's fallback and
+* reports the error. With no boundary between the read and the route, the
+* server can't render the page. `useHandleValue` returns `Initial` there
+* instead.
+*
 * `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
@@ -115,7 +121,7 @@ const useAtomResult = (source, handle) => {
 	const registry = React.useContext(RegistryContext);
 	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.`);
+	if (handle.inBrowser === true && isRequestRegistry(registry)) throw new Error(`raf-effect-atom: ${String(atom)} starts in the browser (Loader.prefetchInBrowser), so useAtomResult throws on the server: React renders the nearest Suspense boundary's fallback, and the browser renders the boundary. Read it under a Suspense boundary inside the route, or with useHandleValue, which returns Initial on the server.`);
 	const targets = targetsOf(atom, handle, "useAtomResult");
 	const { read, started } = targets;
 	const streamed = Predicate.isString(targets.key) ? stream(registry, targets.key) : void 0;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "raf-effect-atom",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "description": "Render-as-you-fetch for Effect Atom: start atoms from route loaders and stream them into the browser, typed failures intact",
   "keywords": [
     "effect",