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

plus.config

v1.0.10

Published

This config based on `nconf` and `config` packages and loads configuration from folder. It has 2 parameters `dir` and `env`.

Downloads

88

Readme

plus.config - configuration with environment

This config based on nconf and config packages and loads configuration from folder. It has 2 parameters dir and env.

Loading environment

Dir structure

|-- config.json
|-- config_dev.json
|-- config_test.json
|-- config_prod.json
`-- parameters.json

    var Config = require('plus.config');

    var config = new Config({
        dir: __dirname,
        env: process.env.NODE_ENV || 'dev'
    });

    config.get('var-name')
    config.get('deep.to.var-name')

This code loads config.json overrides variables with config_dev.json and overrides variables parameters.json. It works recursively.

It loads:

  • config.json // common settings
  • config_dev.json // environment settings
  • parameters.json // custom settings for local environment

Using

NODE_ENV=test node app.js

if you use test environment it will loads files in this order:

  • config.json // common settings
  • config_test.json // environment settings
  • parameters.json // custom settings for local environment

Config support

Now plus.config supports files in this format to this based on config package https://www.npmjs.com/package/config

default.EXT
default-{instance}.EXT
{deployment}.EXT
{deployment}-{instance}.EXT
{short_hostname}.EXT
{short_hostname}-{instance}.EXT
{short_hostname}-{deployment}.EXT
{short_hostname}-{deployment}-{instance}.EXT
{full_hostname}.EXT
{full_hostname}-{instance}.EXT
{full_hostname}-{deployment}.EXT
{full_hostname}-{deployment}-{instance}.EXT
local.EXT
local-{instance}.EXT
local-{deployment}.EXT
local-{deployment}-{instance}.EXT