Mark Stosberg

Closing as stale-- no interest in 5 years.

@lorenwest, perhaps this is best solved with a companion module, similar to what [`config-local`](https://www.npmjs.com/package/config-local) has done. This approach allows the main `node-config` project to still focus on and promote loading...

So the way I would see this playing out is for a custom project, you would continue to use `node-config` using the current behavior. If you publishing a module on...

@iMoses The new proposal needs to address how it would work in a "sub-module" that has several modules of it's own. One of the conveniences of `config` is that you...

@iMoses I'm in favor. I think it's OK if NPM authors have to do a little more work. They are minority of users.

Please add a failing test to the test suite which covers this case and submit your proposed change as a PR.

@flodaniel this bug may be of interest to you.

`node-config` strives to be immutable after the first call to `config.get()`. I believe this case happens because it's not a case of mutating an existing property but adding a new...

What about adding it to `makeImmutable`? https://github.com/lorenwest/node-config/blob/master/lib/config.js#L530 On Wed, Feb 21, 2018 at 9:10 AM Rémi Bèges wrote: > Thanks for clearing that up ! > > Well I see...

AWS just announced environment variables for AWS Lambda. It sounds like they are immutable. That is, if you wanted to support multiple configurations, you would have multiple versions of your...