Steven

[image-optimizer] Refactor into lightweight transform module (#97988) This PR is strictly a refactor, no logic should change. The idea is that we eventually want to run the image optimizer transform step in a child process. This PR refactors the code to make a new `transform.ts` that is lightweight and should reduce some of the overhead of loading a large module graph when spawning a new process.

feat(next/image): Add experimental imgOptMozjpeg config (#98571) In a previous PR, `mozjpeg` was set to true which might be the reason output jpeg spikes cpu. - https://github.com/vercel/next.js/pull/65846 I made a benchmark and found that disabling MozJPEG saved 72% CPU, with average outputs 31% larger. - https://github.com/lovell/sharp/issues/4603 So this PR adds a new experimental flag to enable (or rather disable) mozjpeg and try with real workloads. This is useful becaues in many cases, cpu is more costly than bandwidth since most CDNs provide [near unlimited bandwidth](https://vercel.com/blog/introducing-flat-rate-cdn).

fix(next/image): improve test coverage for unsupported image types (#96301) We were missing some test coverage for image optimization. This PR adds tests for many missing image formats. Additionally, this PR also ensures the sharp encoders match that allowlist from detectContentType() such that future versions of sharp that enable new encoders by default are not automatically enabled in next/image. Practically, there is no change to the end user because detectContentType() runs before sharp so that is the true allowlist, but this gives us a little more control to align the sharp allowlist as well (since sharp can release new features in semver minor).

chore(deps): bump sharp@0.35.3 (#95507) ## Notable changes - No more install script needed - No more dynamic require/import tracing workaround - AVIF uses [tune iq](https://aomedia.org/blog%20posts/Libavif_v1_4_0-Boasts-Major-Updates-to-Encoder-Technology/#the-tune-iq-image-quality-tuning-mode) to better match human perception ## All changes - https://github.com/lovell/sharp/releases/tag/v0.35.0 - https://github.com/lovell/sharp/releases/tag/v0.35.1 - https://github.com/lovell/sharp/releases/tag/v0.35.2 - https://github.com/lovell/sharp/releases/tag/v0.35.3 --------- Co-authored-by: Sebastian Sebbie Silbermann <sebastian.silbermann@vercel.com>

fix(next/image): reject empty image on read/write to disk cache (#97278)

chore: remove unused code from image optimizer (#98060) This PR removes some unused code from the image optimizer. - Remove redundant MIME validation - Remove unreachable fallback error These used to be necessary until PR https://github.com/vercel/next.js/pull/82118 removed the fallback. Before 82118: ```js upstreamType = detectContentType(upstreamBuffer) || imageUpstream.contentType?.toLowerCase().trim() ``` After 82118: ```js upstreamType = detectContentType(upstreamBuffer) ``` Now there is never a case where upstreamType is invalid since its already been validated, there is no more fallback.

test: add test for local font with deployment id (#97987) Follow up to a previous PR: - https://github.com/vercel/next.js/pull/82488 - https://github.com/vercel/next.js/pull/82384 Closes: - https://github.com/vercel/next.js/pull/82547

fix(create-next-app): make AGENTS.md blue (#95432) I noticed that this last question for AGENTS.md doesn't have any blue highlighted word. So I made AGENTS.md blue to follow the convention of the others. <img width="865" height="163" alt="image" src="https://github.com/user-attachments/assets/d10f74e1-f5ec-4c8a-9c6d-8d01b9c1abf3" /> --------- Co-authored-by: Joseph <joseph.chamochumbi@vercel.com>

fix(deps): bump `satori` and `@vercel/og` (#97276)