Add support for PNPM for installation commands #1285
Merged
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
Kocal
force-pushed
the
feat/pnpm-support
branch
from
8fa4471 to
9a03029
Compare
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.
Close #1279
Now, if you have a
pnpm-lock.yamlfile in your project, then the installation commands (displayed when you try to enable a feature and dependencies are missing) adapt topnpm.I've also simplified the detection/output logic, and removed
yarnas default command if no lock files are found.Yarn was recommended years ago, but that's not the case anymore. I believe
npmis good enough by default, and it's aswell the default package manager shipped with Node.js.