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

appconfig

v0.0.1

Published

Load topic-specific json files from the `config` folder. Default settings are put in the root object, and environment-specific settings overwrite them based on `NODE_ENV`.

Downloads

52

Readme

appconfig

Load topic-specific json files from the config folder. Default settings are put in the root object, and environment-specific settings overwrite them based on NODE_ENV.

// config/redis.json

{
  "url": "redis://localhost:6379",

  "staging": {
    "url": "redis://user:[email protected]:8273/2"
  },

  "production": {
    "url": "redis://user:[email protected]:2983/1"
  }
}

Depending on the environment (default to "development"), the correct url will be fetched. Default values are put in the root config object like above.

// lib/redis.js

var config = require('appconfig').redis
var client = createClient(config.url)

That's it. As long as the config folder is in the root of your project, it will load properly.

caveats

  • You need to put the json in the config folder.

  • You can't use environment variables in the json.

There are hundreds of configuration packages for node. This is just one approach.

install

$ npm install aj0strow/appconfig --save

Put json in the config folder. Here's an example app structure, where config is available in every js file.

config/
  redis.json
  mongo.json
server/
  middleware/
    auth.js
  app.js
index.js

notes

This package searches for the main module (your app) and then finds the config folder. If you use appconfig in dependent packages, it will load configuration for the main application package.

You can provide appconfig as an option in dependent packages, in an effort to bring more convention over configuration to the node ecosystem.

var config = {}
try {
  config = require('appconfig')
} catch (error) {
  console.warn('no config folder')
}

License: MIT