-
-
Notifications
You must be signed in to change notification settings - Fork 161
fix(resolve): rank the bun export condition above node for --platform bun #10283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| Rank the `bun` condition above `node` when resolving package `exports` and | ||
| `imports` under `--platform bun`. Bun resolves with `["bun", "node", …]`, so a | ||
| package that ships both entries — `@opentui/core` offers `{ bun: | ||
| ./index.bun.js, node: ./index.node.js, import: ./index.node.js }` — previously | ||
| compiled its node entry and ran a different backend than the bun binary the | ||
| program is meant to match. OpenCode's terminal interface died on exactly that: | ||
| the node entry's renderer backend is not the one its bun build loads. `bun` | ||
| stays below `perry`, so an explicit perry entry still wins, and the order is | ||
| unchanged for every other target. The three resolvers now read one shared | ||
| list so they cannot disagree. |
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win
Make the Bun platform state compilation-scoped.
run_with_parse_cachesetsBUN_PLATFORM, but no compilation lock or restoration exists. The resolver and dependency paths read it throughdefault_conditions, so overlapping compilations can resolve modules with another compilation's platform conditions. The regression test also leaves the flag enabled if an assertion panics before its final reset. Pass the condition set explicitly, or serialize the entire compilation with a shared lock and restore the previous value through an RAII guard. Use the same guard for the test.🤖 Prompt for AI Agents