Files
next.js/errors/sharp-missing-in-production.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

48 lines
1.9 KiB
Plaintext

---
title: Sharp Missing In Production
---
## Why This Error Occurred
The `next/image` component's default loader uses [`squoosh`](https://www.npmjs.com/package/@squoosh/lib) because it is quick to install and suitable for a development environment.
- For a production environment using `next start`, it is strongly recommended you install [`sharp`](https://www.npmjs.com/package/sharp).
You are seeing this error because Image Optimization in production mode (`next start`) was detected.
- For a production environment using `output: "standalone"`, you must install [`sharp`](https://www.npmjs.com/package/sharp).
You are seeing this error because Image Optimization in standalone mode (`output: "standalone"`) was detected.
## Possible Ways to Fix It
- Install `sharp` by running one of the following commands in your project directory:
```bash filename="Terminal"
npm i sharp
```
```bash filename="Terminal"
yarn add sharp
```
```bash filename="Terminal"
pnpm add sharp
```
```bash filename="Terminal"
bun add sharp
```
Then, build your project with `next build`. Finally, restart the server with either `next start` for production mode or `node .next/standalone/server.js` for standalone mode.
- If `sharp` is already installed but can't be resolved, set the `NEXT_SHARP_PATH` environment variable such as `export NEXT_SHARP_PATH=/tmp/node_modules/sharp`. Then, build your project with `next build`. Finally, restart the server with either `next start` for production mode or `node .next/standalone/server.js` for standalone mode.
> Note: This is not necessary for Vercel deployments, since `sharp` is installed automatically for you.
## Useful Links
- [Image Optimization Documentation](/docs/pages/building-your-application/optimizing/images)
- [`next/image` Documentation](/docs/pages/api-reference/components/image)
- [Output File Tracing](/docs/pages/api-reference/config/next-config-js/output)