gatsby-plugin-image and device pixel ratio

[cameronmcefee]

I feel like I'm going to feel ridiculous once I learn the answer, but how does gatsby-plugin-image work with device pixel ratio? Say I have a constrained 1000 x 500px image, which would need a 2000 x 1000px source to look crisp at the largest size. And for the sake of argument, the default max width is set to 1000px. The docs say this of the outputPixelDensities option:

For constrained: [0.25, 0.5, 1, 2]
A list of image pixel densities to generate. It will never generate images larger than the source, and will always include a 1x image. The value is multiplied by the image width, to give the generated sizes. For example, a 400 px wide constrained image would generate 100, 200, 400 and 800 px wide images by default. Ignored for full width layout images, which use breakpoints instead.

Based on that, for my example, I would expect to see image sizes that would be something like [250, 500, 1000, 2000], but what it seems to create is [125, 250, 500, 1000].

Similarly, if I switch my image to layout: "fullWidth", the image that is created — based on the default max width — is 1000px x 500px, not 2000px x 1000px like I'd expect since the defaults generally claim to account for high density displays.

To get around this, I can set width="2000" on the image, but since fullWidth layouts don't use width and thus still render the image for 1x, I feel like this is not the right answer.

Is this a bug that has somehow gone unnoticed (unlikely) or am I misunderstanding how this works?

Thanks for your insight.

[cameronmcefee]

As is the case with such things, I think this is pebkac. The file that was being referenced was not the one I thought it was, and the actual file being referenced was much smaller. While I still feel like things aren't exactly straightforward, I'm pretty sure this is just a me problem.