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
We currently only auto-load .env.local, but sometimes people like to use .env or .env.dev
.env.local
.env
.env.dev
I like the approach Next.js uses (docs)
Environment variables are looked up in the following places, in order, stopping once the variable is found.
process.env .env.$(NODE_ENV).local .env.local (Not checked when NODE_ENV is test.) .env.$(NODE_ENV) .env
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Problem / use case
We currently only auto-load
.env.local
, but sometimes people like to use.env
or.env.dev
Proposed solution
I like the approach Next.js uses (docs)
The text was updated successfully, but these errors were encountered: