b7d057453d
In a previous PR (#19032), we added a hard error during `next export` if the default Image Optimization API is being used because it requires a server to optimized on demand. The error message offers several different solutions but it didn't consider that by the time someone runs `next export`, they are probably done writing their app. So if `next export` is a hard requirement, the quickest path forward is to disable Image Optimization API. So this PR adds a new configuration option to `next.config.js`: ```js module.exports = { images: { unoptimized: true } } ``` ### Update Upon further discussion, we might want to avoid doing this just for images and instead introduce a top-level config to indicate export is coming and then handle errors or warn for [unsupported features](https://nextjs.org/docs/advanced-features/static-html-export#unsupported-features). ``` module.exports = { nextExport: true } ``` Co-authored-by: JJ Kasper <22380829+ijjk@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| advanced-features | ||
| api-reference | ||
| api-routes | ||
| basic-features | ||
| guides | ||
| migrating | ||
| routing | ||
| authentication.md | ||
| deployment.md | ||
| faq.md | ||
| getting-started.md | ||
| going-to-production.md | ||
| manifest.json | ||
| testing.md | ||
| upgrading.md | ||