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

cfgapp

v1.0.5

Published

Application config management library

Downloads

2

Readme

NodeJS config repository

Dotenv wrapper

Set up config

Configuration singleton is created in the main file. If defaultsPath property is provided defaults are red at the moment of config creation. Defaults must be a JSON file.

import {createAppConfig} from 'cfgapp';

createAppConfig([{type: 'json', source: './constants.json'}]);

Use config

Config can be accessed anywhere in application right after createAppConfig() call.

Options from .env file overrides defaults (if any are loaded). For example if option exists in both .env and defaults file, value from .env will be returned by get() call.

In cases when option itself must persist in .env for documentation purposes but contain default value, option's value can be set to "~" (tilde).

import appCfg from 'cfgapp';

const result = appCfg('MY_OPTION');
console.log(result);

Advanced usage

Sometimes it is not enough to have option value only as string. For example you might need to load structured config into some factory object. In those cases you can create option with object structure in defaults file. And override only environment specific parts.

defaults.json

{
    "COMPLEX_OPT": {
        "user": "johndoe",
        "pass": "%PASS%"
    }
}

.env

PASS=TheVerySecretPass
import {createAppConfig, appCfgObject} from 'cfgapp';

createAppConfig([{type: 'json', source: './constants.json'}]);

const result = appCfgObject('COMPLEX_OPT');
console.log(result['pass']); // outputs: TheVerySecretPass