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

config-default-cjson

v1.0.2

Published

Loads a cjson file as config

Downloads

2

Readme

config-default-cjson

Loads a cjson formatted config file.

This library assumes your project uses two files for configuration:

  1. config-default.json
  2. config.json

The config-default.json file should contain all configuration parameters used by your program however you should leave sensitive information empty (empty string or 0 or null or an empty array - whatever makes sense).

The config.json file will override values from config-default.json. This allows you to keep sensitive information such as developer keys, authentication tokens and passwords separate from the config-default.json.

With this setup you can safely commit the config-default.json file to your code repository with the knowledge that it does not contain any sensitive information. Since cjson allows you to insert comments in your json file this means you can treat the config-default.json file as both the default settings and documentation of your software's configuration.

Never commit your config.json file into your code repository. The main purpose of separating it from config-default.json is so that custom configurations don't get committed by accident. If you are using git add it to your .gitignore!

Example usage:

const config = require('config-default-cjson');