PSA: Angular v21 and NgRx v21
Information
For those looking to upgrade to NgRx v21 along with Angular v21, we would like to post some general notes as we go through this each release cycle.
We're still working on getting the release out.
- NgRx v20 still works with Angular v21.
- Until then, you may need to install using the legacy peer deps option with
npmnpm i --legacy-peer-deps. - We won't be bumping the NgRx v20
package.jsonto go past Angular v20 package versions. Our stance has been to keep each major release of NgRx aligned with each major release of Angular.
As this project is maintained by open source contributors in their free time, we try to work at a sustainable pace. You can support us by sponsoring the project or leveling up your team through one of our workshops.
We will have the release out as soon as it's ready.
Thanks in advance, The NgRx Team
For those who want an alternative to the legacy peer deps command, you can specify "overrides" in a package.json like this: https://github.com/ngrx/platform/issues/4787#issuecomment-2927617033
Guys, would you consider specifying the minimum angular version rather than the exact one? At least by +1 from the current one. For example for v20:
"peerDependencies": {
"@angular/core": ">=20 <22"
},
Guys, would you consider specifying the minimum angular version rather than the exact one? At least by +1 from the current one. For example for v20:
"peerDependencies": { "@angular/core": ">=20 <22" },
Indeed, that is the approach taken by @angular/material :
"peerDependencies": {
[...]
"@angular/core": "^21.0.0 || ^22.0.0",
"@angular/common": "^21.0.0 || ^22.0.0",
[...]
}
It allows the possibility to test quickly with the next version, without having to use workarounds. You have no reason to deny your users the possibility to at least try if it works ?
NgRx v21.0.0-beta.0 has been released! 🤝
@markostanimirovic as I was looking on this post and on the workshops part I just saw that the Upcoming Workshops section is outdated.