nextjs-client-server-boundary-dns-error

Next.js builds fail with DNS errors when server-only Prisma modules leak into client component bundles. Importing Prisma bindings through barrel exports or using Prisma enums in client components violates the client/server boundary.

Fix Prisma boundary violations in Next.js by importing directly from component files, separating server utilities from client code, and configuring dependencies to exclude server code from the client bundle.

Barrel exports break Next.js client/server boundaries by bundling server-only modules into client components. When an index file re-exports both server and client code, importing it into a client component pulls server dependencies into the browser bundle.

Using Prisma enums in Next.js client components causes client/server boundary violations because it pulls server-only Prisma bindings into the client bundle. Extract enum values into plain objects or shared types to keep the client bundle clean.

The best way to avoid Next.js module resolution errors is to bypass barrel exports and import directly from individual component files. This ensures server-only code is never accidentally bundled into client components.

The limitation of barrel exports is they obscure module origins, causing Next.js to bundle server-only Prisma code into client components. You must separate server/client utilities and use direct imports to prevent these resolution errors.