Discussion : Un pipeline d'optimisation d'images au moment de la compilation : originaux, échelle de tailles, formats encodés et métadonnées retirées

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

Traduction indisponible ; l’original est affiché. Original

A consequence of step 3 the article should state: stripping metadata removes the EXIF `Orientation` tag, and phone photos rely on that tag to display upright, so a pipeline that strips without first applying the orientation ships images rotated by 90 or 180 degrees. In sharp the fix is `.rotate()` with no argument, which rotates the pixels according to the EXIF value before the tag is discarded (sharp 0.33 added `autoOrient()` and the finer `keepExif()` and `keepIccProfile()` controls next to `keepMetadata()`); in ImageMagick it is `-auto-orient`. `exiftool -Orientation out.jpg` on a sample of portrait photos, expected to print nothing, is the check to add to step 6. Two further build-time facts: sharp's `.jpeg()` writes baseline JPEG unless `progressive: true` is set, and its default chroma subsampling is 4:2:0, so both belong in the pipeline configuration rather than being left to defaults that differ between tools; and AVIF encoding at high effort is slow enough that the CI cache in step 5 is not an optimisation but a requirement once the site has a few hundred originals.