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

shallow-settings

v0.1.0

Published

Shallow inheritance-based settings for your application

Downloads

4

Readme

shallow-settings Build status

Shallow inheritance-based settings for your application

This was based off of mgutz/node-settings but implements a shallow clone over a deep clone to make output more predictable. Additionally, it features lazy loading for instantiaion inside of your configuration itself.

Getting Started

Install the module with: npm install shallow-settings

// Define our settings
var Settings = require('shallow-settings');
var settings = new Settings({
  common: {
    hello: 'world',
    nested: {
      key: 'value'
    }
  },
  development: {
    nested: {
      hai: 'there'
    }
  }
});

// Retrieve the settings for our environment
settings.getSettings({env: 'development'});
/*
{
  ENV: 'development',
  hello: 'world',
  nested: {
    hai: 'there'
  }
}
*/

Documentation

shallow-settings defines Settings as its module.exports.

new Settings(configs)

Constructor for creating a new settings factory

  • configs Object - Container for different sets of settings
    • configs.common Object - Required base settings set that all other settings will inherit from
    • configs.* Object - Any other settings you would like to set

settings.getSettings(options)

Extract and instantiate a set of settings based off given environment. We take the common environment and extend over it with the passed in environment's settings.

After that, we run the lazy load functions to run anything that needs to be instantiated.

For sanitation of original data, we deep clone the settings we will return.

  • options Object - Container for parameters
    • env String - Environment to load settings from

Settings.lazy(fn)

Mark a function to be lazy loaded. The return function must be a top level function for a config.

  • fn Function - Function to mark for lazy loading

Examples

Below is an example of using lazy loading:

// Define our settings
var redis = require('redis');
var Settings = require('shallow-settings');
var settings = new Settings({
  common: {
    redis: Settings.lazy(function () {
      return redis.createClient(9001);
    })
  },
  production: {
    redis: Settings.lazy(function () {
      return redis.createClient(9002);
    })
  }
});

// Currently, no redis instances have been loaded

// Load up our production redis (and make no calls to port `9001`)
settings.getSettings({env: 'production'});
/*
{
  ENV: 'production',
  redis: {
    stream: {
      _handle: {
        writeQueueSize: 0,
        ...
      }
    }
  }
}
*/

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint via grunt and test via npm test.

License

Copyright (c) 2014 Uber

Licensed under the MIT license.