Image srcset size widths not generated at all

[apfelbox]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:38:37 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.12.1
      npm: 8.19.2
      Yarn: N/A
      pnpm: 8.0.0
    Relevant packages:
      next: 13.2.5-canary.20
      eslint-config-next: 13.2.4
      react: 18.2.0
      react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

Image optimization (next/image, next/legacy/image)

Link to the code that reproduces this issue

—

To Reproduce

We are using the image component with a custom loader. However for regular images, there are no image sizes generated anymore.

Only the 1x and 2x sizes are generated, however no screen width based ones.

Describe the Bug

We use the image like this:

const image = {
    src: "...",
    width: ...,
    height: ...,
};

<Image src={image} alt={alt} />

But now it just generates an image with srcset 1x and 2x and doesn't use the image sizes at all. This way we use the image with 4000px width even on mobile devices.

Expected Behavior

It should always generate the different width-sizes as well, to avoid loading huge sizes on mobile.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[styfle]

The 1x/2x is the default behavior for fixed width images.

If you are using responsive images, you need to set the sizes prop.

[styfle]

Closing since responsive image usage was documented in PR #51457.

See the rendered documentation here: https://nextjs.org/docs/app/building-your-application/optimizing/images#responsive

[apfelbox]

Perfect, thank you (esp for the direct docs link) 👍

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.