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

cf

v0.0.3

Published

Environment sensitive configuration file loader for node.js

Downloads

772

Readme

cf

Environment sensitive config loader for node.js, using xtend

Example usage:

Installation:

npm install cf

Create a directory where you intend to store your configuration files. Eg. 'config'. In that directory, make two files:

  • config/default.config.json
  • config/development.config.json

In your code:

var myConfig = require('cf')({
    root: __dirname + '/config'
});

Now your myConfig variable will be an object containing all the values of the default config file and the ones your development config file overrides.

Now you can also make a production config in config/production.config.json and when you start your app using NODE_ENV=production node myapp.js that file will be used instead.

Options

  • root: root directory of your config files. Required
  • suffix: what file suffix you want to use.. default is .config.json
  • defaultEnv: what environment name to use if none is defined.

note: not very well tested at this point.. WIP

License:

MIT