Do not warn when "bun" is used in "engines" in package.json
#9214
Conversation
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
malonehedges
approved these changes
Oct 31, 2025
malonehedges
left a comment
malonehedges
left a comment
There was a problem hiding this comment.
approved, let's get this in. thanks for the PR @Jarred-Sumner
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently, when
"engines"of any package.json dependency includes"bun", yarn v1 prints the warning below:This PR adds
"bun"to the list of engines to ignore, so that yarn v1 doesn't print this warning. This will let npm packages that use the"engines"field specify they want to use the Bun runtime more easily.