-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
deno run --env
fails when no .env
file is present.
#21788
Comments
I think we did this on purpose when landing |
Nope. I feel like it shouldn't error. |
This was done on purpose. Should we instead print a gentle message saying that no Lines 723 to 727 in aadcd64
|
@iuioiua that makes sense. Any chance you could fix it and open a PR? |
bartlomieju
pushed a commit
that referenced
this issue
Jan 21, 2024
Uses similar format to when the latest version of std is implicitly being used. Closes #21788
bartlomieju
pushed a commit
to bartlomieju/deno
that referenced
this issue
Jan 22, 2024
Uses similar format to when the latest version of std is implicitly being used. Closes denoland#21788
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Fresh we recently switched from using std's
dotenv
module to Deno's--env
in denoland/fresh#2204 . But we noticed that passing--env
when no.env
file is present will exit the current process with an error message.With the
dotenv
module it didn't error when no.env
file was present.Steps to reproduce
foo.ts
(can be empty)deno run -A --env foo.ts
Version: Deno 1.39.1
The text was updated successfully, but these errors were encountered: