Does NestJS ConfigModule Load .env in Production by Default?
Background In a typical NestJS project, ConfigModule.forRoot({isGlobal:true}) is used to centralise configuration. The module’s default behaviour is to read .env files only when NODE_ENV is not set to production . Consequently, a local dev build that relies on a .env file will work, while a production deployment that omits the file and expects platform‑suppl
nestjs