Hyperse
  • Pricing
  • FAQs
Newsletter

Subscribe to our newsletter

Receive weekly updates with latest collections and exclusive offers, straight to your inbox.

Hyperse

Headless commerce solutions for brands, developers, and modern ecommerce teams.

Explore

  • Home
  • About Us
  • Partners
  • FAQs

Legal & resources

  • Proposal
  • Privacy Policy
  • Terms & Conditions

© 2026 Hyperse. All rights reserved.


  1. Back to Popular Libraries
  2. @hyperse/next-config
Next.js Configuration

@hyperse/next-config

A type-safe configuration toolkit for Next.js. Simplifies managing environment variables, runtime options, and shared settings across projects, ensuring safety and consistency in production.

typescriptnextjsconfigurationenvhyperse

Quick start

git clone https://github.com/hyperse-io/hero-tel-input.git
loading...

On this page

  • @hyperse/next-config
    • Features
    • Installation
    • API Reference
      • createNextConfig
      • createNextConfigEnv
      • Example Usage
    • License

@hyperse/next-config

Type-safe environment variables and runtime configuration patterns for Next.js applications

build stable version GitHub top language Licence

A powerful utility package that provides type-safe environment variables and flexible configuration patterns for Next.js applications. Built with TypeScript and Zod for maximum type safety and runtime validation.

Features

  • 🔍 Type-safe Environment Variables: Validate and type-check your environment variables using Zod schemas
  • 🛡️ Runtime Validation: Catch environment variable errors early with detailed validation messages
  • 🔌 Plugin System: Extensible plugin architecture for Next.js configuration
  • 📝 Development Feedback: Clear console output of validated environment variables during development
  • 🎯 TypeScript First: Full TypeScript support with comprehensive type definitions
  • 🚀 Zero Runtime Overhead: Minimal impact on production builds

Installation

API Reference

createNextConfig

Creates a normalized Next.js configuration by applying a series of plugins.

createNextConfigEnv

Validates and type-checks environment variables using Zod schemas.

Example Usage

Here's a complete example showing how to use both features together:

License

MIT © Hyperse

# Using npm
npm install --save @hyperse/next-config
# Using yarn
yarn add @hyperse/next-config
# Using pnpm
pnpm add @hyperse/next-config
import { createNextConfig } from '@hyperse/next-config';
const config = createNextConfig(
{
// Your initial Next.js config
reactStrictMode: true,
},
[
// Array of plugins that transform the config
(config) => ({
...config,
// Add your modifications
}),
]
);
export default config;
import { createNextConfigEnv } from '@hyperse/next-config';
import { z } from 'zod';
// Define your environment variable schema
const envSchema = z.object({
DATABASE_URL: z.string().url(),
API_KEY: z.string().min(32),
PORT: z.string().optional(),
});
// Validate and get typed environment variables
const env = createNextConfigEnv(envSchema);
// Now you have type-safe access to your env vars
const dbUrl = env.DATABASE_URL; // Type: string
const port = env.PORT; // Type: string | undefined
// next.config.mjs
import { createNextConfig, createNextConfigEnv } from '@hyperse/next-config';
import { z } from 'zod';
// Define and validate environment variables
const envSchema = z.object({
NEXT_PUBLIC_API_URL: z.string().url(),
DATABASE_URL: z.string().url(),
});
const env = createNextConfigEnv(envSchema);
// Create Next.js config with plugins
const config = createNextConfig(
{
// Base config
reactStrictMode: true,
env: {
// Access validated env vars
NEXT_PUBLIC_API_URL: env.NEXT_PUBLIC_API_URL,
},
},
[
// Add your custom plugins
(config) => ({
...config,
// Your customizations
}),
]
);
export default config;