docs: papercuts in image API reference (#99256)
- The `sizes` section didn't explain what happens to `fill` images without `sizes`. Only images with a `width` get the limited `1x`/`2x` `srcset` - `fill` images get one built from `deviceSizes`. - Updated `deviceSizes` to match: it's also used for `fill` images without `sizes`. - "Forever" isn't an accurate description of static image import caching. The built-in image optimizer serves these with `public, max-age=315360000, immutable`, which is 10 years ([source](https://github.com/vercel/next.js/blob/aea417ab0c490ec3e07112ed48ba20236fdfad18/packages/next/src/server/image-optimizer.ts#L305-L309), [header](https://github.com/vercel/next.js/blob/aea417ab0c490ec3e07112ed48ba20236fdfad18/packages/next/src/server/image-optimizer.ts#L831)). - Changed to "long-lived `immutable`" in the image and `legacy` image references.
Showing
Please
register
or
sign in
to comment