Discussion on "Managing multiple environments in NestJS"

Petros Kyriakou · 2021-08-17T18:59:48.861Z

So, recently I started working on a new startup and each time I do, I try to adopt a new technology be it language or framework . (this is not always recommended, in this case I have previous experience with NestJS) This time around I chose to adopt ...

Glad to see someone else had the same requirements in regards to managing environments and environment variables in NestJS. What we ended up using was nest-typed-config with its multiple loaders approach.

Basically we have 4 different config files:

base.yml (shared across all environments)
development.yml
test.yml
production.yml

We still leverage the env var loader with highest precedence to adhere to 12factor principles, while providing sane defaults to ease the setup and being developer friendly.

Interesting, thanks for sharing. From what i can understand the main selling point is type safety and flexibility on loaders?

Petros Kyriakou yes exactly, also doing validation/transformation through class-validator/class-transformer, but validation is also possible in the official NestJS config module through Joi like you outlined in your great article :)

Search Hashnode

Managing multiple environments in NestJS

Responses1