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

node-pkg-configuration

v1.1.0

Published

Merge multiple configuration

Readme

configuration-node

Installation

npm install --save node-pkg-configuration

Usage

Config files:

Files in dir configuration/test

  
    test:
      hotelbook_params:
        url: https://hotelbook.com/xml_endpoint
        username: TESt_USERNAME
        password: PASSWORD
      logging: info
      databases:
        redis:
          master:
            username: R_USER
            password: R_PASS
            
    defaults:
      port: 8081
      logging: ignore
  

Files in dir configuration/defaults

  defaults:
    port: 8080
    hotelbook_params:
      area_mapping:
        KRK: Krakow
        MSK: Moscow
        CHB: Челябинск
    logging: debug

Import files:

Import with string params

   import Config from 'node-pkg-configuration';
   const config = new Config(`${__dirname}/configuration`, 'test');

Import with ENV params

   import Config from 'node-pkg-configuration';
   const config = new Config(process.env.CONFIG_PATH, process.env.STAGE);

CONFIG_PATH - should have full path to file. Exemple:

   CONFIG_PATH=Users/user/projects/my-project/configurations

Import without params

   import Config from 'node-pkg-configuration';
   const config = new Config();

With this config search in .env file variables CONFIG_PATH and STAGE if you don't have this variables in .env, set default path: /configuration and STAGE: production

Get config data:

  
  config.get() //return config object: 
  {
     hotelbook_params: {
       area_mapping: {
         KRK: 'Krakow',
         MSK: 'Moscow',
         CHB: 'Челябинск',
       },
       url: 'https://hotelbook.com/xml_endpoint',
       username: 'TESt_USERNAME',
       password: 'PASSWORD',
     },
     logging: 'ignore',
     databases: {
       redis: {
         master: {
          username: 'R_USER',
          password: 'R_PASS'
        }
      }
    },
    port: 8081,
  }
   
  config.get('port') //return: 
  8081;
  
  config.get('hotelbook_params') //return object: 
  hotelbook_params: {
    area_mapping: {
      KRK: 'Krakow',
      MSK: 'Moscow',
      CHB: 'Челябинск',
    },
    url: 'https://hotelbook.com/xml_endpoint',
    username: 'TESt_USERNAME',
    password: 'PASSWORD',
  }
  
  config.get('hotelbook_params.area_mapping.KRK') //return:
  'Krakow'

Contact us.

If you have any issues or questions, you are welcome to create an issue, or You can write an Email to [email protected] or [email protected]

License.

Released under the GNU GPL v3