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

@briskforge/envcheck

v0.5.5

Published

Tiny environment-variable validator with aggregated errors

Readme

@briskforge/envcheck

Tiny environment-variable validator. Walks a schema, checks each value, coerces numeric/boolean/json kinds, throws one error per call that lists every problem.

Install

npm i @briskforge/envcheck

Usage

import envcheck from '@briskforge/envcheck';

// Server / Node — reads from process.env when no source is passed.
const env = envcheck({
  PORT: 'integer',
  NODE_ENV: 'string',
  DATABASE_URL: 'url',
  ENABLE_CACHE: 'boolean',
});

// Vite / Webpack — pass the bundler's env map.
const clientEnv = envcheck(
  {
    VITE_RPC_ETH: 'url',
    VITE_RPC_POLYGON: 'url',
    VITE_WALLETCONNECT_PROJECT_ID: 'string',
  },
  import.meta.env,
);

If a key is missing or fails its kind check, the call throws:

Error: envcheck failed:
  - PORT: not an integer
  - DATABASE_URL: missing

(err.errors carries the same list as a string array.)

API

envcheck<S>(schema: S, env?: Record<string, string | undefined>): { [K in keyof S]: unknown }

Schema entries

Each entry is either a kind or a spec object:

type Kind =
  | 'string'    // any non-empty string
  | 'url'       // must include a protocol (https://...)
  | 'number'    // any finite number
  | 'integer'   // integer only
  | 'boolean'   // accepts true|false|1|0
  | 'email'
  | 'json'      // parsed via JSON.parse

type Spec = { kind: Kind, optional?: boolean, default?: unknown }
envcheck({
  HOSTNAME: 'string',
  RETRIES: { kind: 'integer', default: 3 },
  SENTRY_DSN: { kind: 'url', optional: true },
});

Source argument

  • Omit it on Node and envcheck reads process.env.
  • Pass import.meta.env for Vite or process.env for Webpack-injected.
  • Pass any plain object for tests.

Helpers

envcheck.KINDS       // string[] — all accepted kinds
envcheck.isURL(s)    // boolean — same check as the 'url' kind uses
envcheck.isEmail(s)  // boolean — same check as the 'email' kind uses

License

MIT.