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

@tanakapayam/conclude

v0.3.0

Published

Set up your defaults; conclude infers the env vars, config-file keys, and CLI flags, and resolves them all into one settings object.

Readme

@tanakapayam/conclude

The TypeScript / Node.js implementation of conclude.

A setting that can come from a flag, an environment variable, or a config file usually gets written down three times: a flag, an environment variable, and a config-file key -- each with its own name, its own type conversion, and its own copy of the default. conclude has you write it once: declare your settings as defaults, and it derives the rest and resolves every layer into one typed settings object.

Status: early (0.x). The package is complete enough to use and passes every conformance fixture in spec/ -- the same fixtures the Python package passes -- but the API may still change between minor versions. (0.1.0 was published without its build output and cannot be imported; use 0.1.1 or newer.)

npm install @tanakapayam/conclude
npm install ignore   # optional: only for the gitignore check (developer file, strict .env)
import { defineConfig, int, list } from "@tanakapayam/conclude";

const config = defineConfig({
  name: "myapp",
  settings: {
    host: "localhost",
    port: int(8080),
    debug: false,
    tags: list(), // unset by default, but still a list when set
  },
});

const { cli } = config.parseArgs();
console.log(config.resolve({ cli }));
$ MYAPP_PORT=9000 node app.ts --debug --tags a,b
{ host: 'localhost', port: 9000, debug: true, tags: [ 'a', 'b' ] }

That one declaration gave you the flags (--host, --port, --debug, --tags), the environment variables (MYAPP_HOST, MYAPP_PORT, ...), the config-file keys (a [myapp] table in ~/.config/myapp/config.toml or ./.config.toml), a caster for each, and a fully typed result -- settings.port is a number, settings.tags a string[] | null.

The layers

defaults < system < user < project < env < developer < CLI

The user and project config files are on by default; the system file, a .env fallback, and a private, gitignored developer file that beats the environment are opt-in. config.describeSources() reports which are in play, and config.formatEnv(), formatToml() and formatCli() generate templates from the same declaration, and config.formatInvocation(settings) turns resolved settings back into a command line.

Documentation

  • Guide -- builds a small CLI, remind, one idea at a time.
  • Reference -- every option, method and function.
  • The concept -- the language-neutral behavior this package follows.
  • Changelog.

Requirements

Node.js 24 or newer (an ESM package that require() can also load). One runtime dependency, smol-toml, for TOML. The gitignore check (the developer file, or a .env you require to be gitignored) uses the optional peer dependency ignore; without it those features report a setup error rather than silently skipping the check.

Development

npm ci
npm run typecheck
npm test             # the shared conformance fixtures, the API tests, and the docs
npm run build
npm run smoke        # packs the package and checks the tarball from the outside

Sources are TypeScript run directly by Node's type stripping, so they use only erasable syntax (no enums, namespaces or parameter properties).

License

MIT.