/**
 * Resolve Angular package paths from the compiled runtime node_modules first,
 * then the app's process.cwd()/node_modules, falling back to the bare specifier.
 * This prevents Bun's baked import.meta.dir from resolving Angular packages
 * from the absolutejs source tree instead of the consumer's project when
 * running from a published npm package.
 */
export declare const resolveAngularPackageDir: (specifier: string) => string | null;
export declare const resolveAngularPackage: (specifier: string) => string;
/** Prefer the linked Bun-target vendor file built by
 *  `buildAngularServerVendor`. The file is at
 *  `<ABSOLUTE_BUILD_DIR>/angular/vendor/server/<safe>.js`, which is what every
 *  server bundle's `@angular/*` imports get rewritten to point at. Sharing
 *  this path keeps SSR's class identity unified — the dual-package hazard
 *  that produces NG0201 only appears when the runtime imports a *different*
 *  copy from the bundles. Falls back to `resolveAngularPackage` (node_modules)
 *  when no vendor file is available — e.g. running tests outside an
 *  absolutejs build, or before the vendor pass completes. */
export declare const resolveAngularRuntimePath: (specifier: string) => string;