How does it support multiple env files?

[zhaoyi0113]

I am looking through this instruction: https://docs.nestjs.com/techniques/configuration to setup env file for my nestjs application.

I see it supports creating multiple config files: envFilePath: ['.env.development.local', '.env.development'], but I wonder how it supports dynamically choose environment file based on NODE_ENV.

I have three env files: .env.dev, .dev.staging, .dev.prod. And I usually use NODE_ENV=dev env to set the current environment. How does nestjs/dev work with NODE_ENV. Can it pick one based on its value?

[kamilmysliwiec]

but I wonder how it supports dynamically choose environment file based on NODE_ENV.

For example:

envFilePath: `.env.${process.env.NODE_ENV}`

Please, use our Discord channel (support) for such questions. We are using GitHub to track bugs, feature requests, and potential improvements.

[kamalkech]

@kamilmysliwiec that s not working, still load .env prod even if we add commands in packages file to set NODE_ENV

[micalevisk]

@kamalkech this might help you https://docs.nestjs.com/techniques/configuration#custom-env-file-path

I'm using envFilePath with no worries.