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

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

@@ -2,10 +2,27 @@ import type { BunPlugin } from 'bun';
 /**
  * Bun bundler plugin that runs the Angular Linker on partially compiled
  * Angular libraries at build time. Converts ɵɵngDeclare* declarations
- * into fully AOT-compiled code so @angular/compiler is not shipped to
- * the browser.
+ * into fully linked code.
  *
- * Uses a disk cache keyed by file content hash — Babel only runs once
- * per Angular package version. Subsequent builds are pure file reads.
+ * The `linkerJitMode` flag controls whether NgModule definitions retain
+ * `declarations`/`exports` (JIT-mode, required when consumer code is
+ * runtime-compiled) or strip them (AOT-mode, smaller output but only
+ * correct when consumer components have ɵcmp.dependencies baked in by
+ * the Angular compiler-cli).
+ *
+ * In AbsoluteJS dev/HMR, user components are TypeScript-transpiled via
+ * `compileAngularFileJIT` and rely on @angular/compiler at runtime —
+ * that runtime JIT path reads `NgModule.ɵmod.declarations` to find
+ * directives like FormGroupDirective. Linking vendor code in AOT mode
+ * (the default) silently breaks dev because declarations get stripped
+ * and runtime JIT then can't resolve `[formGroup]`, `[ngIf]`, etc. So
+ * dev/HMR builds must use `linkerJitMode: true`. Production AOT builds
+ * use `linkerJitMode: false` (matches AOT'd user components).
+ *
+ * Cache key includes mode so dev and prod artifacts don't collide.
  */
+export declare const createAngularLinkerPlugin: (linkerJitMode: boolean) => BunPlugin;
+/** Default AOT-mode plugin instance — keep for callers that don't need
+ *  to choose. Production AOT builds and any callsite that AOT-compiles
+ *  user components alongside vendor should use this. */
 export declare const angularLinkerPlugin: BunPlugin;

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

@@ -1,5 +1,18 @@
-/** Build vendor bundles for every @angular/* package the project imports. */
-export declare const buildAngularVendor: (buildDir: string, directories?: string[]) => Promise<string[]>;
+/** Build vendor bundles for every @angular/* package the project imports.
+ *  `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.
+ *
+ *  `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.735"
+	"version": "0.19.0-beta.737"
 }