@absolutejs/absolute 0.19.0-beta.970 → 0.19.0-beta.971

package/dist/src/angular/loadGlobalProviders.d.ts

@@ -0,0 +1,7 @@
+import type { EnvironmentProviders, Provider } from '@angular/core';
+/** Derive the manifest key (PascalCase basename) from the page's
+ *  resolved source path. Matches `generateManifest`'s convention for
+ *  Angular `pages/` so `home/home.ts` → `Home`,
+ *  `portal/portal.ts` → `Portal`, etc. */
+export declare const manifestKeyForPagePath: (pageSourcePath: string) => string;
+export declare const loadPageProviders: (pageSourcePath: string) => Promise<ReadonlyArray<Provider | EnvironmentProviders>>;

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

@@ -11,7 +11,13 @@ export type EmittedProvidersFile = {
     /** `true` when the call carried a `providers:` argument. */
     hasProviders: boolean;
 };
-export declare const emitAngularProvidersFiles: (projectRoot: string, calls: AngularHandlerCall[], pageRoutes: AngularPageRoutes[]) => EmittedProvidersFile[];
+export type EmitAngularProvidersOptions = {
+    /** Project-relative path to the global providers module (exports
+     *  `appProviders`). The emitted files re-import it so each page's
+     *  generated providers always include the user's global setup. */
+    providersImport?: string;
+};
+export declare const emitAngularProvidersFiles: (projectRoot: string, calls: AngularHandlerCall[], pageRoutes: AngularPageRoutes[], options?: EmitAngularProvidersOptions) => EmittedProvidersFile[];
 /** Absolute path of the directory the emitter writes to. Exposed so other
  *  build steps (`compileAngular`'s client wrapper, the SSR `pageHandler`)
  *  can compute relative paths to the generated files without hard-coding

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

@@ -9,4 +9,11 @@ export type AngularHandlerScanResult = {
      *  client bundle can import. */
     manifestKeysWithProviders: Set<string>;
 };
-export declare const runAngularHandlerScan: (projectRoot: string, angularDirectory: string) => AngularHandlerScanResult;
+export type AngularHandlerScanOptions = {
+    /** Project-relative path to the user's global Angular providers
+     *  module (must export `appProviders`). When set, every generated
+     *  providers file re-imports it so pages and per-handler calls
+     *  never write providers themselves. */
+    providersImport?: string;
+};
+export declare const runAngularHandlerScan: (projectRoot: string, angularDirectory: string, options?: AngularHandlerScanOptions) => AngularHandlerScanResult;

package/dist/src/utils/loadConfig.d.ts

@@ -12,6 +12,9 @@ export declare const loadConfig: (configPath?: string) => Promise<{
     reactDirectory?: string;
     vueDirectory?: string;
     angularDirectory?: string;
+    angular?: {
+        providersImport?: string;
+    };
     astroDirectory?: string;
     svelteDirectory?: string;
     emberDirectory?: string;

package/dist/types/build.d.ts

@@ -135,6 +135,17 @@ export type BaseBuildConfig = {
     reactDirectory?: string;
     vueDirectory?: string;
     angularDirectory?: string;
+    /** Per-framework Angular config. Currently exposes `providersImport` —
+     *  a project-relative path to a module that exports `appProviders`
+     *  (the global default DI providers every page receives at SSR + client
+     *  bootstrap). The framework imports this module from both the
+     *  generated client bundle and the SSR handler so the two trees are
+     *  identical. Per-page additions (e.g. `provideRouter(routes)`) come
+     *  from page-level `export const routes` and are auto-wired by the
+     *  build — users never write `provideRouter` themselves. */
+    angular?: {
+        providersImport?: string;
+    };
     astroDirectory?: string;
     svelteDirectory?: string;
     emberDirectory?: string;

package/package.json

@@ -402,5 +402,5 @@
 			]
 		}
 	},
-	"version": "0.19.0-beta.970"
+	"version": "0.19.0-beta.971"
 }