envzod 1.0.0 → 1.0.1

package/README.md

@@ -10,7 +10,7 @@ Works with **Next.js, Express, Fastify, Remix, Bun** — any Node.js project.
 
 - `process.env` values are all `string | undefined` — no types, no validation
 - Errors surface at runtime deep in your app instead of at startup
-- `zod-env` validates your env at boot and gives you a **fully typed object** — no casting needed
+- `envzod` validates your env at boot and gives you a **fully typed object** — no casting needed
 
 ---
 
@@ -52,7 +52,7 @@ env.NODE_ENV     // "development" | "test" | "production"
 
 ## Error Output
 
-When validation fails, `zod-env` prints a clear, readable error and throws:
+When validation fails, `envzod` prints a clear, readable error and throws:
 
 ```
 ╔════════════════════════════════════════════╗
@@ -109,19 +109,34 @@ type EnvValidationError = {
 
 ### Next.js (App Router)
 
+> **Important:** Next.js only inlines `NEXT_PUBLIC_*` vars when referenced **explicitly** (e.g. `process.env.NEXT_PUBLIC_FOO`). Passing the whole `process.env` object doesn't work on the client side. Always use the `source` option and list each var individually.
+
 ```ts
 // src/env.ts
 import { createEnv } from 'envzod'
 import { z } from 'zod'
 
-export const env = createEnv({
-  DATABASE_URL: z.string().url(),
-  JWT_SECRET: z.string().min(32),
-  NODE_ENV: z.enum(['development', 'test', 'production']).default('development'),
-  NEXT_PUBLIC_API_URL: z.string().url(),
-}, {
-  verbose: process.env.NODE_ENV === 'development',
-})
+export const env = createEnv(
+  {
+    // Server-only vars
+    DATABASE_URL: z.string().url(),
+    JWT_SECRET: z.string().min(32),
+    NODE_ENV: z.enum(['development', 'test', 'production']).default('development'),
+
+    // Public vars (accessible in browser)
+    NEXT_PUBLIC_API_URL: z.string().url(),
+  },
+  {
+    // Must explicitly list each var so Next.js/Turbopack can statically inline them
+    source: {
+      DATABASE_URL: process.env.DATABASE_URL,
+      JWT_SECRET: process.env.JWT_SECRET,
+      NODE_ENV: process.env.NODE_ENV,
+      NEXT_PUBLIC_API_URL: process.env.NEXT_PUBLIC_API_URL,
+    },
+    verbose: process.env.NODE_ENV === 'development',
+  },
+)
 ```
 
 ### Express
@@ -165,7 +180,7 @@ export const env = createEnv({
 
 ## TypeScript
 
-`zod-env` uses the `InferEnv<T>` utility type to derive the return type from your schema. No manual type annotations needed.
+`envzod` uses the `InferEnv<T>` utility type to derive the return type from your schema. No manual type annotations needed.
 
 ```ts
 import type { InferEnv } from 'envzod'
@@ -184,7 +199,7 @@ type Env = InferEnv<typeof schema>
 
 ## vs t3-env
 
-| Feature | zod-env | t3-env |
+| Feature | envzod | t3-env |
 |---|---|---|
 | Framework | Universal | Next.js focused |
 | Setup | `createEnv(schema)` | Separate client/server schemas |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "envzod",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "Universal, type-safe environment variable validation powered by Zod. Zero config, works everywhere.",
   "main": "./dist/index.js",
   "module": "./dist/index.mjs",