313b552026
* Enable .env support by default Given we've had tons of reports from various people that expected .env support to work even though they had dotenv installed already I think it's fine to enable it as a default: Fixes #12728 * Remove old test * Fix duplicate env loading * Update docs Co-authored-by: JJ Kasper <jj@jjsweb.site>
20 lines
924 B
Markdown
20 lines
924 B
Markdown
# Env Loading Disabled
|
|
|
|
#### Why This Error Occurred
|
|
|
|
In your project you have `dotenv` listed as a `dependency` or a `devDependency` which opts-out of Next.js' automatic loading to prevent creating a conflict with any existing `dotenv` behavior in your project.
|
|
|
|
This is also disabled if a `package.json` isn't able to found in your project somehow.
|
|
|
|
#### Possible Ways to Fix It
|
|
|
|
Update to the latest version of Next.js (>= v9.4.1) where this support is enabled regardless of `dotenv` being installed.
|
|
|
|
Remove `dotenv` from your `devDependencies` or `dependencies` and allow Next.js to load your `dotenv` files for you.
|
|
|
|
### Useful Links
|
|
|
|
- [dotenv](https://npmjs.com/package/dotenv)
|
|
- [dotenv-expand](https://npmjs.com/package/dotenv-expand)
|
|
- [Environment Variables](https://en.wikipedia.org/wiki/Environment_variable)
|
|
- [Next.js Environment Variables Docs](https://nextjs.org/docs/basic-features/environment-variables)
|