bug in canary version #174
Comments
|
Hi @tilman |
|
OS: macOS Catalina v10.15.1 Unfortunatily it's closed source. But we just use next optimized images in a standard config with the new Img component: ex: images.config.js module.exports = {
default: {
webp: true,
sizes: [200, 400, 700, 1000],
densities: [1, 2],
},
types: {
thumbnail: {
sizes: [200, 400],
webp: false,
},
},
}; |
|
Thank you! I found and fixed a bug related to the cache in (After updating, it is expected for all images to re-compile once) |
|
Great, thanks for the quick help! With the new version everything works as it should :) |
Hey, every time I restart the build (with
npm run dev) the cache seems to be invalidated and I have to wait again 5 Minutes for the compile phase to be finished.I took a look at the cache folder and it seems like the IDs of the images are staying the same but the content of the previously optimized images is nulled at each beginning. Is there a reason for that or is it just a bug?
This is the content after I removed the .cache folder and let it run for the first time:
This is the content after I restarted
npm run devduring the compile phase, as you can see many images have still 0Byte even if the have been there in the cache previously.The text was updated successfully, but these errors were encountered: