PSA: Angular v22 and NgRx v22

[markostanimirovic]

Information

For those looking to upgrade to NgRx v22 along with Angular v22, 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 v21 still works with Angular v22.
• Until then, you may need to install using the legacy peer deps option with npm: npm i --legacy-peer-deps.
• We won't be bumping the NgRx v21 package.json to go past Angular v21 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

[michael-small]

An alternative to --legacy-peer-deps that I personally recommend.

  "overrides": {
    "@ngrx/signals": {
      "@angular/common": "$@angular/common",
      "@angular/core": "$@angular/core"
    }
  }

I personally like the overrides approach as it is one and done and doesn't require both you/your corworkers and your entire CI process to always need to pass a flag. I have been using this approach for months in personal projects with the prerelease versions of Angular 22, and I will do this in the meantime in serious projects using Angular 22 stable.