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

configdir-loader

v0.0.3

Published

Loads environment-specific configuration files into a config object.

Downloads

7

Readme

#configdir-loader build status

configdir-loader loads environment-specific configuration files from one or more directories into a config object.

Config files are loaded using Node's standard require() function, so they can either be JSON files, or JS files that export arbitrary objects.
Config files can also be suffixed with an optional environment, and the loader will only parse files with the active suffix.
For properties common to all environments, you can create a -base file, and the loader will recursively merge the environment-specific file into the base file.

You can also specify multiple directories to load config from, and the configuration from each directory will also be deeply merged (properties from later directories override earlier directories).

Sample directory structure:

  • core-config/
  • domains.json
  • featureSwitches.json
  • website-config/
  • sql-dev.json
  • sql-prod.json
  • featureSwitches-base.json
  • featureSwitches-prod.json
var config = require('configdir-loader').load('prod', [__dirname + '/core-config', __dirname + '/website-config']);

This will return an object with the following merged files:

{
	domains: [core/domains],
	featureSwitches: [core/featureSwitches, website/featureSwitches-base, website/featureSwitches-prod],
	sql: [website/sql-prod]
}

The loader is completely synchronous.