Skip to content

Next.js, fix the `module not found` error

New Course Coming Soon:

Get Really Good at Git

While doing some sanitization on a variable in Next.js I ran into this weird problem:

Module not found: Error: Can't resolve 'net'

You might have some variation of it, which says a core Node.js module is missing.

Do NOT npm install net or anything like that. If you already tried, run npm uninstall on those modules.

The problem is this: Next.js is trying to run backend code in the frontend.

In my case it was the DOMPurify library. I was using it inside the component, but instead I had to use it in the getStaticProps() method.

That method runs at build time in the Node environment, where that library expected to be ran into.

Are you intimidated by Git? Can’t figure out merge vs rebase? Are you afraid of screwing up something any time you have to do something in Git? Do you rely on ChatGPT or random people’s answer on StackOverflow to fix your problems? Your coworkers are tired of explaining Git to you all the time? Git is something we all need to use, but few of us really master it. I created this course to improve your Git (and GitHub) knowledge at a radical level. A course that helps you feel less frustrated with Git. Launching Summer 2024. Join the waiting list!
→ Get my Next.js (pages router) Handbook

Here is how can I help you: