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

join-config

v1.0.1

Published

Function for extending config (should be node module) from application parameters and environments variables

Downloads

3

Readme

JOIN-CONFIG

Usually we have config.js file like this:

module.exports = {
    port: 3000,
    mongo: 'mongodb://localhost:27017/db'
};

This module extends config module with Environment Variables and Application Variables. Application Variables should have format property=value, for Environment Variables only properties used in initial config.js will be used because otherwise config will be clogged with useless variables from environment. If you use objects in Applications Variables they should be valid JSON. And do not forget to escape double quotes with backslash if you specify them in IDEs like WebStorm.

Examples:

node app.js mongo=mongodb://<host>/<db> watch=true interval=3
PORT=4000 USE_MONGO=true node app.js server='{"host":<host>,"port":1234}'