Open ksmolyanin opened 7 years ago
we can't disable webp in 3.4.1
I've create pull request to fix it
use 3.4.0
Encountered this issue.
I don't think webp can help because you don't know if the browsers support it. The only option is that generate two images. One for the original format one for webp format, and let developer choose which to use. But it still doesn't help because there is an easy way to let developers reference them.
My images are created as webp but I didnt specified webp option, what is going on?
loaders: [
'file-loader',
{
loader: 'image-webpack-loader',
query: {
mozjpeg: {
progressive: false,
quality: 80,
revert: true,
fastcrush: true,
notrellis: true,
notrellisDC: true,
noovershoot: true
},
gifsicle: {
interlaced: false,
},
optipng: {
optimizationLevel: 7,
},
pngquant: {
quality: '75-90',
speed: 4,
}
}
}
Hey. While waiting for #115, you can use 3.4.0 with the workaround. Answer has been given in previous answers
Fixed with 3.4.2
If you have the webp.enabled=false
hack, make sure you remove it when upgrading to 3.4.2.
Hey guys using webp: {quality: 80}
didn't create new versions of my files like I thought it would. Is there additional configuration I'm missing?
Hey @MikaAK, following the docs of imagemin-webp, I can't see how you could configure it to create new files instead of doing the optimization in place. I would be interested if you figure out how to do it though!
because it cancels workaround when adding
webp: { enabled: false }
to options fixes the problem. You can look intoindex.js
form line 77 to line 81 to make sure that webp transformation is now always on.