nconf.overrides won't merge as expected

[gusverdywid]

Calling nconf.overrides the second time will replace every options set the first time.

nconf.overrides({
  modules1: {prop1: 'abc', prop2: 'def'}
});

// The following will replace every object in nconf.overrides specified before
nconf.overrides({
  moduleA: {newProp: 'foo'}
});

Am I doing it right? Is it the intended behavior of nconf.overrides?

[indexzero]

Yes. Why not merge these two objects up front before calling .overrides() a single time?

[gusverdywid]

But sometimes the configuration may come from different modules. Is there any other way to override configurations in different modules or files and merge them together without retrieving the configuration first, merging them and later calling .overrides()?

[indexzero]

Just use a .set in those multiple modules.

[AndersDJohnson]

@indexzero What if we want to provide overrides at the top-level of the object from multiple places? set seems to require a key. Could iterate over get but that's dirty.