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.
Description (What)
This PR adds support for pnpm workspaces. This was accomplished by using get-packages to get the list of pnpm workspace packages.
Note that
get-packages
searches the directory hierarchy for the closestpnpm-workspace.yaml
file, starting from the current working directory, so the behavior is a little different for pnpm than it is for npm/yarn. I would argue that being able to runsyncpack
from anywhere within a monorepo is actually a nice feature.Justification (Why)
pnpm is the "other" package manager which is already in heavy use by organizations like Microsoft and is growing in popularity. Many who use it say it has best-in-class support for monorepos. Thus it seemed natural to add pnpm support to syncpack.
How Can This Be Tested?