Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Can't select project when doing ng update

See original GitHub issue

🐞 Bug report

Command (mark with an `x`)

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

Description

When running ng update --all --force is will only update the package.json in the root of the Angular project, but will skip your projects in the projects folder. There is no way to specify the project on the command line. Having a few larges libraries it’s convenient to update projects too.

Issue Analytics

State:
Created 4 years ago
Comments:13 (1 by maintainers)

Top GitHub Comments

1reaction

alan-agius4commented, Mar 28, 2020

Hi all,

Yeah, peerDependencies need to be updated manually one of the reason is that it’s up to the library author to decide the support strategy of their library.

Tried the same for angular 7 to 8 but library project is not updated.

What did you expect to see updated in the library when you updated from version 7 to 8?

Prior to version 9, ng update did update library projects as well.

1reaction

alan-agius4commented, May 20, 2019

Migrations run against all projects in a workspace. They will run on libraries and applications, if the migration schematic is designed to do so. For version 8 we don’t have any migration that effects a library.

However from the request above, I am assuming that the user (@farlock85) is using some sort of workspace concept maybe with yarn. Ie having multiple package.json in various projects. At the moment, this is not supported by the CLI and we only update dependencies in the root package.json.