✨ Feat: Added support for WEBP and AVIF formats #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Como te comenté en el streaming, añadir soporte para los formatos de WEBP y AV1 (AVIF) es muy sencillo gracias al elemento picture de HTML.
Lo ideal por sus características sería usar el formato AVIF, gracias a sus ventajas. Pero desgraciadamente su soporte todavía no es el ideal, he incluso necesesita aplicar pequeñas modificaciones para que funcione en Cloudinary y Netlify (ver sección AVIF Content-Type Headers + Netlify). Aún así, sus ventajas son claras y sus desventajas solo temporales.
Como alternativa a la incompatibilidad con el formato AVIF, tenemos a disposición el formato WEBP con una compatibilidad casi plena, lo que nos permite crear un fallback de calidad al futuro (inminente) de compatibilidad con AVIF.
Y como último recurso, en caso de una mala compatibilidad del navegador (no miro a nadie Internet Explorer, y Safari 👀😑), tenemos la carga del clásico JPG.