edit: we depend on NgRx itself, and they are still working on v22 support. But in the meantime, the overrides system I mentioned can make v21 NgRx and v21 NgRx Toolkit work in a v22 project.
The team is still discussing some particulars, so for now, apologies that this issue is really vague. But the bottom line is that we are reviewing the key pieces we need for a release, and will update this issue leading up to the release when it is ready.
In the meantime, you can use v21 of NgRx and the Toolkit. As per NgRx itself: "NgRx v21 still works with Angular v22".
There is 2 major approaches to achieve this:
package.json overrides approach.
"overrides": {
"@angular-architects/ngrx-toolkit": {
"@angular/common": "$@angular/common",
"@angular/core": "$@angular/core"
},
"@ngrx/signals": {
"@angular/common": "$@angular/common",
"@angular/core": "$@angular/core"
}
}
npm i --legacy-peer-deps approach
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.
edit: we depend on NgRx itself, and they are still working on v22 support. But in the meantime, the overrides system I mentioned can make v21 NgRx and v21 NgRx Toolkit work in a v22 project.
The team is still discussing some particulars, so for now, apologies that this issue is really vague. But the bottom line is that we are reviewing the key pieces we need for a release, and will update this issue leading up to the release when it is ready.
In the meantime, you can use v21 of NgRx and the Toolkit. As per NgRx itself: "NgRx v21 still works with Angular v22".
There is 2 major approaches to achieve this:
package.jsonoverridesapproach.npm i --legacy-peer-depsapproachI 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.