feat(publish): add packageManager option #26
Merged
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.
In the recent Vite 5 beta release,
npm publish
was having trouble publishingvite
. We got:Running
pnpm publish
instead fixes it, and I'm not really sure why. It could be pnpm installing dependencies in a certain way that npm fails.Figured I add a new option instead of hardcoding it so we don't need a major bump, and also
npm publish
should work fine for our other packages, onlyvite
is hitting this problem strangely.