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

configgit

v1.0.2

Published

The easiest way to wrangle your env-specific configuration in node

Downloads

1

Readme

configgit

A wrapper for grabbing env vars from either process.env or a config file depending on the NODE_ENV.

Heavily (totally) influenced and inspired by a pattern that @tautologistics implemented at Moveline.

usage

config/{env}.json file structure

super-config expects a config/{env}.json convention, something like the following:

+--app
+--package.json
+--config
|  +--development.json
|  +--testing.json
|  +--production.json

Where development.json looks like:

//development.json
{
  "PORT": "3000",
  "JEDI_NAME": "Dinkus"
}

Set your NODE_ENV (configgit defaults to 'development'), and....

var Config = require('configgit')()

console.log(Config.get("JEDI_NAME")); // Dinkus

configgit expects a JSON file to exist at '/config/' + process.env.NODE_ENV.toLowerCase(). If one does not, you will see a message logged to the console telling you just that.

###process.env[key] overwrites config/{env}[key]

Any keys added to process.env will overwrite any matching keys in the config file.

Prefix the above example with a JEDI_NAME="Dorku", and run:

var Config = require('configgit')()

console.log(Config.get("JEDI_NAME")); // Dorku