Environment aware config reader that follows our conventions at &yet.

#getconfig - config fetcher for node.js

Managing configs for different environments is kind of a pain.

In short I wanted it to:

  • Be simple to understand and use
  • Use NODE_ENV environment variable to grab appropriate config
  • Let me just go var config = require('getconfig') from anywhere in the app and have it Just Work™
  • Let me write configs that are structured like JSON but allow:
    • comments
    • single quotes
    • trailing commas
  1. npm install getconfig
  2. Create a dev_config.json file in the same folder as the main entry point (usually project root)
  3. Just require getconfig like so from anywhere in your project:
var config = require('getconfig');
  1. That's it!

Again, getconfig looks for a config file in the same folder as the main entry point of your app. In most cases, that's the root of your project.

Just name it so that it matches the following pattern: {{ environment name }}_config.json.

If NODE_ENV isn't set it defaults to dev.

You can name your environments whatever you want, but we color these nicely:

  • dev - dev_config.json
  • test - test_config.json
  • production - production_config.json

getconfig uses ALCE to parse JSON files, which means you can use comments, single quotes, and unquoted keys, woohoo! But of course it works just fine on regular JSON too. It just gives you the option.

In certain circumstances, when your app isn't run directly (e.g. test runners) getconfig may not be able to lookup your config file properly. In this case, you can set a GETCONFIG_ROOT environment variable to the directory where your configs are held.

You can also tell getconfig whether you want it to log out it's environment info (as it does by default) and whether or not to use colors in output. By adding the following to your {{some name}}_config.json file:

    "getconfig": {
        "colors": false, //turns off colors
    "getconfig": {
        "silent": true, //turns off all output

getconfig will always fill in the getconfig.env value in your resulting config object with the current environment name so you can programatically determine the environment if you'd like.

  • 1.0.0
    • Bumping major to get out of 0.x.x range per semver conventions.
    • dev enviroments now look for related config files. So if you've set your $NODE_ENV to development and it will still find a file called dev_config.json.
  • 0.3.0 - Switching from JSON.parse to ALCE to allow single quotes and comments. Better readme.


if you dig it follow @HenrikJoreteg on twitter.