@nativescript/vite 8.0.0-alpha.3 → 8.0.0-alpha.31

package/hmr/server/ns-core-cjs-shape.d.ts

@@ -0,0 +1,204 @@
+/**
+ * CJS/ESM interop shape.
+ *
+ * PROBLEM
+ * -------
+ * ESM Module Namespace Objects (ECMA §9.4.6) have [[Prototype]] = null.
+ * They do NOT inherit Object.prototype — no `hasOwnProperty`, no `toString`,
+ * no `isPrototypeOf`. CJS consumers (most notably zone.js's `patchMethod`)
+ * assume their require() result is a plain object that has those methods:
+ *
+ *     let proto = target;
+ *     while (proto && !proto.hasOwnProperty(name)) // ← crashes on null-proto
+ *       proto = Object.getPrototypeOf(proto);
+ *
+ * `@nativescript/core/index.js` re-exports several sub-modules as namespaces:
+ *
+ *     export * as Utils from './utils';
+ *     export * as Http from './http';
+ *     export * as Connectivity from './connectivity';
+ *     export * as ApplicationSettings from './application-settings';
+ *
+ * When bundle.mjs does `import { Utils } from '@nativescript/core'`, `Utils`
+ * binds to that null-proto sub-namespace. zone.js then does
+ * `patchMethod(Utils, 'mainThreadify', …)` and crashes.
+ *
+ * WHY globalThis.require shims ALONE DON'T FIX THIS
+ * -------------------------------------------------
+ * ESM imports never pass through `globalThis.require`. They go through the
+ * host's ESM linker (V8 on iOS). Shimming `require` only intercepts the CJS
+ * path (vendor packages that use `require('@nativescript/core')`); direct
+ * ESM imports of `Utils` still see the raw null-proto namespace.
+ *
+ * THE FIX
+ * -------
+ * Rewrite `export * as X from 'Y'` at the /ns/core bridge response level:
+ *
+ *     // before
+ *     export * as Utils from './utils';
+ *
+ *     // after
+ *     import * as __ns_re_Utils__ from './utils';
+ *     export const Utils = __NS_CJS_SHAPE__(__ns_re_Utils__);
+ *
+ * Now `Utils` is a plain Object (inherits Object.prototype). Zone.js's
+ * `patchMethod(Utils, ...)` succeeds. The shape function is recursive —
+ * nested namespaces get the same treatment — and identity-preserving
+ * (WeakMap-cached) so mutations stick across lookups.
+ *
+ * WHY THE SHAPE INSTALL MUST RUN IN MODULE BODY (NOT FOOTER)
+ * ---------------------------------------------------------
+ * `export const Utils = __NS_CJS_SHAPE__(__ns_re_Utils__)` is body code. It
+ * executes during module evaluation, BEFORE the registration footer. So the
+ * shape function must be installed as a body-level statement that runs
+ * before the rewritten body — we can't rely on the footer's install.
+ *
+ * Each served /ns/core module independently installs the shape function via
+ * an idempotent `|| (globalThis.__NS_CJS_SHAPE__ = ...)` assignment. The
+ * first module to evaluate wins; subsequent evaluations are no-ops. This
+ * also handles dependency-before-importer order (depth-first ESM eval):
+ * `/ns/core/utils` evaluates before `/ns/core` main, so the shape helper
+ * is in place whenever any body needs it.
+ */
+/**
+ * Body-code statements that idempotently install `globalThis.__NS_CJS_SHAPE__`
+ * and `globalThis.__NS_CJS_SHAPE_CACHE__`. Must execute BEFORE any transformed
+ * `export const X = __NS_CJS_SHAPE__(...)` statement in the same module.
+ *
+ * Properties:
+ *   - Recursive: traverses nested namespaces so `Utils.Something` is also
+ *     a plain Object (if that sub-namespace is itself null-proto).
+ *   - Identity-preserving: WeakMap keyed on the underlying ESM namespace.
+ *     zone.js mutates its patch target; a fresh copy per call would lose
+ *     mutations. Every lookup of the same namespace returns the same
+ *     shaped object.
+ *   - Cycle-safe: records the output in the cache BEFORE recursing into
+ *     children. Handles `core ↔ platform` style cycles.
+ *   - TDZ-safe: wraps each property read in try/catch. Some exports
+ *     (Angular zone.js with early-access patterns) are still in their
+ *     temporal dead zone when the namespace is first snapshotted. A thrown
+ *     property read is skipped rather than failing the whole shape.
+ */
+export declare function buildShapeInstallHeader(): string;
+/**
+ * Rewrite namespace re-exports from CJS-incompatible ESM namespace form into
+ * shape-aware const exports. Handles the two forms Vite/esbuild may emit:
+ *
+ *   (1) Original ES2020 syntax preserved unchanged:
+ *       export * as X from 'Y';
+ *
+ *   (2) Transpiled form esbuild emits when targeting older ES:
+ *       import * as _foo from 'Y';
+ *       export { _foo as X };
+ *
+ * Both become:
+ *   import * as __ns_re_X__ from 'Y';
+ *   export const X = __NS_CJS_SHAPE__(__ns_re_X__);
+ *
+ * Notes on the transform:
+ *   - The internal binding uses a derived name (`__ns_re_<X>__`) so
+ *     collisions with user bindings are extremely unlikely. Core doesn't
+ *     declare identifiers matching that shape.
+ *   - `__NS_CJS_SHAPE__` is read from globalThis with a defensive fallback
+ *     (identity function) in case installation failed or runs in an
+ *     environment where it hasn't been initialized yet. This makes the
+ *     transform safe to apply to modules that don't always go through the
+ *     /ns/core handler's headers.
+ *   - We do NOT shape `export *` (star re-exports without alias). Those
+ *     spread individual named exports — they don't create a nested
+ *     namespace and aren't affected by the null-proto issue.
+ *   - We do NOT shape `export { x } from 'y'` forms. Those copy individual
+ *     named exports directly; the consumer never sees the namespace.
+ *
+ * The regex is intentionally precise. It matches only the `export * as X from
+ * 'Y'` syntactic form (and its transpiled equivalent) — no accidental matches
+ * in string literals or comments because those can't start a top-level
+ * statement with `export`.
+ */
+export declare function rewriteNamespaceReExportsForShape(code: string): string;
+/**
+ * Convenience: returns true if the given code appears to contain at least one
+ * namespace re-export that would benefit from the shape transform. Used to
+ * skip the regex replace for modules that don't need it (keeps the response
+ * identical for most submodules, which just have plain `export * from` or
+ * named exports).
+ */
+export declare function hasNamespaceReExport(code: string): boolean;
+/**
+ * Default-export bridge footer.
+ *
+ * BACKGROUND
+ * ----------
+ * Upstream consumer rewrites in the /ns/m handler convert
+ * `import { X } from '@nativescript/core'` into
+ * `import __ns_core_ns from '/ns/core'; const { X } = __ns_core_ns;`
+ * — a DEFAULT import followed by destructuring. The inline comment on that
+ * rewrite says explicitly: "This makes `import { Frame } from
+ * '@nativescript/core'` work even if the bridge provides only a default
+ * export."
+ *
+ * The original `@nativescript/core/index.js` has no `export default` — all
+ * named exports. Without this footer, consumers of the transformed import
+ * fail at ESM link time:
+ *
+ *     SyntaxError: The requested module '/ns/core/<ver>' does not
+ *     provide an export named 'default'
+ *
+ * THE FIX
+ * -------
+ * Emit `export default __ns_core_self_ns__;` at the end of the served
+ * module body. `__ns_core_self_ns__` is the namespace import the server
+ * already emits at the top of every /ns/core response for self-
+ * registration purposes. ESM spec guarantees a module re-entering itself
+ * during evaluation returns the in-progress namespace — so no extra
+ * evaluation occurs, and the default binding receives an object whose
+ * properties are every named export of the same module.
+ *
+ * CONSUMER MATRIX AFTER THIS FIX
+ * ------------------------------
+ *   • `import X from '/ns/core'` (default)     → X = self namespace
+ *   • `import * as X from '/ns/core'`          → X = self namespace + X.default = self
+ *   • `import { X } from '/ns/core'` (named)   → individual named binding (untouched)
+ *   • `const { X } = <default-import>`         → destructure from self namespace
+ *   • `require('@nativescript/core')` (CJS)    → shaped self via registry
+ *
+ * SKIP CONDITIONS
+ * ---------------
+ * Returns empty string when the source already declares a default export
+ * (some deep subpaths do — e.g. a file that does `export default MyClass`
+ * would SyntaxError on a duplicate). The consumer rewrite is also gated
+ * on `isDeepCoreSubpath`, so those paths don't normally hit the default-
+ * import pattern anyway.
+ *
+ * WHY THE DEFAULT ISN'T SHAPED
+ * ----------------------------
+ * The default is the raw null-proto MNO. This is intentional:
+ *
+ *   1. All current default-import consumers either destructure or do
+ *      property access. Neither requires Object.prototype in the chain.
+ *   2. Shaping the default inside the module body would require calling
+ *      __NS_CJS_SHAPE__ on a namespace whose own `default` slot is still
+ *      being initialized — temporal dead zone hazard.
+ *   3. CJS consumers that need `.hasOwnProperty` go through the registry
+ *      (shaped at registration), not through the default import.
+ *
+ * If a future consumer surfaces that calls `.hasOwnProperty` on the
+ * default, we can revisit. The current rule-of-least-surprise is:
+ * shape at the CJS boundary, not at the ESM boundary.
+ */
+export declare function buildDefaultExportFooter(rewrittenCode: string): string;
+/**
+ * Detects whether a module body already declares a default export in any of
+ * the syntactic forms the ESM spec allows. Mirrors the logic in
+ * `websocket-core-bridge.ts:hasModuleDefaultExport` — kept here so the
+ * default-export bridge helper is self-contained and unit-testable.
+ *
+ * Handles:
+ *   - `export default <expr>;`
+ *   - `export default function|class ...`
+ *   - `export { x as default };`
+ *   - `export { default };`        (implicit `default as default`)
+ *   - `export { default as default };`
+ *   - `export { foo, default };`
+ */
+export declare function hasExistingDefaultExport(code: string): boolean;

package/hmr/server/ns-core-cjs-shape.js

@@ -0,0 +1,271 @@
+/**
+ * CJS/ESM interop shape.
+ *
+ * PROBLEM
+ * -------
+ * ESM Module Namespace Objects (ECMA §9.4.6) have [[Prototype]] = null.
+ * They do NOT inherit Object.prototype — no `hasOwnProperty`, no `toString`,
+ * no `isPrototypeOf`. CJS consumers (most notably zone.js's `patchMethod`)
+ * assume their require() result is a plain object that has those methods:
+ *
+ *     let proto = target;
+ *     while (proto && !proto.hasOwnProperty(name)) // ← crashes on null-proto
+ *       proto = Object.getPrototypeOf(proto);
+ *
+ * `@nativescript/core/index.js` re-exports several sub-modules as namespaces:
+ *
+ *     export * as Utils from './utils';
+ *     export * as Http from './http';
+ *     export * as Connectivity from './connectivity';
+ *     export * as ApplicationSettings from './application-settings';
+ *
+ * When bundle.mjs does `import { Utils } from '@nativescript/core'`, `Utils`
+ * binds to that null-proto sub-namespace. zone.js then does
+ * `patchMethod(Utils, 'mainThreadify', …)` and crashes.
+ *
+ * WHY globalThis.require shims ALONE DON'T FIX THIS
+ * -------------------------------------------------
+ * ESM imports never pass through `globalThis.require`. They go through the
+ * host's ESM linker (V8 on iOS). Shimming `require` only intercepts the CJS
+ * path (vendor packages that use `require('@nativescript/core')`); direct
+ * ESM imports of `Utils` still see the raw null-proto namespace.
+ *
+ * THE FIX
+ * -------
+ * Rewrite `export * as X from 'Y'` at the /ns/core bridge response level:
+ *
+ *     // before
+ *     export * as Utils from './utils';
+ *
+ *     // after
+ *     import * as __ns_re_Utils__ from './utils';
+ *     export const Utils = __NS_CJS_SHAPE__(__ns_re_Utils__);
+ *
+ * Now `Utils` is a plain Object (inherits Object.prototype). Zone.js's
+ * `patchMethod(Utils, ...)` succeeds. The shape function is recursive —
+ * nested namespaces get the same treatment — and identity-preserving
+ * (WeakMap-cached) so mutations stick across lookups.
+ *
+ * WHY THE SHAPE INSTALL MUST RUN IN MODULE BODY (NOT FOOTER)
+ * ---------------------------------------------------------
+ * `export const Utils = __NS_CJS_SHAPE__(__ns_re_Utils__)` is body code. It
+ * executes during module evaluation, BEFORE the registration footer. So the
+ * shape function must be installed as a body-level statement that runs
+ * before the rewritten body — we can't rely on the footer's install.
+ *
+ * Each served /ns/core module independently installs the shape function via
+ * an idempotent `|| (globalThis.__NS_CJS_SHAPE__ = ...)` assignment. The
+ * first module to evaluate wins; subsequent evaluations are no-ops. This
+ * also handles dependency-before-importer order (depth-first ESM eval):
+ * `/ns/core/utils` evaluates before `/ns/core` main, so the shape helper
+ * is in place whenever any body needs it.
+ */
+/**
+ * Body-code statements that idempotently install `globalThis.__NS_CJS_SHAPE__`
+ * and `globalThis.__NS_CJS_SHAPE_CACHE__`. Must execute BEFORE any transformed
+ * `export const X = __NS_CJS_SHAPE__(...)` statement in the same module.
+ *
+ * Properties:
+ *   - Recursive: traverses nested namespaces so `Utils.Something` is also
+ *     a plain Object (if that sub-namespace is itself null-proto).
+ *   - Identity-preserving: WeakMap keyed on the underlying ESM namespace.
+ *     zone.js mutates its patch target; a fresh copy per call would lose
+ *     mutations. Every lookup of the same namespace returns the same
+ *     shaped object.
+ *   - Cycle-safe: records the output in the cache BEFORE recursing into
+ *     children. Handles `core ↔ platform` style cycles.
+ *   - TDZ-safe: wraps each property read in try/catch. Some exports
+ *     (Angular zone.js with early-access patterns) are still in their
+ *     temporal dead zone when the namespace is first snapshotted. A thrown
+ *     property read is skipped rather than failing the whole shape.
+ */
+export function buildShapeInstallHeader() {
+    return [
+        `/* Invariant D: CJS/ESM interop shape installer */`,
+        `try { if (typeof globalThis !== 'undefined') {`,
+        `  const __nsShapeCache = globalThis.__NS_CJS_SHAPE_CACHE__ || (globalThis.__NS_CJS_SHAPE_CACHE__ = new WeakMap());`,
+        `  if (typeof globalThis.__NS_CJS_SHAPE__ !== 'function') {`,
+        `    globalThis.__NS_CJS_SHAPE__ = function __nsShape(obj) {`,
+        `      if (!obj || typeof obj !== 'object') return obj;`,
+        `      let isNsModule = false;`,
+        `      try { isNsModule = obj[Symbol.toStringTag] === 'Module'; } catch (e) {}`,
+        `      const proto = Object.getPrototypeOf(obj);`,
+        `      if (proto !== null && !isNsModule) return obj;`,
+        `      if (__nsShapeCache.has(obj)) return __nsShapeCache.get(obj);`,
+        `      const out = {};`,
+        `      __nsShapeCache.set(obj, out);`,
+        `      try {`,
+        `        const keys = Object.keys(obj);`,
+        `        for (let i = 0; i < keys.length; i++) {`,
+        `          const k = keys[i];`,
+        `          try { out[k] = __nsShape(obj[k]); } catch (e) { /* TDZ / unreadable */ }`,
+        `        }`,
+        `      } catch (e) {}`,
+        `      return out;`,
+        `    };`,
+        `  }`,
+        `} } catch (e) { console.warn('[ns-core] shape installer failed:', (e && e.message) || e); }`,
+    ].join('\n');
+}
+/**
+ * Rewrite namespace re-exports from CJS-incompatible ESM namespace form into
+ * shape-aware const exports. Handles the two forms Vite/esbuild may emit:
+ *
+ *   (1) Original ES2020 syntax preserved unchanged:
+ *       export * as X from 'Y';
+ *
+ *   (2) Transpiled form esbuild emits when targeting older ES:
+ *       import * as _foo from 'Y';
+ *       export { _foo as X };
+ *
+ * Both become:
+ *   import * as __ns_re_X__ from 'Y';
+ *   export const X = __NS_CJS_SHAPE__(__ns_re_X__);
+ *
+ * Notes on the transform:
+ *   - The internal binding uses a derived name (`__ns_re_<X>__`) so
+ *     collisions with user bindings are extremely unlikely. Core doesn't
+ *     declare identifiers matching that shape.
+ *   - `__NS_CJS_SHAPE__` is read from globalThis with a defensive fallback
+ *     (identity function) in case installation failed or runs in an
+ *     environment where it hasn't been initialized yet. This makes the
+ *     transform safe to apply to modules that don't always go through the
+ *     /ns/core handler's headers.
+ *   - We do NOT shape `export *` (star re-exports without alias). Those
+ *     spread individual named exports — they don't create a nested
+ *     namespace and aren't affected by the null-proto issue.
+ *   - We do NOT shape `export { x } from 'y'` forms. Those copy individual
+ *     named exports directly; the consumer never sees the namespace.
+ *
+ * The regex is intentionally precise. It matches only the `export * as X from
+ * 'Y'` syntactic form (and its transpiled equivalent) — no accidental matches
+ * in string literals or comments because those can't start a top-level
+ * statement with `export`.
+ */
+export function rewriteNamespaceReExportsForShape(code) {
+    const shapeExpr = `(typeof globalThis.__NS_CJS_SHAPE__ === 'function' ? globalThis.__NS_CJS_SHAPE__ : function (x) { return x; })`;
+    // Form (1): export * as X from 'Y';  (ES2020 aggregate re-export)
+    let out = code.replace(/(^|\n)(\s*)export\s+\*\s+as\s+([A-Za-z_$][\w$]*)\s+from\s+(['"`])([^'"`\n]+)\4\s*;?/g, (_match, prefix, indent, name, quote, spec) => {
+        const internal = `__ns_re_${name}__`;
+        return `${prefix}${indent}import * as ${internal} from ${quote}${spec}${quote};\n${indent}export const ${name} = ${shapeExpr}(${internal});`;
+    });
+    // Form (2): import * as _x from 'Y'; export { _x as X };
+    // This pattern appears when esbuild targets older ES. We detect the pair
+    // by matching the import and its paired export on the same or adjacent
+    // lines. Rather than try to join two regex passes, we transform the
+    // `export { _x as X }` branch by replacing the `_x` in the export with a
+    // shape-wrapped const. Keeping the import intact is safe because the
+    // local binding is still needed for the shape call.
+    out = out.replace(/export\s*\{\s*([A-Za-z_$][\w$]*)\s+as\s+([A-Za-z_$][\w$]*)\s*\}\s*;?/g, (match, localName, exportName) => {
+        // Only transform if the local name looks like an esbuild-generated
+        // namespace binding (leading underscore) AND the export name is a
+        // PascalCase identifier. This avoids touching user re-exports.
+        if (!/^_/.test(localName))
+            return match;
+        if (!/^[A-Z]/.test(exportName))
+            return match;
+        return `export const ${exportName} = ${shapeExpr}(${localName});`;
+    });
+    return out;
+}
+/**
+ * Convenience: returns true if the given code appears to contain at least one
+ * namespace re-export that would benefit from the shape transform. Used to
+ * skip the regex replace for modules that don't need it (keeps the response
+ * identical for most submodules, which just have plain `export * from` or
+ * named exports).
+ */
+export function hasNamespaceReExport(code) {
+    return /export\s+\*\s+as\s+[A-Za-z_$][\w$]*\s+from\s+['"`]/.test(code);
+}
+/**
+ * Default-export bridge footer.
+ *
+ * BACKGROUND
+ * ----------
+ * Upstream consumer rewrites in the /ns/m handler convert
+ * `import { X } from '@nativescript/core'` into
+ * `import __ns_core_ns from '/ns/core'; const { X } = __ns_core_ns;`
+ * — a DEFAULT import followed by destructuring. The inline comment on that
+ * rewrite says explicitly: "This makes `import { Frame } from
+ * '@nativescript/core'` work even if the bridge provides only a default
+ * export."
+ *
+ * The original `@nativescript/core/index.js` has no `export default` — all
+ * named exports. Without this footer, consumers of the transformed import
+ * fail at ESM link time:
+ *
+ *     SyntaxError: The requested module '/ns/core/<ver>' does not
+ *     provide an export named 'default'
+ *
+ * THE FIX
+ * -------
+ * Emit `export default __ns_core_self_ns__;` at the end of the served
+ * module body. `__ns_core_self_ns__` is the namespace import the server
+ * already emits at the top of every /ns/core response for self-
+ * registration purposes. ESM spec guarantees a module re-entering itself
+ * during evaluation returns the in-progress namespace — so no extra
+ * evaluation occurs, and the default binding receives an object whose
+ * properties are every named export of the same module.
+ *
+ * CONSUMER MATRIX AFTER THIS FIX
+ * ------------------------------
+ *   • `import X from '/ns/core'` (default)     → X = self namespace
+ *   • `import * as X from '/ns/core'`          → X = self namespace + X.default = self
+ *   • `import { X } from '/ns/core'` (named)   → individual named binding (untouched)
+ *   • `const { X } = <default-import>`         → destructure from self namespace
+ *   • `require('@nativescript/core')` (CJS)    → shaped self via registry
+ *
+ * SKIP CONDITIONS
+ * ---------------
+ * Returns empty string when the source already declares a default export
+ * (some deep subpaths do — e.g. a file that does `export default MyClass`
+ * would SyntaxError on a duplicate). The consumer rewrite is also gated
+ * on `isDeepCoreSubpath`, so those paths don't normally hit the default-
+ * import pattern anyway.
+ *
+ * WHY THE DEFAULT ISN'T SHAPED
+ * ----------------------------
+ * The default is the raw null-proto MNO. This is intentional:
+ *
+ *   1. All current default-import consumers either destructure or do
+ *      property access. Neither requires Object.prototype in the chain.
+ *   2. Shaping the default inside the module body would require calling
+ *      __NS_CJS_SHAPE__ on a namespace whose own `default` slot is still
+ *      being initialized — temporal dead zone hazard.
+ *   3. CJS consumers that need `.hasOwnProperty` go through the registry
+ *      (shaped at registration), not through the default import.
+ *
+ * If a future consumer surfaces that calls `.hasOwnProperty` on the
+ * default, we can revisit. The current rule-of-least-surprise is:
+ * shape at the CJS boundary, not at the ESM boundary.
+ */
+export function buildDefaultExportFooter(rewrittenCode) {
+    if (hasExistingDefaultExport(rewrittenCode))
+        return '';
+    return ['/* Default-export bridge for /ns/core consumers */', 'export default __ns_core_self_ns__;'].join('\n');
+}
+/**
+ * Detects whether a module body already declares a default export in any of
+ * the syntactic forms the ESM spec allows. Mirrors the logic in
+ * `websocket-core-bridge.ts:hasModuleDefaultExport` — kept here so the
+ * default-export bridge helper is self-contained and unit-testable.
+ *
+ * Handles:
+ *   - `export default <expr>;`
+ *   - `export default function|class ...`
+ *   - `export { x as default };`
+ *   - `export { default };`        (implicit `default as default`)
+ *   - `export { default as default };`
+ *   - `export { foo, default };`
+ */
+export function hasExistingDefaultExport(code) {
+    if (!code || typeof code !== 'string')
+        return false;
+    if (/\bexport\s+default\b/.test(code))
+        return true;
+    if (/\bexport\s*\{[^}]*\bdefault\b[^}]*\}/.test(code))
+        return true;
+    return false;
+}
+//# sourceMappingURL=ns-core-cjs-shape.js.map

package/hmr/server/ns-core-cjs-shape.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"ns-core-cjs-shape.js","sourceRoot":"","sources":["../../../../../packages/vite/hmr/server/ns-core-cjs-shape.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6DG;AAEH;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,UAAU,uBAAuB;IACtC,OAAO;QACN,oDAAoD;QACpD,gDAAgD;QAChD,oHAAoH;QACpH,4DAA4D;QAC5D,6DAA6D;QAC7D,wDAAwD;QACxD,+BAA+B;QAC/B,+EAA+E;QAC/E,iDAAiD;QACjD,sDAAsD;QACtD,oEAAoE;QACpE,uBAAuB;QACvB,qCAAqC;QACrC,aAAa;QACb,wCAAwC;QACxC,iDAAiD;QACjD,8BAA8B;QAC9B,oFAAoF;QACpF,WAAW;QACX,sBAAsB;QACtB,mBAAmB;QACnB,QAAQ;QACR,KAAK;QACL,6FAA6F;KAC7F,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AACd,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAkCG;AACH,MAAM,UAAU,iCAAiC,CAAC,IAAY;IAC7D,MAAM,SAAS,GAAG,gHAAgH,CAAC;IAEnI,kEAAkE;IAClE,IAAI,GAAG,GAAG,IAAI,CAAC,OAAO,CAAC,sFAAsF,EAAE,CAAC,MAAM,EAAE,MAAc,EAAE,MAAc,EAAE,IAAY,EAAE,KAAa,EAAE,IAAY,EAAE,EAAE;QACpM,MAAM,QAAQ,GAAG,WAAW,IAAI,IAAI,CAAC;QACrC,OAAO,GAAG,MAAM,GAAG,MAAM,eAAe,QAAQ,SAAS,KAAK,GAAG,IAAI,GAAG,KAAK,MAAM,MAAM,gBAAgB,IAAI,MAAM,SAAS,IAAI,QAAQ,IAAI,CAAC;IAC9I,CAAC,CAAC,CAAC;IAEH,yDAAyD;IACzD,yEAAyE;IACzE,uEAAuE;IACvE,oEAAoE;IACpE,yEAAyE;IACzE,qEAAqE;IACrE,oDAAoD;IACpD,GAAG,GAAG,GAAG,CAAC,OAAO,CAAC,uEAAuE,EAAE,CAAC,KAAK,EAAE,SAAiB,EAAE,UAAkB,EAAE,EAAE;QAC3I,mEAAmE;QACnE,kEAAkE;QAClE,+DAA+D;QAC/D,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,SAAS,CAAC;YAAE,OAAO,KAAK,CAAC;QACxC,IAAI,CAAC,QAAQ,CAAC,IAAI,CAAC,UAAU,CAAC;YAAE,OAAO,KAAK,CAAC;QAC7C,OAAO,gBAAgB,UAAU,MAAM,SAAS,IAAI,SAAS,IAAI,CAAC;IACnE,CAAC,CAAC,CAAC;IAEH,OAAO,GAAG,CAAC;AACZ,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,oBAAoB,CAAC,IAAY;IAChD,OAAO,oDAAoD,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AACxE,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6DG;AACH,MAAM,UAAU,wBAAwB,CAAC,aAAqB;IAC7D,IAAI,wBAAwB,CAAC,aAAa,CAAC;QAAE,OAAO,EAAE,CAAC;IACvD,OAAO,CAAC,oDAAoD,EAAE,qCAAqC,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AACjH,CAAC;AAED;;;;;;;;;;;;;GAaG;AACH,MAAM,UAAU,wBAAwB,CAAC,IAAY;IACpD,IAAI,CAAC,IAAI,IAAI,OAAO,IAAI,KAAK,QAAQ;QAAE,OAAO,KAAK,CAAC;IACpD,IAAI,sBAAsB,CAAC,IAAI,CAAC,IAAI,CAAC;QAAE,OAAO,IAAI,CAAC;IACnD,IAAI,sCAAsC,CAAC,IAAI,CAAC,IAAI,CAAC;QAAE,OAAO,IAAI,CAAC;IACnE,OAAO,KAAK,CAAC;AACd,CAAC"}

package/hmr/server/ns-rt-bridge.d.ts

@@ -0,0 +1,51 @@
+export interface NsRtBridgeOptions {
+    /** Version segment from `/ns/rt/<ver>`. Retained for the URL dispatcher; the bridge body intentionally ignores it. */
+    rtVer: string;
+    /** Prologue installed verbatim before the bridge body (typically the require URL guard). */
+    requireGuardSnippet: string;
+    /**
+     * The discovered ESM export names of the underlying vendor package
+     * (`nativescript-vue`, including its `@vue/runtime-core` re-export
+     * chain). Each name becomes `export const <name> = (__ensure().<name>);` —
+     * a single canonical specifier (`/ns/rt`) forwards *every* symbol the
+     * vendor publishes.
+     *
+     * Required: discovery is the only source of truth. There is no hand-curated
+     * fallback — if discovery cannot see the package, the bridge serves no
+     * passthroughs and the call site is expected to surface that as a config
+     * error rather than silently degrade.
+     */
+    vendorExports: Iterable<string>;
+}
+/**
+ * Build the `/ns/rt` runtime bridge module text.
+ *
+ * Single-realm policy: every named export the vendor package publishes
+ * appears as `export const X = (__ensure().X);` — a constant binding, not a
+ * function wrapper. Constant bindings preserve identity for Vue's Symbol
+ * markers (`Fragment`, `Teleport`, …) AND work transparently for functions
+ * (`ref`, `createApp`, …) since the user code calls the underlying value
+ * directly. Calling `__ensure()` at module evaluation time is safe because
+ * the vendor bundle is registered earlier in the boot graph (vendor.mjs →
+ * `__nsVendorRegistry`), and the bridge resolves the same `nativescript-vue`
+ * record everyone else uses.
+ *
+ * HMR-specific shims (`$navigateTo`, `$navigateBack`, `$showModal`) and the
+ * Vite client polyfill (`vite__injectQuery`) are emitted as overrides that
+ * replace the would-be passthrough — those exports route through the HMR
+ * navigator instead of the vendor's native version, so the bridge must
+ * provide the override, not the discovered original.
+ */
+export declare function buildNsRtBridgeModule(options: NsRtBridgeOptions): string;
+/**
+ * Resolve the set of names the bridge should re-export for `nativescript-vue`
+ * given a project root. Static discovery via `enumeratePackageExports` is the
+ * only source — there is no curated fallback. If `nativescript-vue` is not
+ * resolvable from `projectRoot`, the returned set is empty and the bridge
+ * built from it will not emit passthroughs; the caller should treat that as
+ * the misconfiguration it is rather than mask it with a stale baseline.
+ *
+ * Caching lives inside `enumeratePackageExports`, so repeated calls in a dev
+ * session are effectively free.
+ */
+export declare function discoverNsvBridgeExports(projectRoot: string): Set<string>;