feat(create-waku): Add support for bun package manager #1229
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.
Closes: #1228
This change adds support for the
bun
package manager when runningcreate-waku
.From some local testing, it seemed like bun didn't set the
process.env.npm_config_user_agent
variable correctly (it does so when runningbun repl
though...), so instead I opted to fallback to checking if theBun
global was defined, which seems to be present when running the package viabun
.I was also considering checking against
process.argv0
which I think would be'bun'
, however I'm not 100% sure since I was running the cli manually viabun ./path/to/cli.js
vsbun create waku
.