Which @ngrx/* package(s) are the source of the bug?
component-store, effects
Minimal reproduction of the bug/regression with instructions
There seems to be a mostly harmless but odd "issue" with @ngrx/effects and @ngrx/component-store packages where even the latest v18 releases depends on the old 17.0.0-beta.0 version of @ngrx/operators. That dependency is also specified via exact version so even though newer versions are available, that old one will be installed and used.
Which @ngrx/* package(s) are the source of the bug?
component-store, effects
Minimal reproduction of the bug/regression with instructions
There seems to be a mostly harmless but odd "issue" with
@ngrx/effects
and@ngrx/component-store
packages where even the latest v18 releases depends on the old17.0.0-beta.0
version of@ngrx/operators
. That dependency is also specified via exact version so even though newer versions are available, that old one will be installed and used.https://github.com/ngrx/platform/blob/c9c646c7a1b5123d263a0b0df49d3049bafb3a56/modules/component-store/package.json#L47 https://github.com/ngrx/platform/blob/c9c646c7a1b5123d263a0b0df49d3049bafb3a56/modules/component-store/package.json#L47
Expected behavior
@ngrx/operators
not to be a-beta
release and to match the base package version 😀Versions of NgRx, Angular, Node, affected browser(s) and operating system(s)
@ngrx/component-store: >=17.0.0 @ngrx/effects: >=17.0.0
Other information
No response
I would be willing to submit a PR to fix this issue