Repository navigation
docs: clarify that --pack only works for npm packages - #275
Merged
Merged
Conversation
|
andrewbranch
approved these changes
Jun 25, 2026
This file contains hidden or 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
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.
This just tweaks the docs to be clear that other package managers generally won't work with
--pack. Right now, the docs are misleading to me: it just says that it'll runnpm pack, but doesn't make clear that that might not be what you want. As a person unfamiliar with the minutiae of package publishing, I wasn't sure whethernpm packwould be fine even in a pnpm/yarn repo... I've since found out it isn't.