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

param

v1.1.0

Published

param is a tiny module to read config parameters

Downloads

148

Readme

param

A tiny module to read config parameters for your node application. It's avaiable through npm:

npm install param

what?

Param exposes a single function that finds a config parameter

// example.js
var param = require('param');
var port = param('app.port');

console.log(port);

The above example tells param to find the parameter app.port. It does so by first looking at the command line arguments

node example.js --app.port 8080 # prints 8080

If present param will simply return that value. Otherwise param will look for a configuration file specified by --config [filename] or your NODE_ENV env var. If NODE_ENV=development it will look for a config file called config/development.json or config/development.js. It will start looking for the config file in . If it doesn't exist it will try in .. until it reaches /.

{
	"app": {
		"port": 8888
	},
	"certificate": "{./certificate.file}",
	"apikey": "{$API_KEY}"
}

{$API_KEY} reads API_KEY from the environment. Equivalent to process.env.API_KEY.

{./certificate.file} reads the file called certificate.file.

Running the example again with the above file saved as config/development.json

node example.js # prints 8888

Happy configuring!

License

MIT