Getting weird errors about image-webpack-loader HOT 4 CLOSED

i found the reason..

imagemin/imagemin-pngquant#32

from image-webpack-loader.

@milewski

Just out of curiosity, what are the specs for the box you were trying to build on?

I was running into the exact same error trying to build on an Amazon EC2 Nano (1 cpu and 0.5GB memory).

The link you gave, unfortunately, didn't end up helping in my case.

It wasn't until I added 2GB of swap that it finally built correctly while retaining my original pngquant settings.

Not sure if this error is always due to insufficient memory or if that was only the case for me, but definitely something to look into if you're getting this error.

from image-webpack-loader.

@Narkoleptika i was on a high end computer (local dev) dont remember the specs.. but however the problem wasnt related to memory, but pngquant "thows an error" if the range is tooo narrow... it has been closed in that issue i pointed but i cant confirm if that still happens nowadays... but the fix was... increase the max/min quality range... and you should be good to go~

if changing the range doesnt solve your problem u could use imagemin-pngcrush instead and u could hookup this custom plugin with imagemin-loader

from image-webpack-loader.

I'm closing this, because the original issue looks solved. If you have any other issues, please create a separate ticket.

from image-webpack-loader.