Platform: ng update @angular/core (to angular 6.0) fails with 'Package "@ngrx/store-devtools" has an incompatible peer dependency to "rxjs" (requires "^5.5.0", would install "6.1.0").'

[scottleedavis]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ *] Bug report  
[ ] Feature request
[ ] Documentation issue or request

What is the current behavior?

when updating @ngrx/store-dev-tools 5.2, and ng update @angular/core to 6.0, fails as a peer dependency with the following error
ng update @angular/core Package "@ngrx/store-devtools" has an incompatible peer dependency to "rxjs" (requires "^5.5.0", would install "6.1.0"). Incompatible peer dependencies found. See above.

Expected behavior:

ng update @angular/core would pass without error when moving from 5.2 to 6.0

Minimal reproduction of the problem with instructions:

ng update @angular/core

Version of affected browser(s),operating system(s), npm, node and ngrx:

node v9.7.1
npm 5.6.0
Angular CLI: 6.0.0

Other information:

[scottleedavis]

it appears we are still in beta for 6.x stuff. will try those (and wait for new release)

[gioragutt]

@brandonroberts @MikeRyanDev just a question guys - does that mean you're not 6.0 ready yet?
I've tried the same above (before seeing the issue), and couldn't get it to work (got errors in the console about lift and exhaustMap and such).

Get we get some info about when will we be able to fully use 6.0 with ngrx?
Thanks ahead!

[scottleedavis]

Reopened in case this helps resolution. 😃

[brandonroberts]

Support for V6 already exists in the 6.0.0-beta.1 release of each package. Now that Angular 6.0.0 has gone final, we'll work on clean up any remaining issues. We'll likely cut another beta this week and then an RC or release depending on how that goes. if you want to upgrade today, you have to use the --next flag to check for beta releases

[gioragutt]

@brandonroberts understood. Just curious, is there anything we(the community) can PR to make your v6.0 advance? I'd very much like to contribute! I don't see any viable help wanted issues in the backlog.

Also, long as v6.0 is still in beta, it might be useful to point out that you can use the --next flag to allow working with the ngrx beta. This could save me some time, and I'm sure a whole lot of other people would like to work with it as well.

[gioragutt]

@brandonroberts I've tried updating with ng update --next --force @ngrx/store @ngrx/effects @ngrx/router-store @ngrx/entity @ngrx/store-devtools and it didn't work. Can I get a bit of help here?

[nickraphael]

@gioragutt I'm also struggling to update to the beta version.

[timdeschryver]

@gioragutt @nickraphael what problems are you encountering?
I haven't played around with the ng update command but I believe this doesn't update ngrx modules?
@gioragutt can you try npm i @ngrx/store@beta --save, this should install the beta version
@brandonroberts there is no next tag available - npm/@ngrx/store

[brandonroberts]

The --next flag looks at beta also if I'm not mistaken. I think using ng update requires a little bit more machinery on our end with migrations as noted here

[timdeschryver]

Yea you're right using the next flag will also look for beta tags when using ng update.
I was referring to npm, as in npm i @ngrx/store@next, my bad :sweat_smile: .

When I tried ng update --next it didn't update the ngrx libraries tho, or I must have done something wrong.

[gioragutt]

The command I used was npm install @ngrx/{store,effects,router-store,entity,store-devtools}@beta,
you might have to split it if you're using powershell or something.
Of course, npm install -D @ngrx/schematics.

I would also advice rm -rf ./node_modules before, and a full npm install after, the ngrx install.

[brandonroberts]

This has been resolved and work with ng update @ngrx/store --next --force until final release

[Riccardo-Andreatta]

I am getting the same error when I am upgrading from version 5 to version 6 but running ng update @angular/core --next --force is forcing update to the latest release: is there a workaround to update just to the version I want?