-
Notifications
You must be signed in to change notification settings - Fork 281
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
Bun runtime fails if there's an .env
file in the working directory
#130
Comments
FYI: @terracatta |
byroot
added a commit
that referenced
this issue
Sep 16, 2023
byroot
added a commit
that referenced
this issue
Sep 16, 2023
byroot
added a commit
that referenced
this issue
Sep 16, 2023
Fixed in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
When there's an
.env
in the working directory of Bun, the Bun runtime crashes with a JSON parse error.I believe the reason for the crash is because Bun outputs
[0.32ms] ".env"
toSTDERR
when it loads the.env
-file, and the bun runner (or external runtime?) combinesSTDERR
withSTDOUT
into a single output value, which is then parsed withJSON.parse
.It seems the external runtime merges
STDERR
on purpose:execjs/lib/execjs/external_runtime.rb
Line 210 in 6c1c228
Reproduction steps
This is reproducible on master.
Result:
The text was updated successfully, but these errors were encountered: