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 🙏

© 2026 – Pkg Stats / Ryan Hefner

nodejsconfig

v0.2.2

Published

nodejs configuration management

Downloads

10

Readme

About

nodejsconfig is a Node.JS package that helps developers to write and maintain configurations for multiple environments. It has the following features:

  • No need to matian multiple configuration files;
  • Common configuration can be shared by multiple environments (*.username in the following example)
  • Using JSON to configure values;
  • Easy to use;

Install

npm install nodejsconfig

Use Case

It is common that developers use different database credentials in development, QA and production environment. We assume that for these three environments, database user names and passwords are:

  • Dev: admin/password_dev
  • QA: admin/password_qa
  • Prod: admin-prod/password-prod

With nodejsconfig, the developer needs to author a configuration file (e.g. config.properties) like below:

*.username = "admin";
prod.username= "admin-prod";

*.password = "password_dev";
qa.password = "password_qa";
prod.password = "password-prod";

# other configurations
*.port = 3306;
*.enabled = true;
*.price = 12.04;

The synax of the above file is very easy to understand. It reads:

by default, the username is 'admin';
if the environment is 'prod' then the username becomes 'admin-prod';

by default, the password is 'password_dev';
if the environment is 'qa' then the password is 'password_qa';
if the environment is 'prod' then the password is 'password-prod';

To read the configurations for a given environment:

var xnconfig = require('nodejsconfig');
var fs = require('fs');

var data = fs.readFileSync(__dirname+"/config.properties", "UTF8");

// assume we will be using environment "prod"
var config = xnconfig.parse("prod", data);

// the output will be admin-prod
console.log(config["username"]);

Advanced Features

nodejsconfig supports definition of arrays and maps in the configuration file:

*.credentials = {
    username: "admin",
    password:"password"
};

*.valid_users = ["admin", "foo", "bar"];

You can use "@" to refer other keys in the same configuration file:

*.username = "admin";
*.password = "password";

*.credentials = {
   #
   # @username to refer the 'username' defined in the same env
   # please note it is not @*.username.
   #
    username: @username, 
    password: @password
};

By default, you can use one '' as the prefix of your property names. If you want, you can tell nodejsconfiguration to use multiple ''s as the prefix. For example:

! PREFIX_NUM = 2;
# set the number of prefixes to 2

*.*.username = "admin";
*.*.password= "password";

*.special.username="admin_special";

By doing that, in environemnt prod.special, the username will be admin_special; otherwise, it is "admin".

Resources

  1. Antlr
  2. Antlr Javascript
  3. Java version of nodejsconfig (XNConfig)