Well maybe a little bit strange and basic question but..
As usual in my application I have some configurations parameters specific for current environment like dbs, paths, keys, logins etc.
There is an access to process.env object that may contain any number of string properties, so why not use it for storing all the config information and use it across the application?
I've seen people are using some custom config files or some modules like nconf (https://github.com/flatiron/nconf).
nconf seems to be very robust, but I don't really see where I may use its power, as I just need to be able init some shared parameters and use it in different app's modules.
So the question is init and store configuration parameters in process.env and use across all application code just in sake of simplicity?
You could just use global, adding a new variable into the global scope. Just be careful with it ;-)