See associated pull request for more information.

See associated pull request for more information.

See associated pull request for more information.

See associated pull request for more information.

… manager abstraction

This change introduces the ability to specify a base temporary directory when creating a `PackageManager` instance. This allows for creating temporary directories within the project structure (e.g., `node_modules/.tmp`), which enables package managers to correctly inherit project-specific configurations like `.npmrc` or `.yarnrc` during operations like `acquireTempPackage`.

(cherry picked from commit 5fb3af0)

The 'ng add' command now attempts to use '.angular/cache' or 'node_modules' as the base for temporary directories when acquiring packages. This ensures that the package manager can inherit project-specific configuration (like '.npmrc' or '.yarnrc') during the installation of temporary packages.

The implementation uses a fallback strategy, checking for candidate directories and defaulting to the system's temporary directory if none are found.

(cherry picked from commit 2cd4f2d)

…on in ng add

This change enhances the error handling in the 'ng add' command's 'installPackageTask'. It now specifically catches 'PackageManagerError' exceptions and surfaces the standard output or standard error from the underlying package manager process. This provides users with more actionable information when a package installation fails.

(cherry picked from commit 158d715)

…directory

This change adds support for copying package manager configuration files (like `bunfig.toml`) from the project root to the temporary directory used for acquiring packages. This is particularly necessary for Bun, which does not automatically inherit configuration from parent directories when running in a separate temporary location.

(cherry picked from commit d58c714)

See associated pull request for more information.

Fixes crash when platform/app destroys itself during the bootstrapping and
stabilization phase. Previously, the code would call `applicationRef.injector`
without checking if the platform was destroyed, resulting in:
"Error: Injector has already been destroyed"

This can occur when:
- Component constructor calls `inject(PlatformRef).destroy()`
- AbortSignal triggers during request handling
- APP_INITIALIZER rejects and causes cleanup
- Custom guard/resolver logic destroys the platform

Solution: Check `applicationRef.destroyed` after `whenStable()` and return error
state instead of accessing destroyed injector.

Test: Added test case that destroys app in component constructor to
verify graceful handling of this edge case.

(cherry picked from commit fd1a209)

Update all copyright headers throughout the codebase to reflect the
current legal entity name. This is a non-functional change that only
affects the copyright notices in source files.

(cherry picked from commit 712f508)

…ar material link

Update all license URL references throughout the codebase to point to the
new angular.dev domain. This is a non-functional change that only
affects the license links in source file headers.

(cherry picked from commit 6ed2cb7)

See associated pull request for more information.

See associated pull request for more information.

See associated pull request for more information.