docs: improve explanation of --prod flag #500
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
|
|
|
@CakeWithDivinity is attempting to deploy a commit to the pnpm Team on Vercel. A member of the Team first needs to authorize it. |
zkochan
reviewed
Jan 17, 2024
zkochan
approved these changes
Jan 17, 2024
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.
The
--prodflag for thepnpm installcommand is not well displayed as a boolean value.It is unclear that one can use the flag like this
pnpm install --prod=falseto use a "development" install in a production environment. This has already happened to some people: pnpm/pnpm#6254This PR tries to explain the option a bit better, so its use-case is a bit more clear, and aims to make the docs page more consistent.
I took inspiration from how the
--frozen-lockfileoption works: https://pnpm.io/cli/install#--frozen-lockfile