nextjs-client-server-boundary-module-errors
Fix Next.js 16 build errors "Module not found: Can't resolve 'dns', 'fs', 'net', 'tls'" when client components import constants from files that transitively import Node.js modules. Use when: (1) Build fails with Node.js module resolution errors in client components, (2) Error trace shows [Client Component Browser] importing from a utility file, (3) Constants or shared code in a file with database/Prisma/server imports. Solves client/server boundary violations by extracting shared constants to isolated files.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Features and purpose
Fix Next.js 16 build errors "Module not found: Can't resolve 'dns', 'fs', 'net', 'tls'" when client components import constants from files that transitively import Node.js modules. Use when: (1) Build fails with Node.js module resolution errors in client components, (2) Error trace shows [Client Component Browser] importing from a utility file, (3) Constants or shared code in a file with database/Prisma/server imports. Solves client/server boundary violations by extracting shared constants to isolated files.
Quick start
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
Guides ↗Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-24
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!