PSA: Angular v19 and NgRx v19

[timdeschryver]

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 npm npm 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

Update 26 Nov: Version 19.0.0-beta.0 is now available, keep in mind that there will be breaking changes added in next versions before we publish a release candidate.

[michael-small]

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"
    }
  }

[salztorte]

@michael-small
Is a possible workaround, but is not really something I want to have for production.
Would be nice, ngrx can be release a new version, so the workaround is not needed.

In the main branch, the dependency is already updated. Just a new release is missing.

[rainerhahnekamp]

@salztorte, once we release, there won’t be room for breaking changes for at least the next six months. Therefore, if there are features that require only a few days to implement but involve breaking changes, it’s better to address them now rather than in May 2025.

[salztorte]

@rainerhahnekamp I totally understand that a lib can not just update stuff or do breaking changes.
It just would be nice to have an EST for better planning.

[rainerhahnekamp]

Sure, this one has the breaking change and must be merged: #4607

I cannot give you an exact EST but looking at the PR, it looks very ready.

[timdeschryver]

Version 19.0.0-beta.0 is now available, keep in mind that there will be breaking changes added in next versions before we publish a release candidate.