@wular/pnext 0.0.18 → 0.0.19

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wular/pnext",
-  "version": "0.0.18",
+  "version": "0.0.19",
   "description": "A fast little framework for server-first React apps, fully compatible with Next.js",
   "type": "module",
   "bin": {

package/src/config.ts

@@ -193,18 +193,27 @@ export function pathToFileHref(filePath: string) {
 }
 
 export function publicEnvDefines() {
-  return Object.fromEntries(
-    [
-      // eslint-disable-next-line turbo/no-undeclared-env-vars
-      ['NODE_ENV', process.env.NODE_ENV ?? 'production'],
-      ...Object.entries(process.env).filter(
-        ([key]) => key.startsWith('NEXT_PUBLIC_') || key.startsWith('PNEXT_PUBLIC_'),
-      ),
-    ].map(([key, value]) => [
-      `process.env.${key}`,
-      value === undefined ? 'undefined' : JSON.stringify(value),
-    ]),
-  )
+  const publicEnv = Object.fromEntries([
+    // eslint-disable-next-line turbo/no-undeclared-env-vars
+    ['NODE_ENV', process.env.NODE_ENV ?? 'production'],
+    ...Object.entries(process.env).filter(
+      ([key]) => key.startsWith('NEXT_PUBLIC_') || key.startsWith('PNEXT_PUBLIC_'),
+    ),
+  ]) as Record<string, string>
+  return {
+    // The whole object, not just the keys that happen to be SET at build time. A browser has no
+    // `process`, so a `NEXT_PUBLIC_*` the source reads but the environment never defined would
+    // otherwise survive as a bare reference and throw ReferenceError on first evaluation - taking
+    // hydration, and every event handler on the page, down with it. Reading a missing key off this
+    // yields undefined, which is what Next inlines for one.
+    'process.env': JSON.stringify(publicEnv),
+    ...Object.fromEntries(
+      Object.entries(publicEnv).map(([key, value]) => [
+        `process.env.${key}`,
+        JSON.stringify(value),
+      ]),
+    ),
+  }
 }
 
 type FrameworkRuntimeAlias =