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

beat-conf

v0.0.2

Published

Simple configuration utility for Beat dependency injection

Downloads

5

Readme

beat-conf Build Status Code Climate

Simple configuration utility for Beat dependency injection

NPM

This module provide a conf object to be injected in beat instances.

How to use

Set your configurations normally in the native package.json (abbreviated here for simplicity)

{
  ...
  "config": {
    "serverPort": "3000",
    "mongo": "mongodb://localhost:27017/production_db",
    "publicPath": "/public"
  }
}

Install this module with NPM:

npm install --save beat-conf

Declare it as a dependency of your Beat module and inject conf object where you need it

var Beat = require('beat');
var server = module.exports = new Beat('server', [
  'beat-conf',
  'http'
]);

server.run(function(http, conf){
  http.createServer().listen(conf.serverPort);
});

Config environments

This utility is very simply crafted, but it's important to understand its behavior.

The config object in package.json can contain several sub-objects whose key refers to current env.

The default one will be used, and will be overlapped by the configs according to current process.env.NODE_ENV, if exists.

As in this example:

{
  ...
  "config": {
    "default": {
      "serverPort": "3000",
      "mongo": "mongodb://localhost:27017/production_db",
      "publicPath": "/public"
    },
    "test": {
      "mongo": "mongodb://localhost:27017/test_db"
    }
  }
}

mongo property will normally be mongodb://localhost:27017/production_db;

while with process.env.NODE_ENV setted as 'test', it will be setted to mongodb://localhost:27017/test_db.

The other configurations continue the same.

githalytics.com alpha