Update dependency @angular-devkit/build-angular to v22

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@angular-devkit/build-angular	^21.2.11 → ^22.0.0

---

Release Notes

angular/angular-cli (@​angular-devkit/build-angular)

v22.0.5

Compare Source

@​angular/cli

Commit	Type	Description
f099e641c	fix	gracefully handle package manager errors in command handler
cf033ec48	fix	respect release age policy in update bootstrapping logic

@​schematics/angular

Commit	Type	Description
862a38069	fix	remove unused app tsconfig outDir

@​angular-devkit/build-angular

Commit	Type	Description
f75085f4b	fix	prevent OS command injection in ssr-dev-server builder

@​angular/build

Commit	Type	Description
dfee1e7b1	fix	auto-inject localize/init in library unit tests
aba718403	fix	inherit preserveSymlinks option from build target in unit-test builder
7c0d9f03c	fix	load zone.js dynamically for library unit tests
4288e4452	fix	scope createRequire module resolution using paths to prevent parent paths

@​angular/ssr

Commit	Type	Description
5f774f891	fix	preserve response headers during redirect

v22.0.4: 22.0.4

Compare Source

@​angular/build

Commit	Description
	aggregate parallel worker performance timings on the main thread
	dispose builder result context early in non-watch mode

v22.0.3

Compare Source

v22.0.2

Compare Source

@​angular/cli

Commit	Type	Description
136fc2714	fix	support registry metadata fetching under bun package manager
2653dd5c7	perf	implement semaphore backpressure throttling in PackageManager

@​angular/build

Commit	Type	Description
0b4a48add	perf	implement semaphore backpressure throttling in JavaScriptTransformer

@​angular/ssr

Commit	Type	Description
d996a27e9	fix	avoid caching non-SSG page lookups
285a34e42	fix	correct grammar in console warning for redirected location headers
c8088a536	fix	prioritize options over environment variables in AngularNodeAppEngine

v22.0.1

Compare Source

@​angular/cli

Commit	Type	Description
b54e9a549	fix	do not sort migrations of the same version alphabetically
d33311612	fix	fallback to local package.json for schematic detection on first run
918102a93	fix	isolate temporary package installation from parent pnpm workspace
b048b5f4a	fix	remove forceAuth and unscoped credential parsing
277934035	fix	validate registry option is a valid URL in ng add
4510dae02	perf	optimize update schematic registry query counts by fetching package metadata lazily

@​schematics/angular

Commit	Type	Description
c80012294	fix	fix browserMode option mapping in refactor-jasmine-vitest
a9b6bd904	fix	safely comment out multiline statements in refactor-jasmine-vitest
12199df00	fix	use null objects and callbacks in karma-to-vitest migration

@​angular/build

Commit	Type	Description
89d1be979	fix	allow disabling Vitest isolation from builder
d45b84be9	fix	exclude JSON imports from Vite dependency optimization
e3cab4ddd	fix	prevent concurrent stylesheet bundling esbuild context leaks
bd413b0eb	fix	restrict application builder output paths to output directory

v22.0.0

Compare Source

Breaking Changes

• Node.js v20 is no longer supported. The minimum supported Node.js versions are now v22.22.0 and v24.13.1.
• The @angular-devkit/architect-cli package is no longer available. The architect CLI tool has been moved to the @angular-devkit/architect package.
• The experimental @angular-devkit/build-angular:jest and @angular-devkit/build-angular:web-test-runner builders have been removed.

@​angular/build

• The @angular/build:dev-server (ng serve) now assigns the highest priority to the PORT environment variable. This value will override any port configurations specified in angular.json or via the --port command-line flag. This includes the default port 4200.
• istanbul-lib-instrument is now an optional peer dependency.
  Projects using karma with code coverage enabled will need to ensure that istanbul-lib-instrument is installed. Note: ng update will automatically add this dependency during the update process.

@​angular/ssr

• The server no longer falls back to Client-Side Rendering (CSR) when a request fails host validation. Requests with unrecognized 'Host' headers will now return a 400 Bad Request status code. Users must ensure all valid hosts are correctly configured in the 'allowedHosts' option.

Deprecations

@​angular-devkit/build-angular

• Webpack builders in build-angular are deprecated. Use @​angular/build builders instead.

@​angular-devkit/build-webpack

• Webpack builders in build-webpack are deprecated. Use @​angular/build builders instead.

@​angular/ssr

• CommonEngine APIs are deprecated in favor of AngularNodeAppEngine or AngularAppEngine.

@​ngtools/webpack

• @​ngtools/webpack loader and plugin are deprecated. Use @​angular/build instead.

@​angular/cli

Commit	Type	Description
58c0978f6	feat	add support for Node.js 26.0.0
a5c7c0b5f	fix	reflect new minimum supported Node version in ng.js
a5e1e48db	fix	update odd-numbered Node.js version warning condition for future releases
93c3eb8fb	fix	update zoneless migration tool to handle ChangeDetectionStrategy.Eager
a39a33128	perf	cache root manifest and resolve restricted package exports in ng add

@​schematics/angular

Commit	Type	Description
be60a63b7	feat	add migrate-karma-to-vitest update migration
43505066e	feat	add migration to add istanbul-lib-instrument
b2f7a038b	feat	conditionally install istanbul coverage provider for Vitest migration
d227e6985	feat	migrate fake async to Vitest fake timers
d2aa9ede5	feat	migrate fakeAsync's flush behavior when used in beforeEach
f98cc82eb	feat	rely on strict template default in generated workspaces
c9f408153	feat	set up fake timers in beforeEach instead of beforeAll
de630c2fc	feat	stabilize refactor-jasmine-vitest schematic
8d0805dd1	feat	update TSConfig globals during karma to vitest migration
470e1f937	fix	add istanbul-lib-instrument to application/library generator dependencies
dc1238e5a	fix	add trusted-proxy-headers migration
6572a6944	fix	default components to OnPush change detection
aed407db8	fix	defer karma config deletion in Karma to Vitest migration
4fbc60891	fix	preserve Jasmine stub-by-default semantics for bare spies
b3d838dfd	fix	replace deprecated ChangeDetectionStrategy.Default with Eager
a7ac8e5f0	fix	support spy call arguments migration in refactor-jasmine-vitest
7fb59eaa6	fix	use service decorator in ng generate

Commit	Type	Description
d0e9e8163	build	update minimum supported Node.js versions
1f21e89d9	refactor	remove @angular-devkit/architect-cli package
b4885b851	refactor	remove experimental Jest and Web Test Runner builders

@​angular-devkit/build-angular

Commit	Type	Description
b7940dbcb	refactor	deprecate Webpack builders

@​angular-devkit/build-webpack

Commit	Type	Description
3d5daa45e	refactor	deprecate webpack and webpack-dev-server builders

@​angular/build

Commit	Type	Description
e9aa7967b	feat	add isolate option to unit-test builder
fe720cab6	feat	add process.env.PORT support to the dev server
0781f7498	feat	add quiet option to suppress build noise in unit tests
cd2ad3c19	feat	enable chunk optimization by default with heuristics
3007f46b7	feat	move istanbul-lib-instrument to optional peer dependency
af2c7e944	feat	rename experimentalPlatform to platform in application builder
58c7c7a9d	feat	subresource integrity validation for dynamically loaded modules
73233dc5f	feat	support Istanbul coverage in Vitest runner
414320d02	feat	support runtime Zone.js detection in Vitest unit test runner
b85ec6798	fix	allow configuring Access-Control-Allow-Origin via headers option
edfa782d5	fix	use dynamic TestComponentRenderer for Vitest

@​angular/ssr

Commit	Type	Description
5adc92541	fix	enforce explicit opt-in for proxy headers
f85343925	fix	support all X-Forwarded-* headers when trustProxyHeaders is true
8471ba634	fix	support server-side rendering configuration options
50b16a65b	refactor	deprecate CommonEngine APIs
27cd35561	refactor	remove CSR fallback for invalid hosts

@​ngtools/webpack

Commit	Type	Description
547ca515b	refactor	deprecate @​ngtools/webpack loader and plugin

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

\n\n## Beta npm build\n\nMaintainers can publish this PR to npm for fast testing.\n\nComment `/publish-beta` after the PR checks are green.\n\nThe workflow will:\n- publish a prerelease package on the `beta` tag\n- add a pinned `pr-36` dist-tag for this exact PR build\n- update this comment with the install command\n\nSecurity note: beta publish is only enabled for branches inside this repository.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​angular-devkit/​build-angular@​21.2.11 ⏵ 22.0.5				-1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @angular-devkit/build-angular is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: examples/angular-app/package.json → npm/@angular-devkit/build-angular@22.0.5 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@angular-devkit/build-angular@22.0.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm @angular/build is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@angular-devkit/build-angular@22.0.5 → npm/@angular/build@22.0.5 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@angular/build@22.0.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm lmdb is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@angular-devkit/build-angular@22.0.5 → npm/lmdb@3.5.4 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/lmdb@3.5.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm webpack is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@angular-devkit/build-angular@22.0.5 → npm/webpack@5.106.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/webpack@5.106.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[cursor]

Risk: medium. This major @angular-devkit/build-angular bump (21→22) exceeds the low-risk approval threshold and needs human review, especially with @angular/* still on 21.x. Cursor Bugbot was not present on this PR; assigning riderx for review.

  

_{Sent by Cursor Approval Agent: Pull Request Approver External}