How to fix the `can't resolve module` error in Next.js
New Courses Coming Soon
Join the waiting lists
I ran into this issue with Next.js:
Module not found: Can’t resolve ‘fs’
In a Next.js page your can import methods from a file that loads Node.js modules.
This is fine, as long as you also use the imported method in getStaticProps().
Example, I had this code:
import { getData } from '../lib/data'
//...
export async function getStaticProps() {
const data = getData()
return {
props: {
data,
},
}
}
When I commented const data = getData()
, Next started giving me the error 'fs' module not found
because fs
was the first module I imported in lib/data
.
It might happen with any other Node library you import first.
This happens because anything in getStaticProps() is just called when ran in a server environment, but if we don’t invoke the Node.js function in there, Next.js can’t know that.
→ Get my Next.js (pages router) Handbook
Here is how can I help you:
- COURSES where I teach everything I know
- CODING BOOTCAMP cohort course - next edition in 2025
- BOOKS 16 coding ebooks you can download for free on JS Python C PHP and lots more
- Follow me on X