782b7e48ec
This adds a warning when `next export` and custom routes are defined outside of a platform that supports them since they won't be applied anymore.
19 lines
1 KiB
Markdown
19 lines
1 KiB
Markdown
# `next export` No Custom Routes
|
|
|
|
#### Why This Error Occurred
|
|
|
|
In your `next.config.js` `rewrites`, `redirects`, or `headers` were defined while `next export` was being run outside of a platform that supports them.
|
|
|
|
These configs do not apply when exporting your Next.js application manually.
|
|
|
|
#### Possible Ways to Fix It
|
|
|
|
Disable the `rewrites`, `redirects`, and `headers` from your `next.config.js` when using `next export` to deploy your application or deploy your application using [a method](https://nextjs.org/docs/deployment#vercel-recommended) that supports these configs.
|
|
|
|
### Useful Links
|
|
|
|
- [Deployment Documentation](https://nextjs.org/docs/deployment#vercel-recommended)
|
|
- [`next export` Documentation](https://nextjs.org/docs/advanced-features/static-html-export)
|
|
- [Rewrites Documentation](https://nextjs.org/docs/api-reference/next.config.js/rewrites)
|
|
- [Redirects Documentation](https://nextjs.org/docs/api-reference/next.config.js/redirects)
|
|
- [Headers Documentation](https://nextjs.org/docs/api-reference/next.config.js/headers)
|