Angular 11 has now been released and this library should look towards supporting it.
internalsystemerror
All 8 comments
100% agreed! It should work out of the box because we are Ivy compatible.
Have you had any issues or is the problem just regarding the npm dependency range?
PS. We plan to cut another release this week that has Angular 11 included in the npm dependency range.
markwhitfeld
on 16 Nov 2020
No issues noticed in 2 apps so far, 1 using ngxs more than the other. Although I had no issues upgrading from 9 to 10 either. Mainly just want to ensure that the tests in this repository are run against ng11 before putting these live. Thanks.
internalsystemerror
on 16 Nov 2020
I had the same, seems fine. I ended up having to do a 'npm outdated' and hand roll my updates. Nuked my node_modules and did a fresh 'npm install'.
cybercussion
on 16 Nov 2020
ng update @angular/core @angular/cli --force works fine for me updating to Angular 11 (aside from the compatibility warnings that would prevent it from running without --force). If you manually updated, review the angular changelog and the update migrations to determine if they apply to you. Source for angular update migrations here: https://github.com/angular/angular-cli/tree/master/packages/schematics/angular/migrations
bbarry
on 17 Nov 2020
Running ng update @angular/core @angular/cli without force:
Package "@ngxs/devtools-plugin" has an incompatible peer dependency to "@angular/core" (requires ">=6.1.0 <10.0.0" (extended), would install "11.0.0").
✖ Migration failed: Incompatible peer dependencies found.
Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together.
You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later.
See "/private/var/folders/vm/b6mkwp7s5c182c_2v7mzkfh00000gn/T/ng-ao4mmL/angular-errors.log" for further details.
miguelvictor
on 17 Nov 2020
@miggymigz sorry, I wanted to send a comment, but pressed the wrong button. Most likely only one workaround will work now: ng update @angular/core @angular/cli --force
splincode
on 17 Nov 2020
@splincode No worries. I just realized markwhitfeld already said that this week's release will include the updated dependencies. Sorry for that.
miguelvictor
on 17 Nov 2020
This is resolved with the release of v3.7.1
markwhitfeld
on 2 Dec 2020
Related issues
garthmason
·
5Comments
goodmite
·
5Comments
piernik
·
5Comments
abalad
·
5Comments
michael42
·
4Comments
Most helpful comment
100% agreed! It should work out of the box because we are Ivy compatible.
Have you had any issues or is the problem just regarding the npm dependency range?
PS. We plan to cut another release this week that has Angular 11 included in the npm dependency range.