Closed childrentime closed 1 year ago
Firstly
how should we fix it?
Only change options for autoprefixer, if postcss returns warnings we print them
The yellow warnings are really ugly.
Not sure what do you mean, yellow is default color for warnings
Even we solve problems with cache you will have these warnings in console until you fix your configuration
Well, thanks a lot. Anyway I can't use it beacuse I currently use node12🥹. Ofcourse I know the yellow is default color for warnings, it's just bothering when seeing it.
Just update node.js :smile:
System: OS: Windows 11 10.0.22621 CPU: (12) x64 AMD Ryzen 5 5500U with Radeon Graphics Memory: 1.54 GB / 7.33 GB Binaries: Node: 20.11.0 - C:\Program Files\nodejs\node.EXE Yarn: 1.22.21 - ~\AppData\Roaming\npm\yarn.CMD npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD Browsers: Edge: Chromium (121.0.2277.83) Internet Explorer: 11.0.22621.1 Packages: webpack: ^5.90.0 => 5.90.0 webpack-cli: ^5.1.4 => 5.1.4
Bug report
postcss-loader will emit warnning when some css has ambiguity. But it will cause unstoppable yellow warning in terminal. It is because postcss-loader custom defined a
Waring
object and emit it withthis.emitWarning
Actual Behavior
print waring in terminal even with
stat: false
Expected Behavior
do not emit non-serializable object
How Do We Reproduce?
https://github.com/childrentime/webpack-cache-reproduce
Please paste the results of
npx webpack info
here, and mention other relevant information