@absolutejs/absolute 0.19.0-beta.736 → 0.19.0-beta.737

package/dist/src/build/buildAngularVendor.d.ts

@@ -2,8 +2,17 @@
  *  `linkerJitMode` controls whether NgModule definitions retain their
  *  declarations/exports — required when consumer (user) components are
  *  runtime-compiled by `@angular/compiler` (dev/HMR via compileAngularFileJIT).
- *  Production AOT builds set this to false to match AOT'd user components. */
-export declare const buildAngularVendor: (buildDir: string, directories?: string[], linkerJitMode?: boolean) => Promise<string[]>;
+ *  Production AOT builds set this to false to match AOT'd user components.
+ *
+ *  `depVendorSpecifiers` are non-framework packages that are also vendored
+ *  separately (by `buildDepVendor`). They MUST be externalized here too —
+ *  otherwise transitive imports like `@angular/fire/compat/auth` →
+ *  `firebase/compat/auth` get bundled twice, creating duplicate
+ *  @firebase/app-compat instances. The angular-vendor copy registers
+ *  `firebase.auth.*` on its own firebase singleton, leaving the user's
+ *  `import firebase from 'firebase/compat/app'` with `firebase.auth` undefined.
+ *  Externalizing forces both pipelines to share the same /vendor chunks. */
+export declare const buildAngularVendor: (buildDir: string, directories?: string[], linkerJitMode?: boolean, depVendorSpecifiers?: string[]) => Promise<string[]>;
 export declare const computeAngularVendorPaths: (specifiers?: string[]) => Record<string, string>;
 /** Async variant that scans source + transitive deps before producing the
  *  vendor path map. Use this when the page-bundle build needs the full set of

package/package.json

@@ -336,5 +336,5 @@
 			]
 		}
 	},
-	"version": "0.19.0-beta.736"
+	"version": "0.19.0-beta.737"
 }