nconf with multiple files

app-output.txt

$ node app.js
My specific title
green
undefined

app.js

nconf = require('nconf');
nconf.add('global', {type: 'file', file: 'global.json'})
nconf.add('user', {type: 'file', file: 'user.json'})
nconf.load();
console.log(nconf.get('title'));
console.log(nconf.get('color'));
console.log(nconf.get('movie'));

global.json

{
  "title": "My generic title",
  "color": "red",
  "movie": "Kill Bill"
}

package.json

{
  "author": "Brian Link <cpsubrian@gmail.com>",
  "name": "nconf_example",
  "version": "0.0.1",
  "repository": {
    "url": ""
  },
  "main": "app.js",
  "engines": {
    "node": "~0.6.2"
  },
  "dependencies": {
    "nconf": "0.4.x"
  },
  "devDependencies": {}
}

user.json

{
  "title": "My specific title",
  "color": "green"
}

I'm banging my head against what seems to be very unintuitive behavior of nconf and stumbled across this. Was this designed to show how nconf doesn't handle multiple files, i.e. the 'global' settings are clobbered by the 'user' settings?

I believe if same key is present in multiple files then the value from the first file (in order they are defined) will be considered