You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which @ngrx/* package(s) are relevant/related to the feature request?
signals
Information
For those looking to upgrade to NgRx v19 along with Angular v19, just wanted to post some general notes as we go through this each release cycle.
We're still working on getting the release out.
NgRx v18 still works with Angular v19.
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 v18 package.json to go past Angular v18 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 its ready.
Thanks in advance,
The NgRx Team
Describe any alternatives/workarounds you're currently using
No response
I would be willing to submit a PR to fix this issue
Yes
No
The text was updated successfully, but these errors were encountered:
Thanks for mentioning this, the issue like this but for when Angular 18 came out helped me.
For people who may want an alternative so the install peer deps option doesn't need to be used on the CLI / CI every time is to put the following in a package.json
// Applicable to any ngrx package
"overrides": {
"@ngrx/signals": {
"@angular/common": "$@angular/common",
"@angular/core": "$@angular/core"
}
}
Which @ngrx/* package(s) are relevant/related to the feature request?
signals
Information
For those looking to upgrade to NgRx v19 along with Angular v19, just wanted to post some general notes as we go through this each release cycle.
We're still working on getting the release out.
npm
npm i --legacy-peer-deps
.package.json
to go past Angular v18 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 its ready.
Thanks in advance,
The NgRx Team
Describe any alternatives/workarounds you're currently using
No response
I would be willing to submit a PR to fix this issue
The text was updated successfully, but these errors were encountered: