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

reverse-config

v0.1.0

Published

Reverse npm package config environment variables into an object.

Downloads

10

Readme

reverse-config npm version build status code climate

Reverse npm package config environment variables into an object.

Installation

$ npm install reverse-config

reverse-config, What is it Good For?

Essentially, this package is just syntactic sugar for reading npm_package_config_* properties from process.env.

Usage

var reverseConfig = require('reverse-config');
reverseConfig.get({string} [key])
  • if key is undefined, the entire configuration object is returned
  • if key is alphanumeric, it is used as property accessor for the configuration object
  • otherwise
    • all non-alphanumeric characters are replaced by underscores
    • consecutive underscores are collapsed to a single one
    • leading and trailing underscores are stripped
    • the remaining value is split with the underscore and used as a 'deep' property accessor
      • example: .get('@my.scoped/package') would try to access .my.scoped.message in the configuration object

Gotchas

The npm transformation of the package.json config object to environment variables is a destructive process.

Given either

{
  "config": {
    "foo": [
      42
    ]
  }
}

or

{
  "config": {
    "foo": {
      "0": 42
    }
  }
}

or

{
  "config": {
    "foo_0": "42"
  }
}

the resulting environment variable name is npm_package_config_foo_0, and its value the string '42'.

Rule of thumb: only use alphanumeric property names.

The useful exception would be package names used as config sections, e.g.

{
  "config": {
    "my_package": {},
    "@my.scope/my-package": {},
  }
}

Use with moderation and pretend to be a responsible adult.

Values

During reversion values are coerced with good faith as follows:

  • numeric string => {number}
  • 'true' => {boolean} true
  • 'false' => {boolean} false
  • 'null' => {null} null

In other words, you might face surprises if you use strings like "42", "true", "false" or "null" as property values in your package.json config object. Don't do that then!.

License

MIT