feat: Automatically select the package manager to install release-it #4
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
|
Basic tests have been conducted on npm, pnpm, yarn, and bun, and they are running smoothly! |
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.
When using
npm init release-itto initialize release-it, I encountered the following error, which left me a bit confused. Clearly, it didn't fully succeed!Then I realized it was because my project uses pnpm as the package manager, so executing
npm install release-it --save-devfailed. To address this, I added a piece of logic to automatically detect the project's package manager and execute the corresponding installation command. It works well now!bun
pnpm
npm