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 🙏

© 2025 – Pkg Stats / Ryan Hefner

nconf-jsonenv

v1.0.0

Published

Configure nconf with JSON from environment variables

Readme

nconf-jsonenv

Configure nconf with JSON from environment variables.

By default it looks for environment variables with prefix JSONCONF_, parses them as JSON and merges them into the nconf config. Environment variables are processed alphabetically, so you can control their order using simple A-Z naming conventions JSONCONF_A, JSONCONF_B, etc.

By default all configs are merged into the top-level config, but this can be overridden by adding a second environment variable with the same name, and suffix _AT with the nconf path where the config should be added.

For example, suppose the following environment variables are defined.

export JSONCONF_A='{"port": 3000}'
export JSONCONF_B='{"hostname": "127.0.0.1", "password": "shhh"}'
export JSONCONF_B_AT='db:main'

They would produce the following nconf configuration.

{
	port: 3000,
	db: {
		main: {
			hostname: '127.0.0.1',
			password: 'shhh'
		}
	}
}

Installation

npm install --save nconf nconf-jsonenv

Usage

const nconf = require('nconf');
require('nconf-jsonenv');

nconf.use('jsonenv');

Options

  • prefix - string prefix to match for environment variables, default "JSONCONF_"
  • suffix - string to indicate merge path override, default "_AT"
  • readOnly - boolean if values can be overridden, default false.

Example passing custom options:

nconf.use('jsonenv', {
	prefix: 'CUSTOM',
	suffix: 'X',
	readOnly: false
});