Repository navigation
Angular 22 support #91
Description
Hi, is there any plan to support Angular 22 ?
Except conflicts on install (the same as : #75), that I was able to force with :
"overrides": {
"angular-three": {
"@angular/common": "$@angular/common",
"@angular/core": "$@angular/core"
},
"angular-three-soba": {
"@angular/common": "$@angular/common",
"@angular/core": "$@angular/core"
},
"angular-three-postprocessing": {
"@angular/common": "$@angular/common",
"@angular/core": "$@angular/core"
}
},
It seems to be working fine.
Reacted by kheos31, Benedikt Müll, René Keller, Mickaël Martinez and Bogdan Lončar
Activity
kheos31 commentedon Sep 22, 2026
Please could you just publish an Angular 22 version ?
Thanks in advance and have a nice day
qagwaai commentedon Oct 24, 2026
I investigated adding Angular 22 support. The current Angular libraries cap peer dependencies at <22. Angular 22.2 is available, but the current @nx/angular@23.0.1 peer range excludes it; Nx 24 allows Angular 22.
In an exploratory branch, I updated the workspace to Angular 22/Nx 24 and ran the nine library test and build targets. They passed at the last verified checkpoint. However, the upgrade is not just package version changes: Nx 24 removes Vite helpers and changes project target configuration, and TypeScript 6 exposes plugin-generator type errors. Lint remains unresolved, so this is not ready as a PR.
One additional Angular 22 issue surfaced: @angular/compiler-cli@22.2.3 imports encodeRangeMappings, but its declared codec range allowed pnpm to resolve a version without that export. A scoped override resolved the test/build failure in this workspace, but I’d like to confirm whether this is a known upstream packaging issue before proposing that workaround.
@nartc Would you prefer that Angular 22 support be pursued on Nx 24, with the Nx migration handled separately first, or should we investigate whether Angular 22 can be supported while keeping the current Nx major?