npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

sconf

v1.0.0

Published

Simple Configuration for NodeJS Applications

Downloads

2,855

Readme

sconf

Simple Configuration for NodeJS Applications.

Why?

Because you need a well defined metodology to configure your applications both for development and deployment instead of reinventing the wheel for every application or hacking configuration values.

sconf follows the twelve-factor app guidelines.

You should define the application configuration by setting environment variables, but you can have convenient defaults for development, testing or some special development configurations.

All configuration items can be optionally prefixed, to avoid conflict with other applications that may be running in the same environment.

Installation

  npm install sconf

Examples:

  var $ = require('sconf');

  var config = {
    appPort: $('APP_PORT', 8080),
    redisUri: $('REDIS_PORT', 'tcp://example.com:6379'),
  }
  
  //  config.appPort contains 8080 or the value of env.APP_PORT
  
  /*
   config.redisUri:
      redisUri:
         { protocol: 'tcp:',
           slashes: true,
           auth: null,
           host: 'example.com:6379',
           port: '6379',
           hostname: 'example.com',
           hash: null,
           search: null,
           query: null,
           pathname: null,
           path: null,
           href: 'tcp://example.com:6379' }
   */

Using prefixes:

  // prefixed config
  var config = $.prefix('MY_APP')({
    appPort: $('PORT', 8080),
    redisUri: $('REDIS_URI', 'tcp://example.com:6379'),
  });
  
  // tries to read from environment variables MY_APP_PORT, MY_APP_REDIS_PORT

  // we can extend with an unprefixed config
  $.extend(config, $({mode: $('NODE_ENV')}))  

It also supports hierarchies:

 var config = $.prefix('MY_APP')({
   appPort: $('PORT', 8080),
   db: $.prefix('DB')({
     redisUri: $('REDIS_URI', 'tcp://example.com:6379');
   })
 })
 
// tries to read from environment variables MY_APP_PORT, MY_APP_DB_REDIS_PORT

Best Practices

Use a single config.js file for your application. Export the configuration and include that file in all the required server files.

  // config.js

  var $ = require('sconf');

  module.exports = {
    appPort: $('APP_PORT', 8080),
    redisUri: $('REDIS_PORT', 'tcp://example.com:6379'),
  }

API


  /**
    Creates a configuration entry. 
    
    @params envName Environment variable name
    @params defaultDevelopment optional default value in development mode
    @params defaultTest optional efault value in test mode
    @params defaultProduction optional default value in production mode
    
    @returns a value for this entry. Note, if the value is a valid URL, then
    it gets parsed and a URL object is returned instead.
  */
  $(envName, defaultDevelopment, defaultTest, defaultProduction)
  
  
  /**
    Adds a prefix to the environment variable names.
    
    @returns A sconf object with the given prefix appended to it.
  */
  $.prefix(prefix)
  
  
  /**
    Creates a configuration object based on the current prefix hierarchy.
    
    @param object
    @returns object with all the values populated.
  */
  $(object)
  

License

(The MIT License)

Copyright (c) 2013 Manuel Astudillo [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.