@nativescript/vite 8.0.0-alpha.0 → 8.0.0-alpha.10

package/hmr/frameworks/angular/client/index.js

@@ -1,3 +1,71 @@
+// Opt-out flag for the apply-progress overlay (default: enabled).
+// Driven by `NS_VITE_PROGRESS_OVERLAY=0` (or `false`/`off`/`no`) on the
+// dev server; baked into the bundle via
+// `__NS_HMR_PROGRESS_OVERLAY_ENABLED__` at build time. We collapse the
+// build-time constant into a runtime boolean once so each call-site is
+// a single property check rather than a try/typeof. Tests that re-run
+// the angular client (via vitest) see `undefined` and default to
+// enabled — matching the production dev-server experience.
+const overlayEnabled = (() => {
+    try {
+        return typeof __NS_HMR_PROGRESS_OVERLAY_ENABLED__ === 'boolean' ? __NS_HMR_PROGRESS_OVERLAY_ENABLED__ : true;
+    }
+    catch {
+        return true;
+    }
+})();
+function getHmrOverlayApi() {
+    if (!overlayEnabled)
+        return null;
+    try {
+        return globalThis.__NS_HMR_DEV_OVERLAY__ || null;
+    }
+    catch { }
+    return null;
+}
+function setUpdateOverlayStage(stage, info) {
+    if (!overlayEnabled)
+        return;
+    try {
+        const api = getHmrOverlayApi();
+        if (api && typeof api.setUpdateStage === 'function') {
+            api.setUpdateStage(stage, info);
+        }
+    }
+    catch { }
+}
+function hideUpdateOverlay() {
+    if (!overlayEnabled)
+        return;
+    try {
+        const api = getHmrOverlayApi();
+        if (api && typeof api.hide === 'function') {
+            api.hide('hmr-applied');
+        }
+    }
+    catch { }
+}
+// Safe accessor for the build-time `__NS_ENV_VERBOSE__` constant.
+//
+// Vite replaces `__NS_ENV_VERBOSE__` at build time via `define`. In
+// unit tests (vitest, plain ts-node, etc.) the identifier is
+// undeclared at runtime, so a bare reference throws ReferenceError —
+// `typeof` is the only safe way to probe it. We collapse the
+// build-time constant into a runtime boolean once at module load and
+// then short-circuit on `verbose` arguments at every call-site.
+//
+// Always order `verbose && envVerbose` so the runtime flag
+// short-circuits the build-time constant; that prevents reference
+// errors in test environments where the `define` substitution does
+// not run.
+const envVerbose = (() => {
+    try {
+        return typeof __NS_ENV_VERBOSE__ === 'boolean' ? __NS_ENV_VERBOSE__ : false;
+    }
+    catch {
+        return false;
+    }
+})();
 export function installAngularHmrClientHooks() {
     const g = globalThis;
     if (g.__NS_ANGULAR_HMR_CLIENT_INSTALLED__) {
@@ -5,53 +73,781 @@ export function installAngularHmrClientHooks() {
     }
     try {
         g.__NS_ANGULAR_HMR_CLIENT_INSTALLED__ = true;
-        if (__NS_ENV_VERBOSE__) {
+        if (envVerbose) {
             console.log('[hmr-angular] client hooks installed');
         }
     }
     catch { }
 }
-export function handleAngularHotUpdateMessage(msg, options) {
+// HMR cycle serialization mutex.
+//
+// A back-to-back save (e.g., the user holds Cmd+S, or `runOnSave`
+// saves a file twice during one tick) could overlap two HMR cycles:
+// the first cycle's `import(entry)` would still be resolving when the
+// second cycle's `__nsInvalidateModules` ran, leaving the registry in
+// a half-evicted state and producing flaky "module already evaluated"
+// errors.
+//
+// Each `handleAngularHotUpdateMessage` call publishes a promise to
+// `inFlightHmrCycle` and awaits the previous publication before
+// starting its own evict + import. The previous-cycle promise resolves
+// regardless of success or failure (we always run `resolveCycle()` in
+// `finally`), so a stuck cycle can't deadlock the queue. The mutex is
+// intentionally process-wide and resets naturally on cold-boot or
+// websocket reconnect (both blow away the JS realm).
+let inFlightHmrCycle = null;
+// Explicit module eviction.
+//
+// `__nsInvalidateModules` is a runtime-installed global that takes an
+// array of canonical /ns/m/<rel> URLs and removes each one from V8's
+// module registry (`g_moduleRegistry`). The runtime canonicalizer
+// strips legacy `__ns_hmr__/<tag>/` and `__ns_boot__/b1/` segments
+// before lookup, so the same URL evicts every cache entry historically
+// created for that module — even if a stale tagged URL is still around.
+//
+// Soft-fails on older runtimes that don't expose the function. In that
+// case we fall through to the legacy URL-versioning path and emit a
+// one-time warning so the user knows the eviction protocol is
+// unavailable.
+// Dispatch one of Vite's standard HMR lifecycle events through the iOS
+// runtime's `__NS_DISPATCH_HOT_EVENT__` global. The runtime owns the
+// listener registry that `import.meta.hot.on(event, cb)` populates; this
+// function is the producer side that lets the Angular HMR client emit the
+// canonical Vite events (`vite:beforeUpdate`, `vite:afterUpdate`,
+// `vite:beforeFullReload`, `vite:invalidate`, `vite:error`) at the right
+// moments. User code that does
+// `import.meta.hot.on('vite:beforeUpdate', cb)` only fires when this is
+// called.
+//
+// Soft-fails on older runtimes that don't expose the dispatcher (the
+// global is undefined; we no-op). Per-listener failures are swallowed
+// inside the runtime, so a single bad listener can't break the HMR cycle.
+function dispatchHotEvent(g, event, payload) {
+    try {
+        const fn = g && g.__NS_DISPATCH_HOT_EVENT__;
+        if (typeof fn === 'function') {
+            fn.call(g, event, payload);
+        }
+    }
+    catch (err) {
+        // Defensive: if the dispatcher itself throws, we'd already have
+        // no listeners (per-callback failures swallowed inside the
+        // runtime), so this is purely a safety net for runtime
+        // regressions. Log only under verbose to avoid noisy dev logs.
+        if (envVerbose) {
+            console.warn(`[ns-hmr-diag][client] __NS_DISPATCH_HOT_EVENT__('${event}') threw:`, err?.message ?? err);
+        }
+    }
+}
+// Trigger a full app reload via the runtime's `__nsReloadDevApp` global,
+// dispatching `vite:beforeFullReload` first so user-code listeners can
+// react. Returns `true` if the reload was triggered, `false` if the
+// runtime doesn't expose the API. Used both by `import.meta.hot.invalidate()`
+// (handled directly inside the runtime) AND by the declined-module check
+// below (where the JS layer makes the decision and asks for the reload).
+function triggerFullReload(g, message) {
+    const fn = g && g.__nsReloadDevApp;
+    if (typeof fn !== 'function') {
+        return false;
+    }
+    dispatchHotEvent(g, 'vite:beforeFullReload', { message });
+    try {
+        // Fire-and-forget — `__nsReloadDevApp` returns a Promise, but we
+        // don't await it here because the JS realm is about to be torn
+        // down. The HMR cycle's caller treats this as terminal and
+        // short-circuits the rest of the cycle.
+        fn.call(g);
+    }
+    catch (err) {
+        if (envVerbose) {
+            console.warn('[ns-hmr-diag][client] __nsReloadDevApp threw:', err?.message ?? err);
+        }
+        return false;
+    }
+    return true;
+}
+// Check if any module being touched by this HMR update has called
+// `import.meta.hot.decline()`. If so, per Vite spec we MUST do a full
+// reload instead of a hot-update — declining means "I refuse to be
+// hot-updated". Returns `true` if a full reload was triggered (caller
+// should short-circuit the rest of the cycle).
+//
+// Older runtimes without `__nsHasDeclinedModule` skip the check entirely
+// (legacy behaviour: HMR proceeds with the reboot, which is the same
+// behaviour they had before this fix).
+function checkDeclinedAndReload(g, msg, options) {
+    const checker = g && g.__nsHasDeclinedModule;
+    if (typeof checker !== 'function')
+        return false;
+    // `evictPaths` is the eviction set the dev server computed for this
+    // HMR cycle — every module that needs to be re-evaluated. If ANY of
+    // those modules declined HMR, the whole cycle has to convert to a
+    // full reload. Pass them through verbatim; the runtime canonicalizes
+    // internally when matching against `g_hotDeclined`.
+    const evictPaths = Array.isArray(msg?.evictPaths) ? msg.evictPaths : [];
+    let declined = false;
+    try {
+        declined = !!checker.call(g, evictPaths);
+    }
+    catch (err) {
+        if (options.verbose && envVerbose) {
+            console.warn('[ns-hmr-diag][client] __nsHasDeclinedModule threw:', err?.message ?? err);
+        }
+        return false;
+    }
+    if (!declined)
+        return false;
+    const filePath = typeof msg?.path === 'string' ? msg.path : '<unknown>';
+    const message = `module declined HMR (file=${filePath}, evictPaths=${evictPaths.length})`;
+    console.info(`[ns-hmr][decline] ${message} — falling back to full reload`);
+    const reloaded = triggerFullReload(g, message);
+    if (!reloaded && options.verbose && envVerbose) {
+        console.warn('[ns-hmr-diag][client] declined module detected but __nsReloadDevApp unavailable; HMR will proceed (older runtime)');
+    }
+    return reloaded;
+}
+// Drain `import.meta.hot.dispose(cb)` callbacks via the iOS runtime's
+// `globalThis.__nsRunHmrDispose()` global before Angular's reboot.
+//
+// The runtime owns the dispose registry (`g_hotDispose` in
+// `HMRSupport.mm`) — every call to `import.meta.hot.dispose(cb)` from
+// user code lands there. This client just asks the runtime to drain.
+// We pass NO key argument so the runtime drains every registered
+// callback across every module, which matches the wholesale-reboot
+// semantics of `__reboot_ng_modules__`: when Angular tears down its
+// component tree and re-bootstraps, every module's accumulated side
+// effects are conceptually being thrown away. (A future per-module
+// HMR client could pass an explicit key list to limit the drain.)
+//
+// Older runtimes (before this hook shipped) silently no-op via the
+// optional chain; in that case, dispose callbacks register but never
+// fire, and the worker-specific safety net in `terminateTrackedWorkers`
+// below still catches the worker pile-up case.
+function runHmrDisposeCallbacks(g, options) {
+    let runner;
+    try {
+        const candidate = g && g.__nsRunHmrDispose;
+        if (typeof candidate === 'function') {
+            runner = candidate;
+        }
+    }
+    catch {
+        // `globalThis` access defensiveness — Proxy-wrapped globals can
+        // throw on property reads.
+    }
+    if (!runner) {
+        // Older runtime: the dispose callback registry exists in the
+        // native runtime but no JS-callable drain entrypoint is
+        // available. Silently no-op (worker terminator below still
+        // runs). The diagnostic message is gated to verbose so we
+        // don't nag users on every cycle of every project that hasn't
+        // adopted the new runtime yet.
+        if (options.verbose && envVerbose) {
+            console.info('[ns-hmr-diag][client] runtime missing __nsRunHmrDispose; skipping import.meta.hot.dispose drain (upgrade @nativescript/ios for support)');
+        }
+        return;
+    }
+    let executed = null;
+    try {
+        const result = runner.call(g);
+        executed = typeof result === 'number' ? result : 0;
+    }
+    catch (err) {
+        // One bad disposer should already be swallowed inside the
+        // runtime per-callback try/catch. If the runtime itself throws
+        // (out-of-memory, isolate teardown race, etc.) we MUST NOT
+        // take down the HMR cycle.
+        if (options.verbose && envVerbose) {
+            console.warn('[ns-hmr-diag][client] __nsRunHmrDispose threw:', err?.message ?? err);
+        }
+        return;
+    }
+    // Surface ONE concise log per HMR cycle that actually had disposers
+    // to run. Quiet on cycles where no module had registered any.
+    if (executed && executed > 0) {
+        console.info(`[ns-hmr][dispose] ran ${executed} import.meta.hot.dispose callback${executed === 1 ? '' : 's'} before reboot`);
+    }
+}
+// Terminate every live worker before Angular's reboot. Two-tier strategy:
+//
+//   1. PREFERRED — `globalThis.__nsTerminateAllWorkers()` (NS iOS runtime
+//      ≥ the version that ships `Worker::TerminateAllWorkersCallback`).
+//      Native code iterates `Caches::Workers` (the runtime's authoritative
+//      worker registry) and calls `WorkerWrapper::Terminate()` on each
+//      live entry. Universal: catches every worker regardless of how it
+//      was created — `new Worker(new URL(...))`, raw `Worker('~/x.js')`,
+//      dynamic-import-spawned workers, plugin-spawned workers, etc.
+//
+//   2. FALLBACK — drain `globalThis.__NS_HMR_WORKERS__` (a Set populated
+//      by `__nsHmrTrackWorker`, the helper that `workerHmrUrlPlugin`
+//      injects at the top of every dev module containing a
+//      `new Worker(new URL(...))` call). This keeps HMR worker cleanup
+//      working on older runtimes that don't yet expose
+//      `__nsTerminateAllWorkers`. It only catches workers spawned via
+//      the Vite-rewritten path, so the runtime API is strictly better
+//      coverage.
+//
+// Either way: producer-side wraps are still useful as diagnostic
+// metadata (which user code spawned which worker), so we always clear
+// the JS Set after termination — irrespective of which tier ran — so
+// it doesn't grow unbounded across HMR cycles.
+//
+// Tolerant of:
+//   * Missing globals — non-worker apps have neither global; we no-op.
+//   * `terminate()` throwing — the runtime can throw on already-dead
+//     workers; we catch per-entry so subsequent terminations and the
+//     reboot itself still proceed.
+//   * Native API throwing — wrapped in try/catch so a runtime regression
+//     can't take down the HMR cycle; we degrade to the JS-Set fallback.
+function terminateTrackedWorkers(g, options) {
+    let nativeApi;
+    try {
+        const candidate = g && g.__nsTerminateAllWorkers;
+        if (typeof candidate === 'function') {
+            nativeApi = candidate;
+        }
+    }
+    catch {
+        // Reading the global threw (extremely defensive — `globalThis`
+        // access shouldn't, but Proxy-wrapped globals can).
+    }
+    let nativeTerminated = null;
+    if (nativeApi) {
+        try {
+            const result = nativeApi.call(g);
+            // Native API returns the count of workers terminated as a
+            // number. Older betas may return undefined; treat any
+            // non-number as "ran successfully, count unknown".
+            nativeTerminated = typeof result === 'number' ? result : 0;
+        }
+        catch (err) {
+            if (options.verbose && envVerbose) {
+                console.warn('[ns-hmr-diag][client] __nsTerminateAllWorkers threw; falling back to JS-tracked Set:', err?.message ?? err);
+            }
+            nativeApi = undefined; // force fallback below
+        }
+    }
+    // Always touch the JS-tracked Set so producer-side bookkeeping
+    // doesn't outlive its workers across HMR cycles. If the native API
+    // already terminated everything, this is just a `.clear()`. If the
+    // native API isn't available (older runtime), this is the actual
+    // cleanup path.
+    let workers;
+    try {
+        workers = g && g.__NS_HMR_WORKERS__;
+    }
+    catch {
+        // fall through with `workers === undefined`
+    }
+    let fallbackTerminated = 0;
+    let fallbackFailed = 0;
+    const fallbackTotal = workers && typeof workers.size === 'number' ? workers.size : 0;
+    if (!nativeApi && workers && fallbackTotal > 0) {
+        // No native API — drain the JS-tracked Set as the primary path.
+        for (const worker of workers) {
+            try {
+                if (worker && typeof worker.terminate === 'function') {
+                    worker.terminate();
+                    fallbackTerminated++;
+                }
+            }
+            catch {
+                fallbackFailed++;
+            }
+        }
+    }
+    if (workers) {
+        try {
+            workers.clear();
+        }
+        catch { }
+    }
+    // Surface ONE concise log per HMR cycle when there was actually work
+    // to do. This isn't gated on `verbose` so the user can see in the
+    // dev terminal which cleanup tier ran without flipping a flag —
+    // it's a single line per HMR-cycle-with-workers, never per cycle
+    // when no workers exist. Filter on "actually did something" so we
+    // stay quiet on no-worker apps and on cycles where neither tier
+    // found anything.
+    if (nativeApi && (nativeTerminated ?? 0) > 0) {
+        console.info(`[ns-hmr][workers] terminated ${nativeTerminated} via runtime __nsTerminateAllWorkers before reboot`);
+    }
+    else if (!nativeApi && fallbackTerminated > 0) {
+        console.info(`[ns-hmr][workers] terminated ${fallbackTerminated}/${fallbackTotal} via JS-tracked Set fallback before reboot (older runtime; consider upgrading @nativescript/ios for native API)`);
+    }
+}
+function invalidateModules(urls, verbose) {
+    if (!urls || !urls.length)
+        return false;
+    const g = globalThis;
+    const fn = g.__nsInvalidateModules;
+    if (typeof fn !== 'function') {
+        console.warn(`[ns-hmr-diag][client] runtime missing __nsInvalidateModules; falling back to legacy URL versioning. evict=${urls.length}`);
+        return false;
+    }
+    try {
+        if (verbose && envVerbose) {
+            console.info(`[ns-hmr-diag][client] invalidateModules calling __nsInvalidateModules urls=${urls.length}`);
+        }
+        fn.call(null, urls);
+        if (verbose && envVerbose) {
+            console.info(`[ns-hmr-diag][client] invalidateModules OK urls=${urls.length}`);
+        }
+        return true;
+    }
+    catch (error) {
+        // Real exception path — the runtime hook itself threw. Always
+        // surfaced for the same reason as the missing-hook warn above.
+        console.warn('[ns-hmr-diag][client] __nsInvalidateModules threw', error?.message || error);
+        return false;
+    }
+}
+// Eviction-set size cap for the kickstart.
+//
+// `__NS_HMR_KICKSTART_MAX_URLS__` is a build-time literal injected
+// by `helpers/global-defines.ts` (default 32). It is a pure
+// performance gate: the kickstart never affects correctness, so
+// skipping it for large fan-out edits simply reverts the runtime to
+// sequential `HttpFetchText`. See the doc comment on
+// `resolveHmrKickstartMaxUrls` (in global-defines.ts) for the
+// rationale and the empirical numbers behind the default.
+//
+// The constant is read once at module load (the same pattern used
+// for `overlayEnabled`) so each call site is a single inequality
+// check rather than a try/typeof. Tests that re-import this module
+// see `undefined` and fall back to the default.
+const KICKSTART_DEFAULT_MAX_URLS = 32;
+const kickstartMaxUrls = (() => {
+    try {
+        const raw = __NS_HMR_KICKSTART_MAX_URLS__;
+        if (typeof raw !== 'number')
+            return KICKSTART_DEFAULT_MAX_URLS;
+        if (!Number.isFinite(raw))
+            return Number.POSITIVE_INFINITY;
+        if (raw < 0)
+            return KICKSTART_DEFAULT_MAX_URLS;
+        return Math.floor(raw);
+    }
+    catch {
+        return KICKSTART_DEFAULT_MAX_URLS;
+    }
+})();
+// Decide whether to run the kickstart for a given eviction set.
+// Exported for unit testing — callers in this module use the inline
+// `evictPaths.length` comparison below for a slightly cheaper
+// hot-path.
+//
+// Semantics:
+// - `0` urls   → no work to do; skip (returns false).
+// - `urls.length <= cap` → kickstart eligible (returns true).
+// - `urls.length > cap`  → skip kickstart (returns false). V8 falls
+//   back to per-module synchronous fetches inside its module walk.
+// - `cap === 0`           → kickstart disabled regardless of size.
+// - `cap === Infinity`    → kickstart always eligible (no cap).
+export function shouldRunKickstart(urlCount, maxUrls = kickstartMaxUrls) {
+    if (!Number.isFinite(urlCount) || urlCount <= 0)
+        return false;
+    if (!Number.isFinite(maxUrls))
+        return maxUrls > 0;
+    if (maxUrls <= 0)
+        return false;
+    return urlCount <= maxUrls;
+}
+function kickstartHmrPrefetch(urls, verbose) {
+    if (!urls || !urls.length)
+        return null;
+    const g = globalThis;
+    const fn = g.__nsKickstartHmrPrefetch;
+    if (typeof fn !== 'function') {
+        if (verbose && envVerbose) {
+            console.info(`[hmr-angular] runtime missing __nsKickstartHmrPrefetch; serial fetches will be used. urls=${urls.length}`);
+        }
+        return null;
+    }
+    try {
+        // Concurrency cap of 16 matches the runtime's documented
+        // default for the kickstart BFS. Timeout at 10s tracks the
+        // runtime's `HttpFetchText` retry envelope so we don't
+        // hold the JS thread forever on a stalled dev server.
+        const result = fn.call(null, urls.slice(), { maxConcurrent: 16, timeoutMs: 10000 });
+        if (result && typeof result === 'object') {
+            const ok = !!result.ok;
+            const fetched = typeof result.fetched === 'number' ? result.fetched : 0;
+            const ms = typeof result.ms === 'number' ? result.ms : 0;
+            return { ok, fetched, ms };
+        }
+        return null;
+    }
+    catch (error) {
+        if (verbose && envVerbose) {
+            console.warn('[hmr-angular] __nsKickstartHmrPrefetch threw', error?.message || error);
+        }
+        return null;
+    }
+}
+function getAngularBootstrapEntryCandidates(msg) {
+    const root = typeof __NS_APP_ROOT_VIRTUAL__ === 'string' && __NS_APP_ROOT_VIRTUAL__ ? __NS_APP_ROOT_VIRTUAL__ : '/src';
+    // Server announces the canonical bootstrap entry as
+    // `importerEntry`, computed from `package.json#main`. Fall back to
+    // the legacy `entryCandidates` array (for older servers) and finally
+    // to a hard-coded list. All candidates must be project-relative
+    // posix paths (e.g. `/src/main.ts`) so they slot directly behind
+    // `${origin}/ns/m`.
+    const explicit = typeof msg?.importerEntry === 'string' && msg.importerEntry.startsWith('/') ? [msg.importerEntry] : [];
+    const legacy = Array.isArray(msg?.entryCandidates) && msg.entryCandidates.length ? msg.entryCandidates : [];
+    const fallback = [`${root}/main.ts`, `${root}/app.ts`];
+    const merged = [...explicit, ...legacy, ...fallback];
+    const seen = new Set();
+    const result = [];
+    for (const candidate of merged) {
+        if (typeof candidate !== 'string' || !candidate.startsWith('/'))
+            continue;
+        if (seen.has(candidate))
+            continue;
+        seen.add(candidate);
+        result.push(candidate);
+    }
+    return result;
+}
+async function importAngularBootstrapEntry(url) {
+    const g = globalThis;
+    if (typeof g.__NS_HMR_IMPORT__ === 'function') {
+        return g.__NS_HMR_IMPORT__(url);
+    }
+    return import(/* @vite-ignore */ url);
+}
+export async function refreshAngularBootstrapOptions(msg, options) {
+    const g = globalThis;
+    if (typeof g.__NS_UPDATE_ANGULAR_APP_OPTIONS__ !== 'function') {
+        return;
+    }
+    const originSource = typeof msg?.origin === 'string' && /^https?:\/\//.test(msg.origin) ? msg.origin : g.__NS_HTTP_ORIGIN__;
+    if (typeof originSource !== 'string' || !/^https?:\/\//.test(originSource)) {
+        return;
+    }
+    const origin = originSource.replace(/\/$/, '');
+    // Explicit eviction set takes precedence over URL versioning. The
+    // server walks the inverse-dep closure of the changed file
+    // (collectAngularEvictionUrls) and emits canonical /ns/m/<rel> URLs
+    // in `evictPaths`. We hand the list to the runtime before
+    // re-importing the entry; the runtime drops those entries from
+    // `g_moduleRegistry` so V8's subsequent `import(entry)` walks the
+    // dep graph and re-fetches ONLY those modules. Everything else stays
+    // hot in the cache.
+    const evictPaths = Array.isArray(msg?.evictPaths) ? msg.evictPaths.filter((u) => typeof u === 'string' && /^https?:\/\//.test(u)) : [];
+    // Diagnostic: log eviction set client-side so we can verify what
+    // the runtime is being asked to drop. Up to 32 entries are sampled
+    // so large constants edits don't swamp the console. Gated behind
+    // the standard `__NS_ENV_VERBOSE__` build define (`NS_VITE_VERBOSE`)
+    // so the lines stay silent on normal saves.
+    if (options.verbose && envVerbose) {
+        const _path = typeof msg?.path === 'string' ? msg.path : '(unknown)';
+        console.info(`[ns-hmr-diag][client] received ns:angular-update path=${_path} evictPaths.length=${evictPaths.length} importerEntry=${msg?.importerEntry ?? '(none)'}`);
+        if (evictPaths.length) {
+            const sample = evictPaths.slice(0, 32);
+            console.info(`[ns-hmr-diag][client] evictPaths firstN=`, sample);
+            if (evictPaths.length > sample.length) {
+                console.info(`[ns-hmr-diag][client] evictPaths hidden=${evictPaths.length - sample.length}`);
+            }
+        }
+    }
+    // Drive the apply-progress overlay through the 'evicting' frame
+    // *before* the runtime invalidate call so the user sees the count
+    // even on the cheapest stage. Eviction count also doubles as a
+    // useful debug breadcrumb in the overlay's detail line — large
+    // counts (e.g. constants edits → 100+ importers) explain why a
+    // cycle takes longer than an HTML edit.
+    setUpdateOverlayStage('evicting', {
+        detail: evictPaths.length ? `Invalidating ${evictPaths.length} module${evictPaths.length === 1 ? '' : 's'}` : 'Invalidating module cache',
+    });
+    const evicted = invalidateModules(evictPaths, options.verbose);
+    if (options.verbose && envVerbose) {
+        console.info(`[ns-hmr-diag][client] evict count=${evictPaths.length} ok=${evicted ? 'yes' : 'no'}`);
+    }
+    // Parallel HTTP prefetch for the freshly-evicted modules.
+    //
+    // Order matters here: the kickstart MUST run after the eviction so
+    // that it actually re-populates `g_prefetchCache` for the modules
+    // V8 will ask for. If we kickstarted before the eviction, every URL
+    // would skip on the "already cached" check (the walk consumes
+    // destructively but the prior non-evicted modules sit in V8's
+    // `g_moduleRegistry`, not the prefetch cache).
+    //
+    // We only kickstart when the eviction succeeded, because the
+    // fallback path (legacy URL-versioning, see `useStableUrls = evicted`
+    // below) doesn't go through canonical /ns/m URLs and the runtime
+    // would not match its prefetch cache lookups against the version-
+    // prefixed forms V8 will end up requesting. Better to skip the
+    // optimization than risk a confusing partial cache hit.
+    //
+    // `shouldRunKickstart` gates large eviction sets out of the
+    // parallel wave. A `.ts` file with deep inverse-dep fan-in
+    // (constants files, design-system enums) can produce a
+    // 200–300-URL closure that overwhelms Vite's single-threaded
+    // transform pipeline. The kickstart fan-out then makes the cycle
+    // 5–8× slower than letting V8 fetch sequentially as it walks the
+    // real forward path. The cap (default 32, override with
+    // `NS_VITE_KICKSTART_MAX_URLS`) keeps component-shaped closures
+    // (typically 5–30 URLs) on the fast path. Correctness is
+    // unaffected — V8's per-module synchronous fetch is the same fall-
+    // back code path the runtime has always used.
+    if (evicted && evictPaths.length > 0) {
+        if (shouldRunKickstart(evictPaths.length)) {
+            const result = kickstartHmrPrefetch(evictPaths, options.verbose);
+            if (options.verbose && envVerbose && result) {
+                console.info(`[ns-hmr][angular] kickstart urls=${evictPaths.length} fetched=${result.fetched} ok=${result.ok ? 'yes' : 'no'} ms=${result.ms}`);
+            }
+        }
+        else if (options.verbose && envVerbose) {
+            console.info(`[ns-hmr][angular] kickstart skipped urls=${evictPaths.length} cap=${Number.isFinite(kickstartMaxUrls) ? kickstartMaxUrls : 'Infinity'} (eviction set too large; falling back to sequential fetch)`);
+        }
+    }
+    // URL strategy:
+    //
+    // * `evicted=true`  → modern runtime accepted the eviction; we
+    //   re-import the entry under its STABLE canonical URL. V8's
+    //   registry no longer holds the evicted modules so the import
+    //   triggers fresh fetches for them; the rest of the graph is a
+    //   cache hit.
+    // * `evicted=false` → either we have no eviction set (older server)
+    //   or the runtime lacks `__nsInvalidateModules` (older runtime).
+    //   Fall back to the legacy `__ns_hmr__/v<version>/` URL pattern so
+    //   V8 sees a fresh URL and re-fetches the entry. The runtime
+    //   canonicalizer collapses the path back to the stable key, which
+    //   keeps cache identity consistent across saves.
+    const versionRaw = typeof msg?.version === 'number' ? msg.version : 0;
+    const useStableUrls = evicted;
+    let lastError;
+    // 'reimporting' is the entry point for the long tail of an HMR
+    // cycle: V8 walks the freshly-evicted graph and the iOS runtime
+    // re-fetches each node from the dev server. We announce the stage
+    // once, before the loop, so the user sees a progress jump even when
+    // the import resolves on the first candidate (the common case).
+    setUpdateOverlayStage('reimporting', {
+        detail: 'Re-importing Angular bootstrap entry',
+    });
+    for (const entry of getAngularBootstrapEntryCandidates(msg)) {
+        const url = useStableUrls ? `${origin}/ns/m${entry}` : versionRaw ? `${origin}/ns/m/__ns_hmr__/v${versionRaw}${entry}` : `${origin}/ns/m${entry}`;
+        try {
+            g.__NS_ANGULAR_HMR_REGISTER_ONLY__ = true;
+            await importAngularBootstrapEntry(url);
+            return;
+        }
+        catch (error) {
+            lastError = error;
+        }
+        finally {
+            g.__NS_ANGULAR_HMR_REGISTER_ONLY__ = false;
+        }
+    }
+    if (options.verbose && envVerbose && lastError) {
+        console.warn('[hmr-angular] failed to refresh Angular bootstrap entry', lastError?.message || lastError);
+    }
+}
+export async function handleAngularHotUpdateMessage(msg, options) {
     if (!msg || msg.type !== 'ns:angular-update') {
         return false;
     }
+    // Cycle mutex. See `inFlightHmrCycle` for why this is necessary. We
+    // publish `thisCycle` *before* awaiting the previous one so a third
+    // concurrent message sees the latest in-flight, not the stale
+    // previous. This serializes N concurrent updates into a single FIFO
+    // chain.
+    const previousCycle = inFlightHmrCycle;
+    let resolveCycle;
+    const thisCycle = new Promise((resolve) => {
+        resolveCycle = resolve;
+    });
+    inFlightHmrCycle = thisCycle;
+    if (previousCycle) {
+        try {
+            await previousCycle;
+        }
+        catch { }
+    }
+    // Single-line log lands in iOS device console as `CONSOLE INFO` so the user can
+    // correlate with the server's `[hmr-ws][update] ...` line and see
+    // where the save's wall time actually goes (refresh vs. reboot).
+    const t0 = Date.now();
+    let tAfterRefresh = t0;
+    let tEnd = t0;
+    const filePath = typeof msg?.path === 'string' ? msg.path : '<unknown>';
+    const emitTiming = (ok, errorMessage) => {
+        const refreshMs = Math.max(0, tAfterRefresh - t0);
+        const rebootMs = Math.max(0, tEnd - tAfterRefresh);
+        const totalMs = Math.max(0, tEnd - t0);
+        const status = ok ? 'ok' : 'FAILED';
+        const suffix = errorMessage ? ` error=${errorMessage}` : '';
+        console.info(`[ns-hmr][angular] ${status} file=${filePath} refresh=${refreshMs}ms reboot=${rebootMs}ms total=${totalMs}ms${suffix}`);
+    };
+    // Show the apply-progress overlay as soon as the
+    // mutex unblocks us. Posting this *after* the awaited
+    // previousCycle keeps each cycle's stages visually grouped in the
+    // overlay (cycle-1 finishes its 'complete' before cycle-2's
+    // 'received' overrides it).
+    //
+    // The detail line surfaces the changed file path so the user can
+    // confirm at a glance which save the overlay is reflecting.
+    const overlayDetail = filePath && filePath !== '<unknown>' ? `Updating ${filePath}` : 'Preparing update';
+    setUpdateOverlayStage('received', { detail: overlayDetail });
     try {
         const g = globalThis;
-        const App = options.getCore('Application') || g.Application;
-        const bootstrap = g.__NS_ANGULAR_BOOTSTRAP__;
-        if (typeof App?.resetRootView === 'function' && typeof bootstrap === 'function') {
-            if (options.verbose && __NS_ENV_VERBOSE__) {
-                console.log('[hmr-angular] resetting root view via captured bootstrap');
+        // Vite-spec entry: `vite:beforeUpdate` fires as soon as the
+        // client receives an update message, BEFORE any work begins
+        // (refresh, dispose, reboot). User listeners can use this to
+        // pause animations, cancel in-flight requests, etc. Payload
+        // matches Vite's `Update[]` shape loosely — `path` is the
+        // canonical changed file, `evictPaths` is the eviction
+        // closure the server already computed.
+        const updatePayload = {
+            type: 'js-update',
+            path: typeof msg?.path === 'string' ? msg.path : null,
+            evictPaths: Array.isArray(msg?.evictPaths) ? msg.evictPaths : [],
+            timestamp: t0,
+        };
+        dispatchHotEvent(g, 'vite:beforeUpdate', { updates: [updatePayload] });
+        // Declined-module short-circuit. If any updated module called
+        // `import.meta.hot.decline()`, we MUST do a full reload per
+        // Vite spec rather than the hot-update path. `triggerFullReload`
+        // also dispatches `vite:beforeFullReload`. The reload tears the
+        // JS realm down so we don't need to do any further bookkeeping
+        // here — return early.
+        if (checkDeclinedAndReload(g, msg, options)) {
+            tEnd = Date.now();
+            emitTiming(true);
+            return true;
+        }
+        // Prefer __reboot_ng_modules__ — it properly disposes existing modules,
+        // re-bootstraps Angular inside NgZone, and sets the root view internally.
+        // __NS_ANGULAR_BOOTSTRAP__ is exposed as a secondary signal that the
+        // Angular HMR system is ready, but __reboot_ng_modules__ is the
+        // canonical reboot entry point.
+        const reboot = g.__reboot_ng_modules__;
+        if (typeof reboot === 'function') {
+            if (options.verbose && envVerbose) {
+                console.info('[ns-hmr-diag][client] calling __reboot_ng_modules__');
             }
+            await refreshAngularBootstrapOptions(msg, options);
+            tAfterRefresh = Date.now();
+            try {
+                g.__NS_HMR_IMPORT_NONCE__ = (typeof g.__NS_HMR_IMPORT_NONCE__ === 'number' ? g.__NS_HMR_IMPORT_NONCE__ : 0) + 1;
+            }
+            catch { }
             try {
                 g.__NS_DEV_RESET_IN_PROGRESS__ = true;
             }
             catch { }
-            App.resetRootView({
-                create: () => {
-                    try {
-                        return bootstrap();
-                    }
-                    finally {
-                        try {
-                            g.__NS_DEV_RESET_IN_PROGRESS__ = false;
-                        }
-                        catch { }
-                    }
-                },
+            // Two-phase pre-reboot cleanup. Order matters: dispose runs
+            // FIRST so user-code disposers see a still-live runtime
+            // (sockets, workers, etc.) and can issue graceful "I'm
+            // going away" messages; then we hard-terminate any worker
+            // the user didn't manually clean up.
+            //
+            // Phase 1 — `import.meta.hot.dispose(cb)` callbacks
+            // ────────────────────────────────────────────────
+            // The NS iOS runtime exposes
+            // `globalThis.__nsRunHmrDispose()` (registered in
+            // `Worker.mm`'s sibling `HMRSupport.mm`). It walks
+            // `g_hotDispose` — the per-module callback registry that
+            // `import.meta.hot.dispose(cb)` populates — and invokes
+            // every callback with that module's `hot.data` object,
+            // matching the Vite spec. Soft-fails on older runtimes
+            // without the API (call is optional-chained).
+            //
+            // This is the standards-compliant cleanup hook every Vite
+            // user already knows. Apps register their intervals,
+            // listeners, sockets, store subscriptions, etc. via
+            // `import.meta.hot.dispose(...)` and they're guaranteed to
+            // fire before the next Angular reboot — no NS-specific
+            // knowledge required.
+            runHmrDisposeCallbacks(g, options);
+            // Phase 2 — worker auto-terminate (defence in depth)
+            // ───────────────────────────────────────────────────
+            // Even with perfect dispose() coverage, workers spawned
+            // from constructors that re-run on Angular reboot (e.g.
+            // `new Worker(...)` inside `AppComponent`'s constructor)
+            // don't fire dispose for `app.component.ts` when only
+            // `login.component.html` changes — `app.component.ts`
+            // isn't being replaced, so its disposers don't run per
+            // Vite spec. The runtime API
+            // `__nsTerminateAllWorkers()` doesn't care about module
+            // boundaries; it just kills every live worker in
+            // `Caches::Workers`. Falls back to the
+            // `__NS_HMR_WORKERS__` JS Set on older runtimes.
+            terminateTrackedWorkers(g, options);
+            // 'rebooting' marks the long tail of the cycle: NgZone
+            // teardown, module re-instantiation, and resetRootView.
+            // The detail line shows refresh-so-far ms so a user can
+            // already see if the slow phase is re-import or reboot.
+            setUpdateOverlayStage('rebooting', {
+                detail: `Re-bootstrapping Angular (refresh ${Math.max(0, tAfterRefresh - t0)}ms)`,
+            });
+            try {
+                reboot(true);
+            }
+            finally {
+                try {
+                    g.__NS_DEV_RESET_IN_PROGRESS__ = false;
+                }
+                catch { }
+            }
+            tEnd = Date.now();
+            emitTiming(true);
+            // Vite-spec exit: `vite:afterUpdate` fires after the update
+            // has been successfully applied. User code can re-attach
+            // any state torn down by `vite:beforeUpdate` (resume
+            // animations, re-fetch, etc.). Same payload shape as
+            // `vite:beforeUpdate` so listeners can correlate.
+            dispatchHotEvent(g, 'vite:afterUpdate', { updates: [updatePayload] });
+            // 'complete' surfaces the wall-clock total so a user gets a
+            // single-glance confirmation matching the [ns-hmr][angular]
+            // log line in the terminal. The overlay auto-hides shortly
+            // after.
+            setUpdateOverlayStage('complete', {
+                detail: `Total ${Math.max(0, tEnd - t0)}ms`,
             });
             return true;
         }
-        if (options.verbose && __NS_ENV_VERBOSE__) {
-            console.warn('[hmr-angular] Missing global __NS_ANGULAR_BOOTSTRAP__ factory. Set it in your main.ts to enable HMR resets.');
+        if (options.verbose && envVerbose) {
+            console.warn('[hmr-angular] No Angular HMR handler found. Ensure runNativeScriptAngularApp() has been called.');
         }
+        tEnd = Date.now();
+        emitTiming(false, 'no-reboot-handler');
+        // No reboot handler → we can't apply the update; hide the
+        // overlay rather than leaving stale progress on screen.
+        hideUpdateOverlay();
     }
     catch (error) {
         if (options.verbose) {
-            try {
-                console.warn('[hmr-angular] failed to handle update', (error && error.message) || error);
-            }
-            catch { }
+            console.warn('[hmr-angular] failed to handle update', (error && error.message) || error);
+        }
+        tEnd = Date.now();
+        const errorMessage = (error && error.message) || String(error);
+        emitTiming(false, errorMessage);
+        // Vite-spec error event — fires on any HMR cycle that throws.
+        // Payload shape mirrors Vite's `ErrorPayload`: `err: { message,
+        // stack? }` plus optional `path`. Soft-fails if no listeners.
+        dispatchHotEvent(globalThis, 'vite:error', {
+            type: 'error',
+            err: {
+                message: errorMessage,
+                stack: (error && error.stack) || undefined,
+            },
+            path: typeof msg?.path === 'string' ? msg.path : undefined,
+        });
+        // Errors → drop the overlay so the user isn't left looking
+        // at indefinite progress; the underlying error is already
+        // logged above (and surfaced via Vite's standard error
+        // pipeline through the websocket).
+        hideUpdateOverlay();
+    }
+    finally {
+        try {
+            resolveCycle();
+        }
+        catch { }
+        if (inFlightHmrCycle === thisCycle) {
+            inFlightHmrCycle = null;
         }
     }
     return true;