nextjs-client-server-boundary-dns-error

Community

Fix Next.js DNS errors with Prisma.

AuthorDavidTeju
Version1.0.0
Installs0

System Documentation

What problem does it solve?

Next.js builds can fail when server-only modules or Prisma bindings are bundled into client components, causing misleading DNS/module-resolution errors and broken client/server boundaries.

Core Features & Use Cases

  • Detects common client/server boundary violations such as barrel exports importing server code or client components importing Prisma enums.
  • Provides actionable, step-by-step fixes: import directly from component files, separate server utilities from client code, and avoid exposing server dependencies in client bundles.
  • Use cases include Next.js apps using Prisma with pg adapter, where build errors show client component browser traces.

Quick Start

Audit your Next.js project for server-only imports in client components and apply the recommended fixes.

Dependency Matrix

Required Modules

None required

Components

Standard package

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: nextjs-client-server-boundary-dns-error
Download link: https://github.com/DavidTeju/shared-skills/archive/main.zip#nextjs-client-server-boundary-dns-error

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.