Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(next/image): prefer sharp defaults, use mozjpeg for JPEG #65846

Merged
merged 1 commit into from
May 20, 2024
Merged

fix(next/image): prefer sharp defaults, use mozjpeg for JPEG #65846

merged 1 commit into from
May 20, 2024

Commits on May 18, 2024

  1. fix(next/image): prefer sharp defaults, use mozjpeg for JPEG 

    - Upgrades sharp to latest v0.33.4

- Use default concurrency detection instead of os.cpus() as it
inspects things like CPU set/affinity as well as the memory
allocator.

- Prevents use of chroma subsampling for AVIF output, instead
slightly reducing relative quality. This should improve the
appearance of red/orange edges and reduce file size as AV1
chroma-from-luma prediction will work better.

- There's no need to set sequentialRead as sharp now manages this
for each input image and the operations in the pipeline.

- Defaults JPEG output to use mozjpeg features such as trellis
quantisation as these produce smaller file sizes. This should
produce consistent output with squoosh at the same quality.
    @lovell
    lovell committed May 18, 2024
    Configuration menu
    Copy the full SHA
    e531a96 View commit details
    Browse the repository at this point in the history