The current webp library used in the imaging module (sejda fork) is still not supporting aarch64 architecture. This makes m1 owner life a bit miserable when having to troubleshoot issues on modules using the webp format like dam focal.
usefulness fork has added m1 support. I tested it with dam focal on my machine and it seems to work well. The only issue is that if we define this library in dam focal module, the sejda one is still embedded from the imaging module making kind of collision, the only way to exclude the sejda one then is to add a dependency exclusion in the web app, which is not ideal.
Would it be possible to test that dependency ensuring there are no other issues with it and eventually switch to this new one ?