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 🙏

© 2025 – Pkg Stats / Ryan Hefner

next-triple-env

v2.0.5

Published

An env manager for NextJS with 3 environments: server, shared, and static

Readme

next-triple-env

This is a package that allows you to construct a Zod-validated 3-environment schema for Next.JS Pages Router.

Inspired by t3-env

Uses next-runtime-env version 1

Environments

server - Accessible only on the server (live env vars)

shared - Accessible on the server and the client (live env vars)

[!NOTE] These variables are prefixed with NEXT_PUBLIC_

static - Accessible on the server and the client (baked in on build)

[!NOTE] These variables are prefixed with NEXT_STATIC_

When server variables are accessed from a browser context, an error will be thrown.

When in dev mode, each schema will be separately validated upon access.

When building, only the static schema will be validated.

On production start, all schemas will be validatd.

If process.env.NODE_ENV === 'production', individual schemas will not revalidated upon access

Example usage

Create a file env.ts

import { createEnv } from 'next-triple-env'

export const env = createEnv({
  server: {
    TOKEN_SECRET: z.string(),
    TOKEN_EXPIRATION_MINUTES: z.coerce.number()
  },
  shared: {
    NEXT_PUBLIC_API_URL: z.string()
  },
  static: {
    NEXT_STATIC_GOOGLE_ANALYTICS_TAG: z.string().optional()
  },

  staticEnvVars: {
    NEXT_STATIC_GOOGLE_ANALYTICS_TAG: process.env.NEXT_STATIC_GOOGLE_ANALYTICS_TAG
  }
})

Edit your Next config:

import { config } from 'next-triple-env/config'
import { env } from './env'

export default config(env, {
  // ...your config
}, {
  // ...next-runtime-env config
})

Now use this file anywhere:

import { env } from './env'

console.log(env.shared.NEXT_PUBLIC_API_URL)

Standalone

If using output: 'standalone', you can set up a script to run before starting your server

// prestandalone.ts
import { prestandalone } from 'next-triple-env/prestandalone'
import { env } from './env'

prestandalone(env, {
  // ...next-runtime-env config
})

Disabling Validation

Besides for env.skip(), validation can be skipped by setting the SKIP_ENV_VALIDATION environment variable.

The value can be any permutation of the 3 environments (server, shared, static) joined by commas without spaces, or all or true for all 3 environments.