-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider nested workspaces #379
Conversation
Previously only the root-level package.json workspaces field was considered; this accumulates packages for consideration even if they are listed in the workspaces list of another package.json file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this!
Thanks for your comments. I've exceeded my time budget for this work. You can finish this one off or discard it and leave it for another day. |
@dobesv I'd be happy to finish it for you. I'll push to this PR with some updates in the coming days. |
Thanks. Sorry I couldn't do more, I'm just swamped! |
While this could be considered a bug fix, I'll likely consider this a breaking change since it could result in dramatically different results when nested workspaces are present. |
Almost done but need to figure out why Windows CI is failing. |
Will release this in the coming days as soon as I can finish up #348 to be released with it. |
Previously only the root-level package.json workspaces field was considered; this accumulates packages for consideration even if they are listed in the workspaces list of another package.json file.
Fixes #377