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
jpeg-XL is a cutting-edge new image codec that is faster, better at lossy compression than any other image codec and has faster image decompression. Webp is unreliable and jpeg can have a lot of artifacts
So why is jpeg-xl not supported? maybe because it isn't supported by chromium, but hey. If docosaurus supports jpeg-xl before chromium does again, it will be already implemented.
Self-service
I'd be willing to do some initial work on this proposal myself.
The text was updated successfully, but these errors were encountered:
What does it mean for Docusaurus to support jpegxl according to you?
What prevents you from implementing a Docusaurus plugin to add this support on your own?
The goal of Docusaurus is not to support everything out of the box: we rely on the community and our plugin ecosystem for that and only include the most common, well-supported things in the core repo/packages. If something is not supported in all browsers yet, it's unlikely we encourage usage of it by creating something custom to support it.
We use Webpack image loader to allow require("./img.png") syntax:
Have you read the Contributing Guidelines on issues?
Motivation
jpeg-XL is a cutting-edge new image codec that is faster, better at lossy compression than any other image codec and has faster image decompression. Webp is unreliable and jpeg can have a lot of artifacts
So why is jpeg-xl not supported? maybe because it isn't supported by chromium, but hey. If docosaurus supports jpeg-xl before chromium does again, it will be already implemented.
Self-service
The text was updated successfully, but these errors were encountered: