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

etcjs

v1.1.3

Published

Simple stupid node.js configuration module

Downloads

9

Readme

etcjs

Build Status Coverage Status Dependency Status

Simple node.js configuration module

Installation via npm

$ npm install etcjs --save

Example

Even this is useless on its own, here is how to set up configuration for 'development' environment:

$ NODE_ENV=%ENV% npm start ../etc ../etc/default/default
# where %ENV% is the target environment.

Using etcjs as a module in your node app

Once started up, the module will look for the default configuration file by requiring the 'defaultFile'.

After loading the default configuration, it will load the environment specific file from the 'dir' directory.

For example, if NODE_ENV=development then it will require 'root/dir/of/config/files/development.js'.

Finally, the callback function is called once all done.

var etcjs = require('etcjs');
etcjs.load({dir: 'root/dir/of/config/files/', defaultFile: 'path/to/default/config/file'}, function () {
    console.info('configuration has been initialized');
});

if no configuration object is provided, etcjs will look for the default files inside the default location: * default global configuration file: ./etc/all.js * environment specific configuration file: ./etc/%env%.js, where env is the target environment. The callback can also be omitted in this case the module will do it job and returns.

var etcjs = require('etcjs');
etcjs.load(function () {
    console.info('configuration has been initialized');
});

methods

load

load the default and the local configuration and store it in the node environment.

get([key])

returns the environment variable by key. returns the node environment if no key is provided

set(key, value)

sets the environment variable of given key to value.

Running tests

$ npm test

People

Author: Mohamed Boughaba

Looking for more?

Check out argument parser minimist

or even nconf

License

MIT