Introduces an automated macro performance benchmark suite for the i18n inlining subsystem in @angular/build, executable via the benchmark command.

The suite generates synthetic in-memory bundles, source maps, and translation catalogs to evaluate realistic workloads without checking large test fixtures into the repository.

Benchmark scenarios cover standard applications with and without source maps, enterprise multilingual applications across 32 locales, monolithic bundles to verify 2D task sharding, and warm persistent cache throughput.

Each scenario is executed in an isolated child process, and persistent cache priming is performed out-of-process to avoid cross-scenario memory contamination from the OS memory allocator. The harness collects high-precision timing, peak heap, peak RSS, and memory deltas with explicit garbage collection support.

The runner is integrated into devkit-admin with support for baseline comparison, machine-readable JSON output, stale build detection, and automatic rebuilds.

(cherry picked from commit 2a636a7)

Adds a large-scale stress test scenario to the i18n inliner benchmark suite with 10,000 translation messages across 32 locales. The scenario generates a 3 MB main bundle and 100 route chunks with source maps, evaluating binary translation catalog encoding, small file batching, and memory scaling under maximum enterprise workloads.

(cherry picked from commit d285bd8)

See associated pull request for more information.

See associated pull request for more information.

Translation inlining and sourcemap remapping are CPU- and memory-intensive operations. When Piscina is initialized without explicit maxThreads, it defaults to floor(cpus * 1.5), spawning 18 to 48 worker threads on high-core machines. This excessive concurrency causes severe thread oversubscription, memory allocator lock contention, and high-core performance degradation under Promise.all barriers.

This change introduces maxInlinerWorkers in environment options defaulting to min(8, availableParallelism()) while preserving explicit overrides via NG_BUILD_MAX_WORKERS. Concurrency passed to I18nInliner in the application builder is bounded to maxInlinerWorkers, capping standalone workers and shared worker pools while honoring shared pool thread limits when lower.

(cherry picked from commit 93c118e)

…mmand descriptions"

This reverts commit 3d7f081.

See associated pull request for more information.

…yling utilities

(cherry picked from commit d0eb6b6)

…insensitivity in auto-CSP

Previously, isJavascriptMimeType() in auto-csp.ts only performed a case-sensitive check against 'text/javascript' on the slice prior to the first semicolon.

This caused several issues:
1. Valid and common JavaScript MIME types specified in the HTML Living Standard such as application/javascript and text/ecmascript were not recognized as JavaScript.
2. Case differences (e.g. type="text/JavaScript" or type="Module") were not matched, despite HTML attribute matching and MIME types being ASCII case-insensitive.
3. Whitespace around the essence (e.g. type="text/javascript ; charset=utf-8" or type=" text/javascript") caused the strict equality check to fail.

When a script tag with one of these valid types was not recognized, auto-csp bypassed dynamic script rewriting and emitted the script element as-is into index.html. Under the generated strict CSP, the browser would then block the script from executing.

This change introduces JAVASCRIPT_MIME_TYPES containing all HTML-standard JavaScript MIME types, normalizes the essence (stripping parameters, trimming surrounding whitespace, and lowercasing), and updates shouldDynamicallyLoadScriptTagBasedOnType to support case-insensitive module types.

(cherry picked from commit 8e1b202)

…tion error

An unknown property in `angular.json` or in a builder's options reported
`Data path "" must NOT have additional properties(allowedCommonJsDependencies).`,
which names neither the object the property was found in nor what is valid
there. It now reads `Unknown option "allowedCommonJsDependencies". Valid
options are: assets, browser, ...`, with `at "/cli"` where the instance path
is not empty. Errors that are not about an unknown option are unchanged.

Listing the valid options needs ajv's `verbose` option, which is what puts
`parentSchema` on an error. That is the schema the property was rejected by, so
a `$ref` and a `oneOf` branch each list their own options; a schema that
declares no `properties` at all stops after the option name rather than
offering an empty list.

(cherry picked from commit 8c43889)

…cepts

`ng new --ssr` and `ng add @angular/ssr` fail to install their dependencies:
the server schematic adds `@types/node@^20.17.19`, and vitest 5, which the
same schematics now add, has `@types/node@^22.0.0 || >=24.0.0` as a peer.
npm refuses the tree and the workspace is left without `node_modules`.

`^22.12.0` is what this repository uses for `@types/node` itself, and Node 20
is already outside the `engines.node` range of the generated project.

(cherry picked from commit 1627ccb)

When initializing chokidar.watch with ignoreInitial: true, files visited during the initial scan are treated as the initial baseline and do not emit change events. If createChokidarWatcher returns before the initial scan completes, subsequent file modifications made shortly after setup can be visited for the first time during the initial scan, causing the change event to be dropped.

(cherry picked from commit dc79270)