fix(docs): use pnpm add <pkg> instead of pnpm install <pkg>
#7563
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
sade-wusi
added
fixed-content
sade-wusi
approved these changes
Apr 11, 2025
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.
It should be
pnpm add <pkg>instead ofpnpm install <pkg>.pnpm installis used to install all dependencies for a project whilepnpm add <pkg>is used to install a package and any packages that it depends on.More info (official source):
pnpm install <pkg>does the same aspnpm add <pkg>today, but it might stop functioning that way in future versions since the official docs clarify the difference between the two. It might be thatpnpm install <pkg>was used in past versions, and the PNPM team didn't want to remove support for it right away after introducingpnpm add <pkg>.