npm / ng-packagr
ng-packagr
What changed in ng-packagr 21 to 22, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-19.
3 breaking4 behavior and defaults2 tooling10 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli initng-packagr 2217 changes
Breaking changes 3
The peer dependency is updated to support Angular v22.
Node.js 20 is no longer supported; the minimum supported versions are v22.22.0 and v24.13.1, and Node.js 26 is supported.
TypeScript versions older than 6.0 are no longer supported, while TypeScript 6 is supported as a peer dependency.
Behavior and default changes 3
Reverts parallel entry point scheduling.
Legal and annotation comments are preserved while other comments are removed from JavaScript bundles.
Supported browsers are transformed to targets using the lowest version.
Tooling 2
Spinners are disabled during parallel entry-point builds.
Rolldown replaces Rollup in ng-packagr.
Fixes and other changes 9
TS6059 is ignored on Angular compiler generated shims.
A parallel index.ts is rejected only when it is imported.
Schema validation errors now name the unknown option.
Logs the correct diagnostics array for warnings.
Prevents concurrent compilation and stale cache results.
Generates specific .npmignore entries for secondary entry-point package.json files, fixing how those files are handled in the package.
The angularDiagnosticCache is invalidated when HTML files change.
DTS sourcemaps now point to the original TypeScript files.
Package.json files with export subpaths are now handled.
ng-packagr 212 changes
Behavior and default changes 1
Generated package.json files now default type to module.
Fixes and other changes 1
Rollup now resolves imports with TypeScript extensions.