0

Im a little confused whether we should fill up or leave .env file empty as it is? Since during execution each environment file (.env.dev / .env.production) will append all my values into .env

So what I'm saying is, keeping .env empty and only append env values into each environment files.

.env -> keep it empty

.env.developemnt -> env specific values

.env.development.local -> store all kind of secrets

#.gitignore
.env.development.local

Or, is there a "proper" way to handle this instead?

Tommy Leong
  • 2,509
  • 6
  • 30
  • 54

1 Answers1

0

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

For example, if NODE_ENV is development and you define a variable in both .env.development.local and .env, the value in .env.development.local will be used.

In other words, the first .env to match the order will be loaded.

You can delete .env if you don't use it.

https://nextjs.org/docs/basic-features/environment-variables#environment-variable-load-order

PYTHON DEVELOPER999
  • 301
  • 2
  • 12