@nifrajs/web-react 0.1.0-alpha.4 → 0.1.0-alpha.5

package/dist/react-dom-server.d.ts

@@ -12,11 +12,15 @@
  * dispatcher, no crash. (Empirically verified against a two-copy install fixture — see
  * test/dual-react.test.ts.)
  *
- * Guarding precisely so the PRODUCTION/BUILT path is untouched: when `Bun.resolveSync` is unavailable
- * (Node / Deno / Cloudflare / Vercel / any bundled output), the build has already bundled+deduped a single
- * `react-dom` (buildServer's `reactDedupePlugin` pins `react`), so the static `import` is correct AND is
- * the only thing that works without a Bun resolver. We fall back to it there. The app-root resolution runs
- * ONLY under the Bun runtime, where the duplication can occur and `Bun.resolveSync` exists.
+ * Guarding precisely so the BUILT path is untouched: a bundle is detected two ways — `Bun.resolveSync` is
+ * unavailable (Node / Deno / Cloudflare / Vercel), OR `buildServer` tagged the output with
+ * `process.env.NIFRA_SSR_BUNDLED` (a `target:"bun"` bundle DOES keep `Bun.resolveSync` under the Bun
+ * runtime, so the resolver test alone can't see it). In either case the build already bundled+deduped a
+ * single `react-dom` (buildServer's `reactDedupePlugin` pins `react`), so the static `import` is correct.
+ * Re-rooting a bundle would instead re-import a SECOND react-dom from disk — a second React core whose hook
+ * dispatcher is null for the bundled components → the `…H.useRef of null` SSR crash. The app-root re-root
+ * therefore runs ONLY under an UNBUNDLED Bun runtime (nifra dev/start, nifra_render), where the duplication
+ * can occur, `Bun.resolveSync` exists, and no bundle marker is present.
  */
 import type { ReactNode } from "react";
 /** The slice of `react-dom/server` this adapter uses. Typed locally so the dynamic import (which Bun
@@ -40,5 +44,15 @@ type ResolveSync = (specifier: string, from: string) => string;
  * without depending on the machine's node_modules layout.
  */
 export declare function loadReactDomServer(resolve?: ResolveSync | undefined): Promise<ReactDomServer>;
+/**
+ * The resolver `loadReactDomServer` uses by default, or `undefined` when re-rooting must NOT happen — a
+ * non-Bun host (no `Bun.resolveSync`; the static import is the only path) OR a BUNDLED SSR output.
+ * `buildServer` defines `process.env.NIFRA_SSR_BUNDLED` to `"1"` in every bundle, where react-dom is
+ * already inlined + deduped to the components' React (reactDedupePlugin); re-rooting there would re-import
+ * a SECOND react-dom from disk (a `target:"bun"` bundle still has `Bun.resolveSync`), giving the bundled
+ * components a foreign/null hook dispatcher → the `…H.useRef of null` crash. The marker is read here (per
+ * call, not at module load) so it stays driveable from a test. Unbundled Bun runtimes don't set it, so
+ * dev/start still re-root. Exported for unit testing the gate. */
+export declare function bunResolverFn(): ResolveSync | undefined;
 export {};
 //# sourceMappingURL=react-dom-server.d.ts.map

package/dist/react-dom-server.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"react-dom-server.d.ts","sourceRoot":"","sources":["../src/react-dom-server.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AAEH,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,OAAO,CAAA;AAEtC;wFACwF;AACxF,MAAM,WAAW,cAAc;IAC7B,cAAc,CAAC,IAAI,EAAE,SAAS,GAAG,MAAM,CAAA;IACvC,sBAAsB,CAAC,IAAI,EAAE,SAAS,GAAG,OAAO,CAAC,cAAc,CAAC,UAAU,CAAC,CAAC,CAAA;CAC7E;AA4BD;;;;GAIG;AACH,wBAAgB,cAAc,IAAI,OAAO,CAAC,cAAc,CAAC,CAIxD;AAED,6EAA6E;AAC7E,KAAK,WAAW,GAAG,CAAC,SAAS,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,KAAK,MAAM,CAAA;AAE9D;;;;;GAKG;AACH,wBAAsB,kBAAkB,CACtC,OAAO,GAAE,WAAW,GAAG,SAA2B,GACjD,OAAO,CAAC,cAAc,CAAC,CAiBzB"}
+{"version":3,"file":"react-dom-server.d.ts","sourceRoot":"","sources":["../src/react-dom-server.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AAEH,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,OAAO,CAAA;AAEtC;wFACwF;AACxF,MAAM,WAAW,cAAc;IAC7B,cAAc,CAAC,IAAI,EAAE,SAAS,GAAG,MAAM,CAAA;IACvC,sBAAsB,CAAC,IAAI,EAAE,SAAS,GAAG,OAAO,CAAC,cAAc,CAAC,UAAU,CAAC,CAAC,CAAA;CAC7E;AA4BD;;;;GAIG;AACH,wBAAgB,cAAc,IAAI,OAAO,CAAC,cAAc,CAAC,CAIxD;AAED,6EAA6E;AAC7E,KAAK,WAAW,GAAG,CAAC,SAAS,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,KAAK,MAAM,CAAA;AAE9D;;;;;GAKG;AACH,wBAAsB,kBAAkB,CACtC,OAAO,GAAE,WAAW,GAAG,SAA2B,GACjD,OAAO,CAAC,cAAc,CAAC,CAiBzB;AAED;;;;;;;;kEAQkE;AAClE,wBAAgB,aAAa,IAAI,WAAW,GAAG,SAAS,CAKvD"}

package/dist/react-dom-server.js

@@ -12,11 +12,15 @@
  * dispatcher, no crash. (Empirically verified against a two-copy install fixture — see
  * test/dual-react.test.ts.)
  *
- * Guarding precisely so the PRODUCTION/BUILT path is untouched: when `Bun.resolveSync` is unavailable
- * (Node / Deno / Cloudflare / Vercel / any bundled output), the build has already bundled+deduped a single
- * `react-dom` (buildServer's `reactDedupePlugin` pins `react`), so the static `import` is correct AND is
- * the only thing that works without a Bun resolver. We fall back to it there. The app-root resolution runs
- * ONLY under the Bun runtime, where the duplication can occur and `Bun.resolveSync` exists.
+ * Guarding precisely so the BUILT path is untouched: a bundle is detected two ways — `Bun.resolveSync` is
+ * unavailable (Node / Deno / Cloudflare / Vercel), OR `buildServer` tagged the output with
+ * `process.env.NIFRA_SSR_BUNDLED` (a `target:"bun"` bundle DOES keep `Bun.resolveSync` under the Bun
+ * runtime, so the resolver test alone can't see it). In either case the build already bundled+deduped a
+ * single `react-dom` (buildServer's `reactDedupePlugin` pins `react`), so the static `import` is correct.
+ * Re-rooting a bundle would instead re-import a SECOND react-dom from disk — a second React core whose hook
+ * dispatcher is null for the bundled components → the `…H.useRef of null` SSR crash. The app-root re-root
+ * therefore runs ONLY under an UNBUNDLED Bun runtime (nifra dev/start, nifra_render), where the duplication
+ * can occur, `Bun.resolveSync` exists, and no bundle marker is present.
  */
 var __rewriteRelativeImportExtension = (this && this.__rewriteRelativeImportExtension) || function (path, preserveJsx) {
     if (typeof path === "string" && /^\.\.?\//.test(path)) {
@@ -78,8 +82,18 @@ export async function loadReactDomServer(resolve = bunResolverFn()) {
     // bundler include it (it's a constant), and at runtime resolves the copy visible to this package.
     return (await import("react-dom/server"));
 }
-/** The ambient `Bun.resolveSync`, or undefined on a non-Bun host (where the static import is the only path). */
-function bunResolverFn() {
+/**
+ * The resolver `loadReactDomServer` uses by default, or `undefined` when re-rooting must NOT happen — a
+ * non-Bun host (no `Bun.resolveSync`; the static import is the only path) OR a BUNDLED SSR output.
+ * `buildServer` defines `process.env.NIFRA_SSR_BUNDLED` to `"1"` in every bundle, where react-dom is
+ * already inlined + deduped to the components' React (reactDedupePlugin); re-rooting there would re-import
+ * a SECOND react-dom from disk (a `target:"bun"` bundle still has `Bun.resolveSync`), giving the bundled
+ * components a foreign/null hook dispatcher → the `…H.useRef of null` crash. The marker is read here (per
+ * call, not at module load) so it stays driveable from a test. Unbundled Bun runtimes don't set it, so
+ * dev/start still re-root. Exported for unit testing the gate. */
+export function bunResolverFn() {
+    if (process.env.NIFRA_SSR_BUNDLED === "1")
+        return undefined;
     return hasBunResolveSync && bunResolver?.resolveSync !== undefined
         ? bunResolver.resolveSync.bind(bunResolver)
         : undefined;

package/dist/react-dom-server.js.map

@@ -1 +1 @@
-{"version":3,"file":"react-dom-server.js","sourceRoot":"","sources":["../src/react-dom-server.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;;;;;;;;;AAkBH,MAAM,WAAW,GAAI,UAA6C,CAAC,GAAG,CAAA;AACtE,MAAM,iBAAiB,GAAG,OAAO,WAAW,EAAE,WAAW,KAAK,UAAU,CAAA;AAExE,uGAAuG;AACvG,qGAAqG;AACrG,8EAA8E;AAC9E,IAAI,MAA2C,CAAA;AAE/C;;;;;;GAMG;AACH,SAAS,OAAO;IACd,OAAO,OAAO,CAAC,GAAG,EAAE,CAAA;AACtB,CAAC;AAED;;;;GAIG;AACH,MAAM,UAAU,cAAc;IAC5B,IAAI,MAAM,KAAK,SAAS;QAAE,OAAO,MAAM,CAAA;IACvC,MAAM,GAAG,kBAAkB,EAAE,CAAA;IAC7B,OAAO,MAAM,CAAA;AACf,CAAC;AAKD;;;;;GAKG;AACH,MAAM,CAAC,KAAK,UAAU,kBAAkB,CACtC,UAAmC,aAAa,EAAE;IAElD,IAAI,OAAO,KAAK,SAAS,EAAE,CAAC;QAC1B,oGAAoG;QACpG,8FAA8F;QAC9F,oGAAoG;QACpG,iFAAiF;QACjF,IAAI,CAAC;YACH,MAAM,QAAQ,GAAG,OAAO,CAAC,kBAAkB,EAAE,OAAO,EAAE,CAAC,CAAA;YACvD,OAAO,CAAC,MAAM,MAAM,kCAAC,QAAQ,EAAC,CAAmB,CAAA;QACnD,CAAC;QAAC,MAAM,CAAC;YACP,gGAAgG;QAClG,CAAC;IACH,CAAC;IACD,8FAA8F;IAC9F,oGAAoG;IACpG,kGAAkG;IAClG,OAAO,CAAC,MAAM,MAAM,CAAC,kBAAkB,CAAC,CAAmB,CAAA;AAC7D,CAAC;AAED,gHAAgH;AAChH,SAAS,aAAa;IACpB,OAAO,iBAAiB,IAAI,WAAW,EAAE,WAAW,KAAK,SAAS;QAChE,CAAC,CAAC,WAAW,CAAC,WAAW,CAAC,IAAI,CAAC,WAAW,CAAC;QAC3C,CAAC,CAAC,SAAS,CAAA;AACf,CAAC"}
+{"version":3,"file":"react-dom-server.js","sourceRoot":"","sources":["../src/react-dom-server.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;GAuBG;;;;;;;;;AAkBH,MAAM,WAAW,GAAI,UAA6C,CAAC,GAAG,CAAA;AACtE,MAAM,iBAAiB,GAAG,OAAO,WAAW,EAAE,WAAW,KAAK,UAAU,CAAA;AAExE,uGAAuG;AACvG,qGAAqG;AACrG,8EAA8E;AAC9E,IAAI,MAA2C,CAAA;AAE/C;;;;;;GAMG;AACH,SAAS,OAAO;IACd,OAAO,OAAO,CAAC,GAAG,EAAE,CAAA;AACtB,CAAC;AAED;;;;GAIG;AACH,MAAM,UAAU,cAAc;IAC5B,IAAI,MAAM,KAAK,SAAS;QAAE,OAAO,MAAM,CAAA;IACvC,MAAM,GAAG,kBAAkB,EAAE,CAAA;IAC7B,OAAO,MAAM,CAAA;AACf,CAAC;AAKD;;;;;GAKG;AACH,MAAM,CAAC,KAAK,UAAU,kBAAkB,CACtC,UAAmC,aAAa,EAAE;IAElD,IAAI,OAAO,KAAK,SAAS,EAAE,CAAC;QAC1B,oGAAoG;QACpG,8FAA8F;QAC9F,oGAAoG;QACpG,iFAAiF;QACjF,IAAI,CAAC;YACH,MAAM,QAAQ,GAAG,OAAO,CAAC,kBAAkB,EAAE,OAAO,EAAE,CAAC,CAAA;YACvD,OAAO,CAAC,MAAM,MAAM,kCAAC,QAAQ,EAAC,CAAmB,CAAA;QACnD,CAAC;QAAC,MAAM,CAAC;YACP,gGAAgG;QAClG,CAAC;IACH,CAAC;IACD,8FAA8F;IAC9F,oGAAoG;IACpG,kGAAkG;IAClG,OAAO,CAAC,MAAM,MAAM,CAAC,kBAAkB,CAAC,CAAmB,CAAA;AAC7D,CAAC;AAED;;;;;;;;kEAQkE;AAClE,MAAM,UAAU,aAAa;IAC3B,IAAI,OAAO,CAAC,GAAG,CAAC,iBAAiB,KAAK,GAAG;QAAE,OAAO,SAAS,CAAA;IAC3D,OAAO,iBAAiB,IAAI,WAAW,EAAE,WAAW,KAAK,SAAS;QAChE,CAAC,CAAC,WAAW,CAAC,WAAW,CAAC,IAAI,CAAC,WAAW,CAAC;QAC3C,CAAC,CAAC,SAAS,CAAA;AACf,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nifrajs/web-react",
-  "version": "0.1.0-alpha.4",
+  "version": "0.1.0-alpha.5",
   "description": "React render adapter for @nifrajs/web — SSR + hydration (Bun-native JSX, no Babel).",
   "keywords": [
     "bun",
@@ -77,7 +77,7 @@
   "dependencies": {
     "@nifrajs/i18n": "0.1.0-alpha.4",
     "@nifrajs/image": "0.1.0-alpha.4",
-    "@nifrajs/web": "0.1.0-alpha.4"
+    "@nifrajs/web": "0.1.0-alpha.5"
   },
   "peerDependencies": {
     "react": "^19.0.0",

package/src/react-dom-server.ts

@@ -12,11 +12,15 @@
  * dispatcher, no crash. (Empirically verified against a two-copy install fixture — see
  * test/dual-react.test.ts.)
  *
- * Guarding precisely so the PRODUCTION/BUILT path is untouched: when `Bun.resolveSync` is unavailable
- * (Node / Deno / Cloudflare / Vercel / any bundled output), the build has already bundled+deduped a single
- * `react-dom` (buildServer's `reactDedupePlugin` pins `react`), so the static `import` is correct AND is
- * the only thing that works without a Bun resolver. We fall back to it there. The app-root resolution runs
- * ONLY under the Bun runtime, where the duplication can occur and `Bun.resolveSync` exists.
+ * Guarding precisely so the BUILT path is untouched: a bundle is detected two ways — `Bun.resolveSync` is
+ * unavailable (Node / Deno / Cloudflare / Vercel), OR `buildServer` tagged the output with
+ * `process.env.NIFRA_SSR_BUNDLED` (a `target:"bun"` bundle DOES keep `Bun.resolveSync` under the Bun
+ * runtime, so the resolver test alone can't see it). In either case the build already bundled+deduped a
+ * single `react-dom` (buildServer's `reactDedupePlugin` pins `react`), so the static `import` is correct.
+ * Re-rooting a bundle would instead re-import a SECOND react-dom from disk — a second React core whose hook
+ * dispatcher is null for the bundled components → the `…H.useRef of null` SSR crash. The app-root re-root
+ * therefore runs ONLY under an UNBUNDLED Bun runtime (nifra dev/start, nifra_render), where the duplication
+ * can occur, `Bun.resolveSync` exists, and no bundle marker is present.
  */
 
 import type { ReactNode } from "react"
@@ -95,8 +99,17 @@ export async function loadReactDomServer(
   return (await import("react-dom/server")) as ReactDomServer
 }
 
-/** The ambient `Bun.resolveSync`, or undefined on a non-Bun host (where the static import is the only path). */
-function bunResolverFn(): ResolveSync | undefined {
+/**
+ * The resolver `loadReactDomServer` uses by default, or `undefined` when re-rooting must NOT happen — a
+ * non-Bun host (no `Bun.resolveSync`; the static import is the only path) OR a BUNDLED SSR output.
+ * `buildServer` defines `process.env.NIFRA_SSR_BUNDLED` to `"1"` in every bundle, where react-dom is
+ * already inlined + deduped to the components' React (reactDedupePlugin); re-rooting there would re-import
+ * a SECOND react-dom from disk (a `target:"bun"` bundle still has `Bun.resolveSync`), giving the bundled
+ * components a foreign/null hook dispatcher → the `…H.useRef of null` crash. The marker is read here (per
+ * call, not at module load) so it stays driveable from a test. Unbundled Bun runtimes don't set it, so
+ * dev/start still re-root. Exported for unit testing the gate. */
+export function bunResolverFn(): ResolveSync | undefined {
+  if (process.env.NIFRA_SSR_BUNDLED === "1") return undefined
   return hasBunResolveSync && bunResolver?.resolveSync !== undefined
     ? bunResolver.resolveSync.bind(bunResolver)
     : undefined