What version of Bun is running?
0.5.8
What platform is your computer?
No response
What steps can reproduce the bug?
Bun Docs show that package.json exports can define these fields.

It is missing import and require, where the former breaks importing @astrojs/compiler as it defines this for it's exports:
"exports": {
".": {
"browser": "./browser/index.js",
"import": "./node/index.js",
"default": "./browser/index.js"
},
...
},
And bun picks up browser, and ignores import.
node docs here define import, require, and node-addons which bun ignores. I've never seen that last one but it seems to have some extra logic where the first two can just be treated as a higher priority than browser.
Reproduction:
import {transform} from '@astrojs/compiler';
transform("");
What is the expected behavior?
Loading the node version of the astro compiler.
What do you see instead?

Additional information
Workaround for astro compiler:
import { transform } from "./node_modules/@astrojs/compiler/node/index.js";
What version of Bun is running?
0.5.8
What platform is your computer?
No response
What steps can reproduce the bug?
Bun Docs show that package.json

exportscan define these fields.It is missing
importandrequire, where the former breaks importing@astrojs/compileras it defines this for it'sexports:And bun picks up
browser, and ignoresimport.node docs here define
import,require, andnode-addonswhich bun ignores. I've never seen that last one but it seems to have some extra logic where the first two can just be treated as a higher priority thanbrowser.Reproduction:
What is the expected behavior?
Loading the node version of the astro compiler.
What do you see instead?
Additional information
Workaround for astro compiler: