What's the right way to holding configuration for multi-env?

hold env config like: ip, port, db, …

config/
dev.ts
prod.ts
test.ts

I have multi modules in project, should I create a shared module to hold env config?

[trainerbill]

Are there plans to build @kamilmysliwiec recommendation into the framework?

[kamilmysliwiec]

Additionally, you can do it in more nest-way, using custom providers. Example:

provide: ConfigService,
useClass: process.env.NODE_ENV === 'development' 
     ? DevelopmentConfigService 
     : ProductionConfigService

where ConfigService is an abstract class and both DevelopmentConfigService and ProductionConfigService extends ConfigService.