It only works for one environment, what about if you have other environments ...

[Comment from a deleted post]

It only works for one environment, what about if you have other environments such .env.development .env.staging .env.production etc

Viraj Vimukthi Jayasinghe • Nov 30 '19

did you found the answer?

lamine • Nov 30 '19

take a look at dotenv-flow

Cully Larson • Jan 8 '20

I did something like this in next.config.js:

if(process.env.NODE_ENV === 'development') {
    require('dotenv').config({'path': path.join(__dirname, 'secrets/app.dev.env')})
}
else if(process.env.NODE_ENV === 'production') {
    require('dotenv').config({'path': path.join(__dirname, 'secrets/app.prod.env')})
}

Next.js sets process.env.NODE_ENV depending on the build environment. You could potentially also set another environment variable in your package.json like this:

    "dev": "CONFG_ENV=development next",
    "build": "CONFG_ENV=production next build",
    "start": "CONFG_ENV=production next start",

Then in your next.config.js you'd refernece CONFIG_ENV instead of NODE_ENV.

Charlie Jonas • Jan 27 '20

hopefully you weren't following the solution above and passing your application secrets into DefinePlugin...

Cully Larson • Jan 27 '20

Haha, there aren't actually any secrets in that folder 😁 I just always have a folder with that name that I gitignore and put things I don't want in the repo in there (config, actual secrets, etc). Totally slipped my mind it was named that here.