@nubjs/nub-win32-arm64 0.0.44 → 0.0.45

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nubjs/nub-win32-arm64",
-  "version": "0.0.44",
+  "version": "0.0.45",
   "description": "Nub binary for win32-arm64",
   "license": "MIT",
   "repository": "https://github.com/nubjs/nub",

package/runtime/polyfills.cjs

@@ -32,6 +32,38 @@ const __require = createRequire(__filename);
 function installSyncPolyfills(preloaded) {
   preloaded = preloaded || {};
 
+  // ── Web Storage: neutralize the throwing localStorage getter ────────
+  // When nub injects `--experimental-webstorage` on the 22.4–24 band AND the user
+  // did NOT pass `--localstorage-file`, Node installs a `localStorage` global that
+  // is a getter THROWING `ERR_INVALID_ARG_VALUE` on ANY access — even
+  // `typeof localStorage` throws, so feature-detection is impossible and the throw
+  // can surface before user code expects it. The spawn layer signals this case via
+  // the internal `__NUB_NEUTRALIZE_LOCALSTORAGE` env var (set iff flag-injected ∧
+  // no user file). Replace the throwing getter with a plain `undefined` value —
+  // matching Node 25+'s clean shape — so `typeof localStorage === "undefined"` is
+  // true and no throw occurs; `sessionStorage`, which needs only the flag, keeps
+  // working. This runs in the preload BEFORE any user code, so the throwing getter
+  // is never observed. When the user passes `--localstorage-file`, the env var is
+  // absent and `localStorage` works normally (we do not touch it). We deliberately
+  // KEEP the env var set so it inherits to the whole process subtree: a `node`- or
+  // `nub`-spawned grandchild re-inherits the webstorage flag via NODE_OPTIONS and
+  // would otherwise re-install the throwing getter with no neutralize signal. It's
+  // an internal `__NUB_*` plumbing var that's explicitly fine to leak to children.
+  // Neutralization is idempotent — a descendant re-running this preload with the
+  // var still set just re-defines `localStorage` to undefined again, which is
+  // harmless. The descriptor is configurable+writable so user code can still assign
+  // its own `localStorage`.
+  if (process.env.__NUB_NEUTRALIZE_LOCALSTORAGE) {
+    try {
+      Object.defineProperty(globalThis, "localStorage", {
+        value: undefined,
+        configurable: true,
+        writable: true,
+        enumerable: false,
+      });
+    } catch { /* descriptor non-configurable on this runtime: leave Node's behavior */ }
+  }
+
   // ── reportError (WinterTC min-common-API, not in any Node) ──────────
   // Defined NON-ENUMERABLE so it is invisible to `Object.keys(globalThis)` /
   // for-in / structured-clone-of-keys — that invisibility-to-enumeration IS the

package/runtime/transform-core.mjs

@@ -160,22 +160,6 @@ export const TRANSPILE_EXTS = new Set([".ts", ".tsx", ".mts", ".cts", ".jsx"]);
 export const DATA_EXTS = { ".jsonc": "jsonc", ".json5": "json5", ".toml": "toml", ".yaml": "yaml", ".yml": "yaml", ".txt": "txt" };
 export const TS_PARENT_EXTS = new Set([".ts", ".tsx", ".mts", ".cts"]);
 
-// Reserved words / literals that cannot be a lexical binding name in a module
-// (modules are strict mode). A data file with a top-level key like `package`
-// (e.g. a Cargo.toml `[package]` table) must NOT emit `export const package = …`
-// — that is a SyntaxError that takes down the whole module, default export
-// included. Such keys stay reachable via the default export. Matches bun, which
-// deoptimizes invalid-identifier keys rather than failing the whole module.
-const RESERVED_EXPORT_NAMES = new Set([
-  "break", "case", "catch", "class", "const", "continue", "debugger", "default",
-  "delete", "do", "else", "enum", "export", "extends", "false", "finally", "for",
-  "function", "if", "import", "in", "instanceof", "new", "null", "return", "super",
-  "switch", "this", "throw", "true", "try", "typeof", "var", "void", "while", "with",
-  // Strict-mode (modules are always strict) future-reserved + restricted names:
-  "implements", "interface", "let", "package", "private", "protected", "public",
-  "static", "yield", "await", "eval", "arguments",
-]);
-
 // Packages resolved from Nub's distribution, not the user's.
 export const VENDORED_PACKAGES = new Set(["@oxc-project/runtime"]);
 
@@ -689,15 +673,12 @@ export function loadData(url, ext) {
     return { format: "module", source: "export default undefined;\n", shortCircuit: true };
   }
 
-  let code = `const _data = ${JSON.stringify(parsed)};\nexport default _data;\n`;
-  if (typeof parsed === "object" && !Array.isArray(parsed)) {
-    for (const key of Object.keys(parsed)) {
-      // Emit a named export only for keys that are valid, non-reserved binding
-      // identifiers; everything else remains reachable via the default export.
-      if (/^[a-zA-Z_$][a-zA-Z0-9_$]*$/.test(key) && !RESERVED_EXPORT_NAMES.has(key)) {
-        code += `export const ${key} = _data[${JSON.stringify(key)}];\n`;
-      }
-    }
-  }
+  // Default export only. Data modules deliberately do NOT emit per-key named
+  // exports: named imports of data are categorically un-typeable in TypeScript
+  // (a `declare module "*.yaml"` wildcard has no per-key export index signature),
+  // and default-only matches Node's own JSON modules. Consumers destructure the
+  // default — `import cfg from "./c.yaml"; const { host } = cfg;` — which the
+  // `@nubjs/types` `Record<string, unknown>` default type makes sound.
+  const code = `export default ${JSON.stringify(parsed)};\n`;
   return { format: "module", source: code, shortCircuit: true };
 }

package/runtime/version.mjs

@@ -9,4 +9,4 @@
 // previously lived as a literal inside preload.mjs, which `make version` patched,
 // while the worker carried a hand-maintained "…-compat" copy that `make version`
 // never touched — a latent staleness bug this module closes.)
-export const NUB_VERSION = "0.0.44";
+export const NUB_VERSION = "0.0.45";