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

extending-config

v1.0.3

Published

configuration through demanding common config and updating it with environment-dependent part

Downloads

6

Readme

extending-config

Configuration through demanding common config and updating it with environment-dependent part

Installation

npm i extending-config --save

Usage

Require configurator like this: var configurator = require("extending-config");

And get config then using configurator. It accepts options like this:

basePath path to your config directory. Defaults to your cwd / 'config'

environment your current environment defaults to your NODE_ENV or 'development'

common base part of your config, defaults to 'common'. Use false if you don``t want to have common part of config.

Common config would be updated by environment config. Then get config like this:

var config = configurator();

Be careful not to use one config as base for two different environments in the same process run. They are not copied and my be mixed!

Tests

To test run: npm test

You also can look usage of module in tests/test.js.