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

@forwardimpact/libpreflight

v0.1.2

Published

Fail fast at process start with product-authored errors — runtime-floor checks and required-config assertions before heavy imports resolve.

Readme

libpreflight

Fail fast at process start with product-authored errors — runtime-floor checks and required-config assertions before heavy imports resolve.

Usage

Import the side-effect entry as the first import in every published CLI entry script. The package has zero production dependencies, so ESM post-order evaluation guarantees the floor check runs before any sibling import body executes.

#!/usr/bin/env node
import "@forwardimpact/libpreflight/node22";

// the rest of the bin's imports

Under Node >=22 the import returns silently. Under Node <22 the process writes two lines to stderr and exits 1:

Error: This command requires Node.js 22 or later (running 20.11.0).
Install Node.js 22 (LTS) from https://nodejs.org/ and re-run.

The failure intercepts the bin before any heavy static import — including upstream packages whose constructors may raise their own runtime-floor errors — evaluates.

Testable helper

For unit tests, import the parameterised check:

import { check } from "@forwardimpact/libpreflight/check.js";

const mockProcess = {
  versions: { node: "20.11.0" },
  stderr: { write: (chunk) => { /* capture */ } },
  exit: (code) => { /* capture */ },
};
check(22, mockProcess);

Required-config assertion

Call assertNonEmpty(value, label) from server.js immediately after createServiceConfig to fail the process at startup if a required configuration value is empty. Empty means an empty string, an empty array, an empty Set, or undefined/null.

import { assertNonEmpty } from "@forwardimpact/libpreflight/assert-non-empty.js";

const config = createServiceConfig("svc", { link_completion_ticket_secret: "" });
assertNonEmpty(config.link_completion_ticket_secret, "link_completion_ticket_secret");

On failure the process writes Error: required configuration "<label>" is empty. to stderr and exits 1. A test injects a processObj exposing stderr.write and exit.

Why a side-effect import per floor

Encoding the floor in the subpath (./node22, future ./node24, …) keeps the import statement self-describing and lets a CI invariant cross-check the floor literal against the importing package's engines.node.