Replies: 1 comment
-
|
This is a bug caused by converting the import into an absolute path instead of a package path Converting to an issue |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I always expect
bun .to use mypackage.json#exports.If this is not the desired behaviour of
bun ., what is the easiest way to runpackage.json#exports["."]frombuncli.Beta Was this translation helpful? Give feedback.
All reactions