feat(build-tools): Support pnpm-workspace.yaml as workspace source #12252
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tylerbutler
changed the title
sonalivdeshpande
approved these changes
Oct 5, 2022
curtisman
approved these changes
Oct 5, 2022
|
This commit is queued for merging with the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fluid-build loads workspaces from lerna.json or package.json. This change adds support for pnpm's
pnpm-workspace.yaml. Versions will still be loaded from lerna.json, but the workspace definition will be loaded from pnpm-workspace.yaml if it's present.This is a quality of life fix for folks who are experimenting with pnpm in parts of the repo.