We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Please describe.
@oclif/core should natively support .env files using process.loadEnvFile
Describe the solution you'd like
Call process.loadEnvFile at the beginning of run using path set in settings
run
settings
The call should be gated by a check for the node version to avoid any runtime errors.
The text was updated successfully, but these errors were encountered:
This issue has been linked to a new work item: W-15694504
Sorry, something went wrong.
Is there any workaround for supporting .env files in oclif?
oclif
You can you use dotenv in CLI's bin/run.js to load a .env file
@mdonnalley I see! I've already done this actually. 😄 But how can I make that work for the bin/run.cmd bin file for Windows?
bin/run.cmd
bin/run.cmd just runs bin/run.js so whatever you do in there should also work for windows
bin/run.js
No branches or pull requests
Is your feature request related to a problem? Please describe.
@oclif/core should natively support .env files using process.loadEnvFile
Describe the solution you'd like
Call process.loadEnvFile at the beginning of
run
using path set insettings
The call should be gated by a check for the node version to avoid any runtime errors.
The text was updated successfully, but these errors were encountered: