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

dh-config

v0.3.9

Published

Node module that makes it easier to setup and load deployment environment settings.

Downloads

23

Readme

dh-config

Node module that makes it easier to setup and load deployment environment settings.

Getting Started

dh-conf uses json files to store your settings. You need to create a directory within your project and create separate config files for each of your deployment environments.

Example Directory Structure:

MyApp
  - config
    - json
      - all.json
      - development.json
      - local.json
      - test.json
      - production.json
  - routes
  - utilities
  - services
  - models
  

Usage

1) Require the module when needed and pass in the file path to the directory where your json config files are stored:

let dhConfig = require('dh-config')(__dirname + '/../config/json', logger);

(Note) passing in the file path only has to be performed on the first require to dh-config. All subsequent requires can simply be invoked with:

let dhConfig = require('dh-config')();

(Note) you may pass in a reference to a logger if you have one. It assumes your logger has a .info, .warn, and .error function on it.

2) Load a config file by passing in the name of the config file without the .json:

dhConfig.loadConfig('all');

3) You can also automatically load a config file that matches your NODE_ENV name.

(Note) you can either specify your0 environment using:

NODE_ENV=[environment name] 
  

or by simply specifying the name on the command line:

node server.js [environment name]

To load the config based on the environment name, perform the following call while passing in a default config name to use in case the environment name was not specified:

dhConfig.loadEnvironmentConfig('local');
  

4) You can now access your settings by calling the following method:

dhConfig.get(KEY);
  

You may specify multiple keys if you are traversing through your settings objects. For example, if you had the following json file:

{
  "name": "test",
  "serverSettings" : {
      "port" : 3000
  }
}

To access the server port setting by calling:

dhConfig.get('serverSettings:port');
  

Or if you don't like the : separator you can set the delimiter of your choice:

dhConfig.setDelimiter('.');

Now you will be able to use the dot notation to access nested properties:

dhConfig.get('serverSettings.port');

5) You can load a config file using a file path:

dhConfig.loadConfigWithPath(__dirname + '/config/json/local.json');