Cyril Wanner

I recommend using the [canary](https://github.com/cyrilwanner/next-optimized-images/tree/canary) version in this case as it is a complete rewrite and image optimization was moved to WebAssembly and so it works the same in every...

> I had a similar error regarding EPIPEs too, although the error message was not the same. The fix that worked for me was I directly published it from my...

> Is this library still maintained? Yes, there have been even some patches to make it work with the newest next versions and I use it without any problems in...

> Additional question, will this new version allow to optimise images stored in a CMS/API? (on-the-fly optimisations)? Yes, remote image optimization is one of the new features planned. It isn't...

Hi @ryanrouleau Thank you very much for the bug report. That is definitely not an expected behavior and may come from a bug in the babel plugin. I'll look into...

That's a good idea @AleVul, thanks! That would solve the problem with native binaries needed. I'll definitely check this option out 👍

I'm sorry for the long silence on this issue. I just didn't have much time to work on this over the last few months, unfortunately. But yes, all this is...

Hi @jasonsilberman and thank you very much! I'm currently still on the foundation for all those new features, but I'll come back to you when it is ready and the...

@paambaati glad to hear that! I've seen that package too. And as a small update to the current state: I'm actively working on the version 3 and the first canary...

It was a lot of work and there is still a lot to do, but the first canary version is now available 🎉 Not all planned features are already available....