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

mcms-node-config-loader

v0.0.4

Published

mcms node config loader.

Downloads

6

Readme

mcms-node-config-loader

Easily load config files for multiple environments

What does it do

This packages allows you to easily load the right config file depending on the environment you're working on

Install

npm install mcms-node-config-loader

Folder structure

The library expects a structure like so :

/configDir
        /devEnv
            configFile.json
        /anotherEnv
            configFile.json
configFile.json
anotherConfigFile.json

Every file under the configDir is loaded as production environment. If you create a subdirectory named after an environment you have defined before calling the module, it will overwrite the default config. For example, you have a mysql.json config under the configDir with your mySQL connection settings. If you create the same file with different settings under the configDir/development directory, when you're working on your dev machine theses settings will be loaded instead

Usage

check the examples folder for usage scenarios Initialize like so :

var path = require("path");
var environments = {
    'development' : ['ubuntu','mike-PC','mint-box'],
    'production' : 'myProductionBox'
};
var configLoader = require("../index").setEnv(environments);
var Config = configLoader.loadConfig(path.join(__dirname,'./config'));

That's it, under the Config object you can now access all your settings