Angular-cli: ng update not accepting more than one package

Created on 20 Oct 2018  路  7Comments  路  Source: angular/angular-cli

Bug Report or Feature Request (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)

- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [X] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions


node: 8.12.0
npm: 6.4.1

Angular CLI: 6.2.4
Node: 8.12.0
OS: win32 x64
Angular: 6.1.9
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router, service-worker

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.8.4
@angular-devkit/build-angular     0.8.4
@angular-devkit/build-optimizer   0.8.4
@angular-devkit/build-webpack     0.8.4
@angular-devkit/core              0.8.4
@angular-devkit/schematics        0.8.4
@angular/cdk                      6.4.7
@angular/cli                      6.2.4
@angular/fire                     5.0.2
@angular/pwa                      0.8.4
@ngtools/webpack                  6.2.4
@schematics/angular               0.8.4
@schematics/update                0.8.4
rxjs                              6.3.3
typescript                        2.9.2
webpack                           4.20.2

Repro steps


run ng update @angular/cli @angular/core

The log given by the failure


--from requires that only a single package be passed.

Desired functionality

Mention any other details that might be useful


I tried upgrading my global @angular/cli to @latest and got the same message. I also tried running npx with the same command to make sure I was using the local package, same message.

running ng update @angular/cli gave me Found a modern configuration file. Nothing to be done. and did not upgrade the cli to v7.

running ng update @angular/core did upgrade the core to v7 along with associated dependencies, but again, _not_ the cli.

so ng -v now gives me:

Angular CLI: 6.2.4
Node: 8.12.0
OS: win32 x64
Angular: 7.0.0
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router, service-worker

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.8.4
@angular-devkit/build-angular     0.8.4
@angular-devkit/build-optimizer   0.8.4
@angular-devkit/build-webpack     0.8.4
@angular-devkit/core              0.8.4
@angular-devkit/schematics        0.8.4
@angular/cdk                      6.4.7
@angular/cli                      6.2.4
@angular/fire                     5.0.2
@angular/pwa                      0.8.4
@ngtools/webpack                  6.2.4
@schematics/angular               0.8.4
@schematics/update                0.8.4
rxjs                              6.3.3
typescript                        3.1.3
webpack                           4.20.2

Finally, running npm outdated after this also reveals not all packages were updated:

Package                        Current  Wanted  Latest  Location
@angular-devkit/build-angular    0.8.4   0.8.6  0.10.2  coop-registration
@angular/cdk                     6.4.7   6.4.7   7.0.0  coop-registration
@angular/cli                     6.2.4   6.2.6   7.0.2  coop-registration
@angular/pwa                     0.8.4   0.8.6  0.10.2  coop-registration
karma                            2.0.5   2.0.5   3.0.0  coop-registration
schematicupdate medium regression

Most helpful comment

Try this:
ng update --all --force
That fixed the problem for me...

All 7 comments

Try this:
ng update --all --force
That fixed the problem for me...

You need another param like this: ng update @angular/core @angular/cli --next

Could this be a node issue? I just successfully ran the ng update command on a machine with node 10, but a third running node 8 also would gave me the same error message.

ng update --all
has error. delete node_modules then update

I think this is obsolete - we no longer support node 8 in latest CLI. If you can still reproduce this, please open a new issue referencing this one - thanks!

This is still an issue coming from @angular/[email protected]. I'm getting it with both node 11.12.0 and 10.16.0. After updating it to 8.0.2 I'm no longer seeing the error.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_This action has been performed automatically by a bot._

Was this page helpful?
0 / 5 - 0 ratings