Images with @2x or @3x in their file names are not resolved (breaks static image resources) about metro

[jasperkuperus]

@jeanlauliac Is it an idea to add a better error if someone does use @2x and then refer to this issue?

[jeanlauliac]

Yes, a specific error message sounds good to me. I would not refer to this issue though, I'd just mention that removing the scale specifier solves the problem.

[cpojer]

@jeanlauliac knows about assets.

[jeanlauliac]

Sorry I've been lagging behind quite a lot.

About this issue: in Metro, assets are not meant to be required with a specific scale, since different devices might use different scales. In that example, requiring ./myImage.png would cause either [email protected] or [email protected] to be used depending on the device screen pixel ratio (virtual-pixel to physical-pixel ratio, so to speak).

@mo-solnet can you explain what is the benefit of using require('../[email protected]') over require('../myImage.png')?

[jeanlauliac]

I haven't got the time to try to fit a hint message somewhere in the stack, but I'll close this issue for now, as this is the expected behaviour, and scale specifiers should not be included in the name when requiring assets. Do feel free to send a PR to tweak error messages however.

The documentation mentions having different densities and does have the example without the density specifier, so I don't think it needs updating? (https://facebook.github.io/react-native/docs/images.html#static-image-resources)