Help with "[webpack.cache.PackFileCacheStrategy] Serializing big strings (834kiB) impacts deserialization performance (consider using Buffer instead and decode when needed)" #57843
Replies: 4 comments 1 reply
-
Beta Was this translation helpful? Give feedback.
-
Hi, did you find any track on how to debug this ? I also have the warning in development environment and I'd like to debbug and fix it ! |
Beta Was this translation helpful? Give feedback.
-
Im ditching nextjs now I've had enough headache just trying to make things work when building the app, thanks for 3 years 🤣 |
Beta Was this translation helpful? Give feedback.
-
I totally get the frustration! One thing that helped me was using next-transpile-modules and tweaking Webpack configs manually. Sometimes removing unnecessary large dependencies also improves build performance. Maybe worth a shot before switching? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
I keep getting this in my Next.js web app:
I get this when deploying to Vercel / production, and when running
next build
locally. How do I debug this to figure out what is causing this statement? It is causing my builds to take over 5 minutes each time, which is annoying to work with. Is there anything straightforward to either:Thank you for your help in advance!
Additional information
Here is my basic info:
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions