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

config4u

v0.1.1

Published

Environment, command line or JSON file with comments and single quotes

Downloads

3

Readme

config4u

Environment, command line or JSON file with comments and single quotes

Wanted multiple tiered config like config https://github.com/lorenwest/node-config will use NODE_ENV and ALCE parsing like getconfig with the added ability to define config.json directory or filename via command line --config or environment variable NODE_CONFIG_DIR

Install :hammer:

npm install config4u

Usage :bulb:

{
    postgres: {
        "url": '...', // database connection url
    }
}
config = new require('config4u')({ default: "values"})
dburl  = config.postgres.url
node myapp.js --config dir_or_filename // /somepath for /somepath.config.json or dev_config.json for /current_dir/dev_config.json

Assignment order

  • Passed in defaults
  • config.json file (in current application directory if not defined by --config)
  • config.json file (as defined by --config)
  • config.json file (optionally if defined by NODE_CONFIG_DIR)
  • NODE_ENV environment value as JSON string, ex: NODE_ENV = "{postgres: {url: '...'}}"

Contributions :muscle:

:smile: Feedback, problem reports, enhancement requests are welcome.

:up: Example code are better.

:cool: Pull requests are best.

License

MIT