Next.js · build error

Module not found: Can't resolve 'fs'

./src/app/blog/page.tsx:2:1
Error: Module not found: Can't resolve 'fs'
> 2 | import fs from "fs";

What it means

Code that uses a Node.js API (fs, path, net, tls, child_process) is being bundled for the browser, where those modules don't exist.

Common causes

• fs or path used inside a "use client" file
• A client component imports a helper that reads files, or a Node-only package (database drivers, nodemailer)
• A typo in an import path also gives Module not found, for your own files

How to fix it

1. Read files or call Node APIs in a Server Component, route handler or Server Action
2. Pass the result to the client component as props
3. Add import "server-only" to modules that must never reach the browser

Prompt for Cursor or Claude Code

Next.js can't resolve a Node built-in (like fs) in the browser bundle. Trace which "use client" file imports it, move the Node code into a Server Component or Server Action, and add import "server-only" to that module.

Not quite your error? Paste yours into the free VibeBoot Doctor or browse the Next.js error fixer.