Repository navigation
[15.5.x] Re-enable AVIF image optimization with a runtime libheif version guard - #97954
Conversation
Failing test suitesCommit: ac65ec4 | About building and testing Next.js
Expand output● PPR - partial hydration › Static shell, no streaming metadata › should hydrate the shell without waiting for slow suspense boundaries ● PPR - partial hydration › Static shell, streaming metadata › should hydrate the shell without waiting for slow suspense boundaries |
890bb4e to
587c966
Compare
77ae312 to
f0415c2
Compare
ac7eb17 to
8448b01
Compare
76da755 to
28f8c95
Compare
| it('should bypass optimization for avif input', async () => { | ||
| const query = { url: '/test.avif', w: ctx.w, q: ctx.q } | ||
| it('should resize avif', async () => { | ||
| const query = { url: '/test.avif', w: ctx.w, q: 75 } |
There was a problem hiding this comment.
Removed the hardcoding which got reintroduced by reverting. It was hardcoded before we disabled AVIF.
| it('should bypass avif input when avif output is enabled', async () => { | ||
| const query = { url: '/test.avif', w: ctx.w, q: ctx.q } | ||
| it('should resize avif and maintain format', async () => { | ||
| const query = { url: '/test.avif', w: ctx.w, q: 75 } |
There was a problem hiding this comment.
Same question - Do we need to hardcode q here?
There was a problem hiding this comment.
Removed the hardcoding which got reintroduced by reverting. It was hardcoded before we disabled AVIF.
28f8c95 to
ac65ec4
Compare
|
Flaky test. Force-merging. |
Backports #97931
Part of https://linear.app/vercel/issue/VOC-34654/
Since 15.x supports a Node.js version not supported by a secure sharp version, we have to conditionally block AVIF optimization based on the used libheif version. I added a test that runs for each support major sharp version to validate only the fixed version optimizes AVIF.