Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign up'ng update' does not work with yarn workspaces #14841
Comments
|
Hi, thanks for opening this, however at the moment this is not supported, and hence I am going to mark it as a feature request. |
|
I'm also struggling with this one while trying to upgrade to Angular 9. Is it possible yet? |
|
I think there may have been some progress here in recent versions because running
However, the actual update command for a package doesn't work:
Seems like we're almost there. The problem is on this line: Notice how it says |
|
Possibly relevant: gatsbyjs/gatsby@3b5e41b Seems like a similar commit in gatsby for resolving issues with yarn workspaces. They replaced read-package-tree with their own implementation. |
|
Still relevant.
|
|
I opened a PR at #18610 to implement this. cc @alan-agius4 |
Command (mark with an
x)Is this a regression?
NoDescription
I am utilizing yarn workspaces -feature in my project. Problem is that I have to keep Angular & AngularCLI dependencies on root packages.json, otherwise 'ng update' command can't figure out the version I currently have. I'd rather keep root package.json clean and move Angular & CLI dependencies to project/package.json to keep things isolated.Looking at the code, update command resolves dependencies from root package, even when command is executed on package folder. Would it be possible to change behavior in a way that update would first check package dependencies and the fall back to root if nothing is found?
Root package.json:
'workspace-a/package.json':
Anything else relevant?