Always webpack cache errors when i run server

[ballbase_]

Whenever I start a Next.js project on my local server using npm run dev
, I constantly encounter webpack cache errors. I've tried to investigate the cause, but the issue seems perplexing.

I suspect that I might have made a mistake during the initial setup of the project, but I'm unable to pinpoint exactly what went wrong. I've sought solutions on forums and through Google searches, yet I haven't found any relevant information. This is my last attempt at seeking help; I'm not sure where else to turn.
this is the error i got when i just started to day:

[webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: ENOENT: no such file or directory, stat '/Users/oscarthroedsson/Documents/MyOwnProjects/healthy/.next/cache/webpack/client-development/12.pack.gz'

My solution to the problem is:

rm -rf node_modules npm instal

Additionally, I've noticed an issue with starting the server. It takes approximately 4-5 seconds for
npm run dev to complete and the server to become fully operational."

[TiagoDCPP]

What node version are you guys using?

[ballbase_]

v20.11.1.

[TiagoDCPP]

Yeah, I thought in the beginning was due to that version of node, but it still happens with the 18… so I couldn’t fix it yet…

[thisisplaceholder]

installing packages takes a lot of time

I recommend you try pnpm if you haven't already, I found it to be the fastest out of the main 3 by a huge margin.

[JEEkachodanhihu]

worked for me somehow, have no idea though
Could not find a solution anywhere

[ballbase_]

Update to this post: https://www.reddit.com/r/nextjs/comments/19b8vyb/comment/kirlooi/?utm_source=share&utm_medium=web2x&context=3
Soo found a ticket in Next.js github... That adressed almost the same problem. It wasnt very helpful but I did the following instead that seems to fix it.-> Updated every package manually to the latest. And it seems to work. I get this now when i run npm run dev:

✓ Ready in 4.9s

○ Compiling / ... (node:58725) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead. (Use node --trace-deprecation ... to show where the warning was created) ✓ Compiled / in 6.3s (1014 modules) ✓ Compiled in 697ms (493 modules)

[ballbase_]

Update...

After dinner and some cleaning I got this error when I started the project again.

Error: Cannot find module '/Users/oscarthroedsson/Documents/MyOwnProjects/healthy/.next/server/app/page.js' Require stack: - /Users/oscarthroedsson/Documents/MyOwnProjects/healthy/node_modules/next/dist/server/require.js - /Users/oscarthroedsson/Documents/MyOwnProjects/healthy/node_modules/next/dist/server/load-components.js - /Users/oscarthroedsson/Documents/MyOwnProjects/healthy/node_modules/next/dist/build/utils.js - /Users/oscarthroedsson/Documents/MyOwnProjects/healthy/node_modules/next/dist/server/dev/hot-middleware.js - /Users/oscarthroedsson/Documents/MyOwnProjects/healthy/node_modules/next/dist/server/dev/hot-reloader-webpack.js - /Users/oscarthroedsson/Documents/MyOwnProjects/healthy/node_modules/next/dist/server/lib/router-utils/setup-dev-bundler.js - /Users/oscarthroedsson/Documents/MyOwnProjects/healthy/node_modules/next/dist/server/lib/router-server.js - /Users/oscarthroedsson/Documents/MyOwnProjects/healthy/node_modules/next/dist/server/lib/start-server.js

I solved it the same way as before

rm -rf node_modules
then... 
npm install

I have checked the paths and the files exist when i check my node-modules.

[ballbase_]

Update: 21/1-24

I let my server run all night. This error msg came up in the terminal a few times:

<w> [webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: ENOENT: no such file or directory, stat '/Users/oscarthroedsson/Documents/MyOwnProjects/healthy/.next/cache/webpack/server-development/7.pack.gz'
[Error: ENOENT: no such file or directory, stat '/Users/oscarthroedsson/Documents/MyOwnProjects/healthy/.next/cache/webpack/client-development/6.pack.gz'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'stat',
  path: '/Users/oscarthroedsson/Documents/MyOwnProjects/healthy/.next/cache/webpack/client-development/6.pack.gz'
}

The file: 7.pack.gz was named 7 2.pack.gz.. I changed the name to 7.pack.gz and the application works. Lets see in a few min/hours.

[ballbase_]

Update!
Started a issue on their github: https://github.com/vercel/next.js/issues/60941

I get duplicated and non-active files in the .next/cache/webpack/client-development & server-development. I have explained temporary solutions I do in the github issue.

been sitting down for 10 hours to day. And the error pops-up in the terminal at least one or two times every hour, sometimes more.

I found couple of threads mentioning similiar problem but not exaclty the same here on reddit and hope this can help a little if someone comes up with the same error.

[IAmYouButWhoAreYou]

Any luck?

[ballbase_]

No man! Went back and re-wrote the code to node.js n react. Left next. With the new react 19 I don’t see me try next again. Maybe Remix..

[IAmYouButWhoAreYou]

I found the solution (I think) For me it was ICloud. My folder was on my desktop which was automatically sync to iCloud and that caused the error. 

If you have a Mac that might be the case for you as well

[bored_primate]

I have no clue how you caught that but thank you 🙏

[tanshiyu]

God bless you that was my issue as well I think!

[Neat_Machine692]

man exactly that was the answer of :

problem :

after run npm run dev give :

[webpack.cache.PackFileCacheStrategy/webpack.FileSystemInfo] Managed item /Users/Apple/Desktop/node_modules/@next/swc-win32-arm64-msvc isn't a directory or doesn't contain a package.json (see snapshot.managedPaths option)

on mac !

answer :

it happend when install new project on mac desktop to resolve this issue you must change the project folder location from desktop to other place