nconf.file merges don't work correctly about nconf HOT 6 CLOSED

I remember being burned by this as well. This scenario is not well documented, and perhaps an update should be made since I am not the only one who expected the library to work the way your sample is written.

Anyway, the way things currently stand...

You can only use each of the convenience (argv, env, file, defaults, overrides) methods once because each uses it's name as the key for the config store. If you want to use multiple files, you need to add them like this:

var conf = require('nconf');
conf.add('env-file', {type: 'file', file: path.join(path.resolve(__dirname, '../config'), (conf.get('NODE_ENV') || 'development') + '.json')});
conf.add('default-file', {type: 'file', file: path.resolve(__dirname, '../config/default.json')});

The important part is giving the config store a unique key, which is the first argument passed to add.

I'm surprised this issue sat for a month without a response. What's up, @flatiron ? @indexzero ? @mmalecki ? Is this lib being maintained?

from nconf.

@jstewmon Yes. It is. Unfortunately life can't be all open-source maintenance all the time =D

from nconf.

@jstewmon A pull-request to fix this issue would make you a hero in my book.

from nconf.

Fwiw, I solved this problem by deploying my app with npm and using npm's
built-in config framework.

from nconf.

@indexzero Watch out - that commit has that showHelp change in it too. Did you ever put that elsewhere? I'd like to align my master with flatiron, but I'm using that feature in a project.

from nconf.

Fixed

from nconf.