score:503

Accepted answer

Delete the .next folder at the root of your project, relaunch your project, and force-refresh your page (Shift+F5 / Cmd+Shift+R) to remove the cache.

It apparently is a cache issue. After browsing through GH Issues & various blog posts, my conclusion is that nobody knows what the heck is going on with this webpack-related error, probably caused by Next.js's behavior.

score:1

For me, the problem appeared when I added a plugin to tailwind.config.js (using tailwind)

maybe this will help someone locate strange nextjs behavior

score:1

In my case, I couldn't find the .next folder to be deleted.

Delete all the contents of the build / folder. This worked for me.

score:1

I deleted the .next folder in VSC. The console log generated more errors, so I then restored the folder back to the project. The errors disappeared.

score:5

In my case i had my next.js build directory with a different name as hosted with firebase cloud functions. Follow these similar steps

  1. Delete your build (distDir) directory (mine was called nextjs)
  2. Restart the server
  3. Force Refresh the browser

score:23

I had this error after removing files from the /public folder.

How I fixed it:

  1. Remove your /.next folder.
  2. Launch your project again.
  3. Force refresh in you browser to delete the cache.

Related Query

More Query from same tag