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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@inim/comfig

v1.0.1

Published

Easily get configuration / inputs to the app.

Downloads

10

Readme

Comfig

Super easy development-time config management for apps/mods.

How To

Just ask for a config item, and comfig will look high and low for it, following consistent rules.

const Comfig = require('@inim:comfig');

const cfg = Comfig('FOOBAR', 'FOO');                // The name of your app/lib

let wooden = cfg.getItem('USE_WOODEN_BAT');         // Reads env.FOOBAR_USE_WOODEN_BAT, or --use-wooden-bat; gets the string "true"
wooden = cfg.getItem('USE_WOODEN_BAT', false);      // Reads env.FOOBAR_USE_WOODEN_BAT, or --use-wooden-bat; gets the boolean true

wooden = cfg.smartGetItem('USE_WOODEN_BAT');        // Auto-parses into Number, Boolean, Date, JSON (so an Object), or String

let aluminum = cfg.getItem('USE_AL_BAT');           // Not found anywhere: aluminum is undefined

Remember that all of the places that Comfig could look at when fetching the configuration items will return a string: CLI args are all strings until parsed, same for env.XYZ. But when you pass in a default value, the function knows the type and will parse it into that type. This works only with non-compound (builtin) types: Number, String, Boolean.

Future

TBD: Will follow 12 principles when not ACTIVE_DEVELOPMENT.