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

@ctroenv/nextjs

v1.2.1

Published

Next.js adapter for CtroEnv — client/server split, build-time validation, and type safety

Readme

@ctroenv/nextjs

npm version npm downloads license

Next.js adapter for CtroEnv — client/server env splitting with build-time validation and runtime access control.

Installation

npm install @ctroenv/nextjs

Usage

import { defineEnv, string } from "@ctroenv/nextjs"
import type { ClientServerSchema } from "@ctroenv/core"

const schema = {
  server: {
    DATABASE_URL: string().url(),
    JWT_SECRET: string().secret(),
  },
  client: {
    NEXT_PUBLIC_API_URL: string().url(),
  },
} satisfies ClientServerSchema

const env = defineEnv(schema)

// Server-side: all variables accessible
env.DATABASE_URL  // string
env.JWT_SECRET    // "********" (masked)
env.NEXT_PUBLIC_API_URL // string

// Client-side: server-only access throws
// env.DATABASE_URL → "Server-only environment variable..." error

Build-Time Validation

// next.config.ts
import { withCtroEnv } from "@ctroenv/nextjs"
import type { NextConfig } from "next"

const schema = { server: { ... }, client: { ... } }

const nextConfig: NextConfig = { /* your config */ }

export default withCtroEnv(schema, nextConfig)

Validates all environment variables at build start and logs errors before Next.js compiles.

API

| Function | Description | |----------|-------------| | defineEnv(schema, opts?) | Returns proxied env object with server/client access control | | withCtroEnv(schema, config?) | Next.js config wrapper with build-time validation |

defineEnv

defineEnv<T extends ClientServerSchema>(
  schema: T,
  opts?: { maskWith?: string },
): InferredClientServerEnv<T>

| Option | Type | Default | Description | |--------|------|---------|-------------| | maskWith | string | "********" | Custom string for masking .secret() values |

Proxy Behavior

The returned env object uses a Proxy to enforce access control at runtime:

  • Server side: All keys from both server and client schemas are accessible.
  • Client side: Only client keys are accessible. Accessing a server key throws an error with a message suggesting NEXT_PUBLIC_ prefix.
  • Secret values: Keys marked with .secret() are masked to "********" (or custom maskWith). Raw values are accessible via env.meta.get("KEY").
  • meta object: Non-enumerable property providing .get(), .has(), .keys(), and .toJSON().

Secret Values

env.JWT_SECRET            // "********"
env.meta.get("JWT_SECRET") // actual value
env.meta.keys()           // ["DATABASE_URL", "JWT_SECRET", ...]
env.meta.has("JWT_SECRET") // true
env.meta.toJSON()         // { DATABASE_URL: "...", JWT_SECRET: "...", ... }

Types

import type { ClientServerSchema, InferredClientServerEnv } from "@ctroenv/core"
import type { InferredNextEnv } from "@ctroenv/nextjs"

// InferredNextEnv<T> is an alias for InferredClientServerEnv<T>

// Legacy type (deprecated — use ClientServerSchema instead):
import type { NextSchemaDefinition } from "@ctroenv/nextjs"

Documentation

Full documentation at ctroenv.vercel.app

License

MIT