Files
next.js/errors/next-image-missing-loader.mdx
T
Delba de OliveiraandGitHub 0b35ddd825 Docs: Move next.config.js API pages under a config folder, fix headings in TS and ESLint config pages (#72465)
This PR:

- Moves `next.config.js` options under a "config" folder which includes
references for other configuration such as the ESLint plugin. I figure
it would be tidier than having "Next.config.js Options" and "Config" in
the API reference.
- Fixes the issue with the "config" folder not showing up in canary:
https://linear.app/vercel/issue/DOC-3749/bug-figure-out-why-new-config-folder-isnt-showing-up-in-the-canary
- Fixes the indentation issues and missing example header (caused by an
invisible character).

Redirects: https://github.com/vercel/front/pull/38704
2024-11-08 14:48:55 +00:00

18 lines
811 B
Plaintext

---
title: 'Missing `loader` Prop on `next/image`'
---
## Why This Error Occurred
When using the `next/image` component with [`loader="custom"`](/docs/app/api-reference/config/next-config-js/images) in `next.config.js`, you must provide the [`loader`](/docs/pages/api-reference/components/image#loader) prop to the component with your custom implementation.
## Possible Ways to Fix It
- Add the [`loader`](/docs/pages/api-reference/components/image#loader) prop to all usages of the `next/image` component.
- Change the [`loader`](/docs/app/api-reference/config/next-config-js/images) configuration in `next.config.js`.
## Useful Links
- [Image Optimization Documentation](/docs/pages/building-your-application/optimizing/images)
- [`next/image` Documentation](/docs/pages/api-reference/components/image)