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

modreal-config

v0.0.3

Published

This is an opinionated simple configuration package. It assumes:

Downloads

8

Readme

modreal-config

This is an opinionated simple configuration package. It assumes:

  • configuraiton is a config folder with json files
  • the name of the json file is the name of the configuration
  • NODE_ENV is used for the app environment
  • test defaults to development, staging defaults to production
  • if no environment is specified, it is for all environments

How To Use

Add to your package as a dependency:

"dependencies": {
  "modreal-config": "modreal/config"
}

Install it:

$ npm install

Require it:

// javascript
var config = require("modreal-config");
# coffeescript
config = require 'modreal-config'

Access your configuraiton:

console.log(config.facebook)

See the next section for where to put your config json.

Config Folder Location

The config folder must be in the same directory or a parent directory of your main script file. Here are some examples of working folder setups:

+ package.json
- config
+ main.js
+ package.json
- config
- lib
  + main.js
+ package.json
- lib
  - config
  + main.js

Example JSON Files

mongo.json

{
  "production": "mongodb://alweof8a:[email protected]:1472/app_production",
  "staging": "mongodb://alweof8a:[email protected]:1472/app_staging",
  "development": "mongodb://localhost:27017/app_development",
  "test": "mongodb://localhost:27017/app_test"
}

Would then be available at:

console.log(process.env.NODE_ENV)
// development

config = require('modreal-config')
console.log(config.mongo)
// mongodb://localhost:27017/app_development

License

MIT


AJ Ostrow, November 2013