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

configman

v1.0.2

Published

Dead simple, lightweight configurations utility

Downloads

18

Readme

ConfigMan

npm version Build Status Coverage Status

Dead simple, lightweight configuration utility.

Installation

npm i configman --save

Example

Given the following directory, at the root of your project :

config/
    app.js
    db.js

app.js containing :

module.exports = {
    default: { // This default name can be changed at instantiation
        name: 'My awesome app'
        port: 3000
    },
    dev: { // Could be anything
        port: 8888
    }
}

And db.js containing :

module.exports = {
    default: {
        name: 'myawesomedb',
        port: 3306
    },
    dev: {
        user: 'johndoe',
        password: 'youwillneverfind'
    }
}

We can easily retrieve the app's port and name for the dev environment :

const ConfigMan = require('configman');

const Config = new ConfigMan({ env: 'dev' });

Config.get('app').name; // "My awesome app"
Config.get('app').port; // 8888

We can also request nested properties :

Config.get('db', 'user'); // "johndoe"

API documentation

constructor

new ConfigMan(options)
  • options {Object}
    • options.env {String} : Environment's name, must match the one in the files
    • [options.defaultConfigName = 'default'] {String} : The name of the property containing the configs default values
    • [options.root = 'config'] {String} : The directory in which to retrieve the config files

.get() any

Config.get(...paths)
  • paths {...String} : at least one path matching the file to read in root, optionally more to get nested properties

License

MIT