rsnext/test/integration/image-future
Steven cdb0c47455
Improve next/image error message when src prop is missing (#38847)
Currently, when a user forgets the `src` prop on an image, an error is thrown. However that error doesn't include any of the the user's code in the stack trace, so its nearly impossible to figure out which image is the culprit if there are multiple images on the page.

Since this error only throws on demand when a page is visited during `next dev`, we can instead delay the error so it no longer prints on the server but prints on mount instead. At that point, we'll have the `<img>` element via ref and can print it to the web console with the stack trace.

- Fixes #23742
2022-07-20 21:26:38 +00:00
..
asset-prefix Add experimental next/future/image component (#37927) 2022-06-24 14:56:05 +00:00
base-path Improve next/image error message when src prop is missing (#38847) 2022-07-20 21:26:38 +00:00
default Improve next/image error message when src prop is missing (#38847) 2022-07-20 21:26:38 +00:00
image-from-node-modules Add experimental next/future/image component (#37927) 2022-06-24 14:56:05 +00:00
noscript Remove unnecessary <noscript> from next/future/image (#38080) 2022-06-28 00:58:50 +00:00
react-virtualized Add experimental next/future/image component (#37927) 2022-06-24 14:56:05 +00:00
svgo-webpack Add experimental next/future/image component (#37927) 2022-06-24 14:56:05 +00:00
trailing-slash Add experimental next/future/image component (#37927) 2022-06-24 14:56:05 +00:00
typescript Replace placeholder.com images with *.vercel.app in image-component tests (#38090) 2022-06-30 21:10:16 +00:00
unicode Add experimental next/future/image component (#37927) 2022-06-24 14:56:05 +00:00
unoptimized Update image tests from placeholder.com to *.vercel.app (#38081) 2022-06-28 01:20:59 +00:00