Next.js cannot find module loader.js

Question

This is the error is occurring when I try to run a npm run dev.

I don't understand what's happening and I tried these: deleting package-lock.json, deleting node_modules, reinstalling npm, but nothing works.

PS D:\Users\user\Documents\Projects\NLW#5\podcastrnext> npm run dev

> [email protected] dev D:\Users\user\Documents\Projects\NLW#5\podcastrnext
> next dev

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
info  - Using webpack 5. Reason: no next.config.js https://nextjs.org/docs/messages/webpack5
error - ../../NLW#5/podcastrnext/node_modules/next/dist/client/dev/amp-dev.js
Error: Cannot find module 'D:\Users\user\Documents\Projects\NLW#5\podcastrnext\node_modules\@next\react-refresh-utils\loader.js'
Require stack:
- D:\Users\user\Documents\Projects\NLW#5\podcastrnext\node_modules\next\dist\compiled\webpack\bundle5.js
- D:\Users\user\Documents\Projects\NLW#5\podcastrnext\node_modules\next\dist\compiled\webpack\webpack.js
- D:\Users\user\Documents\Projects\NLW#5\podcastrnext\node_modules\next\dist\next-server\server\config-utils-worker.js
- D:\Users\user\Documents\Projects\NLW#5\podcastrnext\node_modules\next\dist\next-server\server\config-utils.js
- D:\Users\user\Documents\Projects\NLW#5\podcastrnext\node_modules\next\dist\next-server\server\config.js
- D:\Users\user\Documents\Projects\NLW#5\podcastrnext\node_modules\next\dist\server\next.js
- D:\Users\user\Documents\Projects\NLW#5\podcastrnext\node_modules\next\dist\server\lib\start-server.js
- D:\Users\user\Documents\Projects\NLW#5\podcastrnext\node_modules\next\dist\cli\next-dev.js
- D:\Users\user\Documents\Projects\NLW#5\podcastrnext\node_modules\next\dist\bin\next
<i> [webpack.cache.PackFileCacheStrategy/webpack.FileSystemInfo] Node.js doesn't offer a (nice) way to introspect the ESM dependency graph yet.
<i> Until a full solution is available webpack uses an experimental ESM tracking based on parsing.
<i> As best effort webpack parses the ESM files to guess dependencies. But this can lead to expensive and incorrect tracking.
<i> [webpack.cache.PackFileCacheStrategy/webpack.FileSystemInfo] Node.js doesn't offer a (nice) way to introspect the ESM dependency graph yet.
<i> Until a full solution is available webpack uses an experimental ESM tracking based on parsing.
<i> As best effort webpack parses the ESM files to guess dependencies. But this can lead to expensive and incorrect tracking.

Luis Oliveira · Accepted Answer · 2021-05-03 20:11:35Z

19

I had this same issue, removing the "#" from the project path worked just fine.

answered May 3, 2021 at 20:11

Luis Oliveira

1913 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Driezzz Over a year ago

That fixed it for me, thanks!

Victor Pessanha · Accepted Answer · 2021-05-01 21:03:54Z

10

I was able to resolve my problem, I don't know exactly what it was, but I might have a clue.

I was trying to run in this folder "D:\Users\user\Documents\Projects\NLW#5\podcastrnext" and didn't work. Than I tried changing to another folder, this is the folder that I used "D:\Users\user\Documents\Projects\podcastr" and this time worked.

I believe the problem was in the special character "#", somehow the program got lost with it.

answered May 1, 2021 at 21:03

Victor Pessanha

2211 gold badge2 silver badges7 bronze badges

2 Comments

shahriarpshuvo Over a year ago

Helps me. Special characters on directory path causing this problem. Thank you!

Brendan Over a year ago

I had a hyphen in my directory path, removing it worked for me!

Thiago Menezes de Oliveira · Accepted Answer · 2021-09-01 20:20:47Z

2

In file next.config.js insert in module.exports:

webpack5: false

answered Sep 1, 2021 at 20:20

Thiago Menezes de Oliveira

292 bronze badges

2 Comments

kingshuk basak Over a year ago

You are a Life-saver !

Brendan Over a year ago

Tried this but got "Webpack 4 is no longer supported in Next.js. Please upgrade to webpack 5 by removing "webpack5: false" from next.config.js." ... I am running Next version 12.1.5

Brendan · Accepted Answer · 2022-06-05 16:02:46Z

0

I had a hyphen in my root directory for my Next.js project, changing my root folder from my-app to just myapp fixed the issue.

answered Jun 5, 2022 at 16:02

Brendan

1,07511 silver badges12 bronze badges

Collectives™ on Stack Overflow

Next.js cannot find module loader.js

4 Answers 4

1 Comment

2 Comments

2 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

1 Comment

2 Comments

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related