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

@nurliman/env-valibot

v0.7.2

Published

[![jsr.io/@nurliman/env-valibot](https://jsr.io/badges/@nurliman/env-valibot)](https://jsr.io/@nurliman/env-valibot) [![jsr.io/@nurliman/env-valibot score](https://jsr.io/badges/@nurliman/env-valibot/score)](https://jsr.io/@nurliman/env-valibot) [![npm Ve

Downloads

91

Readme

Typesafe Envs made Simple

jsr.io/@nurliman/env-valibot jsr.io/@nurliman/env-valibot score npm Version

Deploying your app with invalid environment variables is a hassle. This package helps you to avoid that.

Installation

[!NOTE]

This is an ESM only package that requires a tsconfig with a module resolution that can read package.json#exports (NodeNext if transpiling with tsc, Bundler if using a bundler).

# deno
deno add @nurliman/env-valibot @valibot/valibot

# npm (one of the below, depending on your package manager)
npx jsr add @nurliman/env-valibot @valibot/valibot
yarn dlx jsr add @nurliman/env-valibot @valibot/valibot
pnpm dlx jsr add @nurliman/env-valibot @valibot/valibot
bunx jsr add @nurliman/env-valibot @valibot/valibot

Currently only supports Valibot (which you'll need to install separately). Bring your own validation library is on the roadmap.

Usage

For full documentation, see https://env.t3.gg

This package supports the full power of Valibot, meaning you can use transforms and default values.

Define your schema

// src/env.mjs
import { createNextjsEnv } from "@nurliman/env-valibot";
import * as v from "@valibot/valibot";

export const env = createNextjsEnv({
  /*
   * Serverside Environment variables, not available on the client.
   * Will throw if you access these variables on the client.
   */
  server: {
    DATABASE_URL: v.pipe(v.string(), v.url()),
    OPEN_AI_API_KEY: v.pipe(v.string(), v.minLength(1)),
  },
  /*
   * Environment variables available on the client (and server).
   *
   * 💡 You'll get type errors if these are not prefixed with NEXT_PUBLIC_.
   */
  client: {
    NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY: v.pipe(v.string(), v.minLength(1)),
  },
  /*
   * Due to how Next.js bundles environment variables on Edge and Client,
   * we need to manually destructure them to make sure all are included in bundle.
   *
   * 💡 You'll get type errors if not all variables from `server` & `client` are included here.
   */
  runtimeEnv: {
    DATABASE_URL: process.env.DATABASE_URL,
    OPEN_AI_API_KEY: process.env.OPEN_AI_API_KEY,
    NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY:
      process.env.NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY,
  },
});

Use the schema in your app with autocompletion and type inference

// src/app/hello/route.ts
import { env } from "../env.mjs";

export const GET = (req: Request) => {
  const DATABASE_URL = env.DATABASE_URL;
  // use it...
};

Roadmap

  • [ ] Bring your own validation library - currently only supports Valibot.