Support using specific dotenv file according to environment

[fralonra]

Is your feature request related to a problem? Please describe.

Currently it seems that we can use only one dotenv file (.env, see load.js) in the project. But sometimes we need to have different dotenv in one project and can use them for different environment.

Describe the solution you'd like

Load dotenv file according to current environment.
eg. .env.dev or .env.development for development, and .env.prod or .env.production for production, and .env for default.

[danielroe]

@fralonra You can specify the .env file to load on the command line e.g. yarn nuxt --dotenv .env.staging - which should give you the flexibility you might want. This works for both env and runtimeConfig.

[nirazul]

Currently, this doesn't seem to work with Nuxt 3 (rc8)

[daviddomain]

No luck as well. Using nuxt/bridge-edge nuxi dev --dotenv .env.whatever does not load the correct environment variables.

[nidmidhalf]

@danielroe Any update on this? nuxt.config.ts is always picking the environment variables from .env instead of .env.development inspite of mentioning the --dotenv .env.development in package.json

[danielroe]

Feel free to create an issue with a reproduction 🙏