You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi.
I have problem witch your package on linux x86, we use some packages for frontend on web aplication.
One package for compile js, css and other things use imagemin/gifsicle-bin version 3.0.4.
This package use gifsicle parameter: gifsicle --no-app-extensions.
The main ploblem is that gifsicle 1.71 do not have console parametr "--no-app-extensions" and my frontend build fails on error: missing parameter, if is operation with gif picture.
Can you fix it with new release where is binary file on same version for all platforms?
It is big problem becouse developers use platform what they like and they will expect than if they install npm package with same version on diferent platform, package will have same behaviours.
The text was updated successfully, but these errors were encountered:
Hi.
I have problem witch your package on linux x86, we use some packages for frontend on web aplication.
One package for compile js, css and other things use imagemin/gifsicle-bin version 3.0.4.
This package use gifsicle parameter: gifsicle --no-app-extensions.
If i install package over npm, on my local mashine will be installed gifsicle binary version: 1.71
from source: https://raw.githubusercontent.com/imagemin/gifsicle-bin/v3.0.4/vendor/linux/x64/gifsicle
On linux x64 is other binary version: 1.87
from source: https://raw.githubusercontent.com/imagemin/gifsicle-bin/v3.0.4/vendor/linux/x64/gifsicle
The main ploblem is that gifsicle 1.71 do not have console parametr "--no-app-extensions" and my frontend build fails on error: missing parameter, if is operation with gif picture.
Can you fix it with new release where is binary file on same version for all platforms?
It is big problem becouse developers use platform what they like and they will expect than if they install npm package with same version on diferent platform, package will have same behaviours.
The text was updated successfully, but these errors were encountered: