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

@variablelab/env

v0.5.6

Published

Only declared variables, checked at boot.

Downloads

1,041

Readme

Contract-first environment configuration. You define the env once with a Standard Schema validator, such as Zod, Valibot or ArkType, and get a typed env object that merges per-environment config with your environment variables.

The core runs on Node, Bun, Deno, the browser, Workers and Edge. Every other entry point is opt-in.

Install

pnpm add @variablelab/env

No validator is bundled. To use Zod, the default in the docs and the validator behind @variablelab/env/zod, install it beside env:

pnpm add zod

Usage

// env.ts
import { defineEnv, schema } from "@variablelab/env";
import * as e from "@variablelab/env/zod";

const Env = schema({
  server: { PORT: e.port, HOST: e.host },
});

export const env = defineEnv({ schema: Env });

Entry points

| Entry point | What it adds | | ------------------------ | ------------------------------------------------------------------- | | @variablelab/env | defineEnv and schema: the runtime-agnostic core. | | @variablelab/env/fs | loadConfig, which reads config files on Node, Bun and Deno. | | @variablelab/env/vite | envConfig(), a Vite plugin. | | @variablelab/env/react | <EnvScript />, which hydrates the runtime env across SSR and CSR. | | @variablelab/env/zod | Zod schema primitives, such as port, host and secret. |

Documentation

All of it is at lab.variable.land/env/docs:

Runnable apps for each runtime are in examples/.

License

The code is MIT. The Sign in brand/ is not: its use is set by BRAND-USE.md.