Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

webpack cache PackFileCacheStrategy

See original GitHub issue

i get this issue when i run my app :

[webpack.cache.PackFileCacheStrategy] Skipped not serializable cache item 'mini-css-extract-plugin C:\Users\foxxp\OneDrive\Bureau\projects\clones-react-ecomm\ecomm-react-main\gatsby-ecomm\ec\node_modules\gatsby\node_modules\css-loader\dist\cjs.js??ruleSet[1].rules[10].oneOf[0].use[1]!C:\Users\foxxp\OneDrive\Bureau\projects\clones-react-ecomm\ecomm-react-main\gatsby-ecomm\ec\node_modules\gatsby\node_modules\postcss-loader\dist\cjs.js??ruleSet[1].rules[10].oneOf[0].use[2]!C:\Users\foxxp\OneDrive\Bureau\projects\clones-react-ecomm\ecomm-react-main\gatsby-ecomm\ec\node_modules\sass-loader\dist\cjs.js??ruleSet[1].rules[10].oneOf[0].use[3]!C:\Users\foxxp\OneDrive\Bureau\projects\clones-react-ecomm\ecomm-react-main\gatsby-ecomm\ec\src\components\Footer\Footer.module.scss|0|Compilation/modules|C:\Users\foxxp\OneDrive\Bureau\projects\clones-react-ecomm\ecomm-react-main\gatsby-ecomm\ec\node_modules\gatsby\node_modules\css-loader\dist\cjs.js??ruleSet[1].rules[10].oneOf[0].use[1]!C:\Users\foxxp\OneDrive\Bureau\projects\clones-react-ecomm\ecomm-react-main\gatsby-ecomm\ec\node_modules\gatsby\node_modules\postcss-loader\dist\cjs.js??ruleSet[1].rules[10].oneOf[0].use[2]!C:\Users\foxxp\OneDrive\Bureau\projects\clones-react-ecomm\ecomm-react-main\gatsby-ecomm\ec\node_modules\sass-loader\dist\cjs.js??ruleSet[1].rules[10].oneOf[0].use[3]!C:\Users\foxxp\OneDrive\Bureau\projects\clones-react-ecomm\ecomm-react-main\gatsby-ecomm\ec\src\components\Footer\Footer.module.scss': No serializer registered for Warning
<w> while serializing webpack/lib/cache/PackFileCacheStrategy.PackContentItems -> webpack/lib/NormalModule -> Array { 2 items } -> webpack/lib/Mod

also when the page is loading it takes too long due to __webpack_hmr

Issue Analytics

State:
Created a year ago
Reactions:1
Comments:23 (13 by maintainers)

Top GitHub Comments

3reactions

NevilDabrecommented, Jun 10, 2022

Getting similar error after upgrading Webpack version from 4 to 5 in the Next.js project.

2reactions

unilimpiocommented, May 25, 2022

@vankop we discussed with @sokra and decide do not impement serilizations in loaders for warnings and errors, there are some limitations with registration and make sense better to fix warnings/errors

Thank you for checking this issue out @alexander-akait . Can you maybe offer some hints as to where to start fixing this warning? I checked the link provided by @vankop but honestly I don’t know what to do with it.

Top Results From Across the Web

<w> [webpack.cache.PackFileCacheStrategy] Caching failed ...

I'm having a similar Webpack error. The message is the following: [webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: Unable to snapshot ...

<w> [webpack.cache.PackFileCacheStrategy] Caching failed ...

i have tried clearing and installing everything fresh but the problem still occurs. any help would be greatly appreciated. <t> [webpack.cache.

Cache - webpack

Cache the generated webpack modules and chunks to improve build speed. cache is set to type: 'memory' in development mode and disabled in...

webpack/webpack - Gitter

The .cache directory is being created, a single one aside the "root" ... PackFileCacheStrategy] Caching failed for pack: Error: ENOENT: no such file...

Maximum Runtime exceeds [Next.js] - Netlify Support Forums

2:00:09 PM: [webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: ENOENT: no such file or directory, ...