Improve package manager detection for Bun 1.2 compatibility #165
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.
I'm using bun and install packages with
bun install --yarn
and its generate a yarn.lock file, same time new version of bun 1.2 generatesbun.lock
file instead ofbun.lockb
.Some users may have bun with
yarn.lock
file or bun withbun.lock
My assets recompilation failed with:
Here is a proposal to handle this, idk what best way to do this. If this way looks ok I can fix test as well. Also we have
using_bun?
method atHelpers
module that dose not check forbun.lock
and return false if bun exists and yarn.lock presentbun.lockb
and newbun.lock
Bun lock filesyarn.lock