@nativescript/angular 21.0.1-alpha.5 → 21.0.1-alpha.6

package/fesm2022/nativescript-angular.mjs

@@ -7447,13 +7447,20 @@ const DEFAULT_INVALIDATE_EVENT = 'ns:cache-invalidate';
  * type is the only one in play; `vite/client`-aware apps still get
  * their own typing on `import.meta.hot` at every call site outside
  * this module.
+ *
+ * Webpack-CommonJS compatibility: every `import.meta` reference here
+ * is a member expression (`import.meta['hot']`). Webpack statically
+ * rewrites both dot- and bracket-style member access to `undefined`
+ * in CommonJS output, so the emitted bundle never carries a literal
+ * bare `import.meta` token. A bare `import.meta` would survive into
+ * the bundle and crash V8 with "Cannot use 'import.meta' outside a
+ * module" the moment the chunk is `require()`d. Vite leaves
+ * `import.meta['hot']` intact and resolves it to the per-module hot
+ * context, so the same code works in both pipelines.
  */
 function readImportMetaHot() {
     try {
-        const meta = typeof import.meta !== 'undefined'
-            ? import.meta
-            : undefined;
-        return meta?.hot;
+        return import.meta['hot'];
     }
     catch {
         return undefined;
@@ -7879,10 +7886,12 @@ function getOrCreateSharedStore() {
 }
 function hasImportMetaHot() {
     try {
-        const meta = typeof import.meta !== 'undefined'
-            ? import.meta
-            : undefined;
-        return !!meta?.hot;
+        // Member-expression access only — webpack rewrites `import.meta['hot']`
+        // to `undefined` in CommonJS bundles (so `!!undefined` → `false`),
+        // while Vite leaves it as the per-module hot context. A bare
+        // `typeof import.meta` would survive into the bundle and crash V8
+        // with "Cannot use 'import.meta' outside a module" on `require()`.
+        return !!import.meta['hot'];
     }
     catch {
         return false;