archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
rsnext/errors/next-image-missing-loader.md
Steven 1a8ad14089
Rename next/image dangerously-unoptimized to custom and warn when applicable (#26998) 
Since we are no longer accepting new built-in loaders, users may wish to use a different cloud provider.

So this PR renames `dangerously-unoptimized` to `custom` to handle this case as well as the intention of `next export`.

If the user doesn't add a `loader` prop, we throw an error.
If the user adds a `loader` prop but it doesn't return the width, we print a warning.

- Follow up to #26847 
- Fixes #21079 
- Fixes #19612 
- Related to #26850
2021-07-08 19:35:19 +00:00

845 B
Raw Blame History

Missing loader Prop on next/image

Why This Error Occurred

When using the next/image component with loader="custom" in next.config.js, you must provide the loader prop to the component with your custom implementation.

Possible Ways to Fix It

  • Add the loader prop to all usages of the next/image component.
  • Change the loader configuration in next.config.js.

Useful Links