-
-
Notifications
You must be signed in to change notification settings - Fork 15
Resolve workspaces recursively for better Yarn 3 support #85
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
Conversation
| // If the error is not a file not found error, throw it | ||
| if (error.code !== 'ENOENT') { | ||
| console.error(`Failed to read changelog in "${projectRootDirectory}".`); | ||
| throw error; | ||
| } | ||
|
|
||
| return console.warn( | ||
| `Failed to read changelog in "${projectRootDirectory}".`, | ||
| ); |
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.
Since not all sub-workflow packages in snaps-skunkworks have a CHANGELOG.md, I changed this to ignore the package if the file doesn't exist.
mcmire
left a comment
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.
Seems useful! LGTM.
Related to MetaMask/snaps#489.
With Yarn 3 it's possible to have a package in a workspace be a workspace as well ("sub-workspace"). Right now we only resolve packages in the root workspace, and packages in sub-workspaces are simply ignored. This PR changes the
getMetadataForAllPackagesto recursively resolve workspace packages.This is tested in the
snaps-skunkworksrepo.