welcoMattic/imagemin.md

Last active August 15, 2024 15:58

Star (6) You must be signed in to star a gist
Fork (0) You must be signed in to fork a gist

Select an option

Learn more about clone URLs
Clone this repository at <script src="https://gist.github.com/welcoMattic/9f0991fa81a80096a3877ee42562c504.js"></script>
Save welcoMattic/9f0991fa81a80096a3877ee42562c504 to your computer and use it in GitHub Desktop.

How to fix `Error: spawn ./node_modules/jpegtran-bin/vendor/jpegtran ENOENT` error for imagemin

Raw

If you're trying to run imagemin (from grunt or gulp or anything else) on Alpine, you certainly had to meet this error :

Error: spawn /YOUR_PROJECT_PATH/node_modules/jpegtran-bin/vendor/jpegtran ENOENT or the same with optipng or gifsicle instead of jpegtran.

Here's how to solve it.

First you need to install on Alpine missing package used to compile jpegtran, gifsicle and optipng binaries. Those packages are (at least):

autoconf automake file build-base nasm musl libpng-dev zlib-dev

Now, rebuild your container.

And then, remove your node_module directory, and run npm install or yarn command.

Enjoy 🎉

Note: this workaround works like a charm for me, please comment here if your meet other issues ;)

jasperf commented Nov 4, 2019

@jnaklaas that really helped me. Got stuck running yarn build:production for my Sage setup. Regular dev build worked but production build choked spitting out

$ webpack --env.production --progress --config resources/assets/build/webpack.config.js
 94% asset optimizationError: spawn /Users/jasper/code/alarsite/wp-content/themes/alar/node_modules/jpegtran-bin/vendor/jpegtran ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
    at onErrorNT (internal/child_process.js:415:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Your yarn add --force jpegtran-bin did the trick. New package-lock.json generation is still wise though:

warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.