Eager loading of dotenv/.env about config

[jmcdo29]

Maybe we could just enhance the documentation to include dotenv?

I think this would be the better approach. And explain the use case as to when you'd want to call dotenv directly vs letting the ConfigModule take care of it

[jmcdo29]

What's the benefit of this over just dotenv.config()? I see you say "calling dotenv...leads to confusion on which configuration library to use", how would a second way to use the ConfigModule change that?

[PhearZero]

What's the benefit of this over just dotenv.config()? I see you say "calling dotenv...leads to confusion on which configuration library to use", how would a second way to use the ConfigModule change that?

It's not critical at all, just was confusing in the documentation. I found a few similar responses on StackOverflow with a similar issue. Maybe we could just enhance the documentation to include dotenv?

This does include validation and keeps things "in nest". The motivation is I received feedback to use the ConfigModule instead of dotenv, I think the assumption is that it is evaluated earlier than it actually is

[PhearZero]

Will update the docs! Thanks!