Files
next.js/errors/empty-configuration.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

22 lines
438 B
Plaintext

---
title: 'Detected `next.config.js`, no exported configuration found'
---
## Why This Warning Occurred
There is no object exported from next.config.js or the object is empty.
## Possible Ways to Fix It
Check if you correctly export configuration in `next.config.js` file:
```
module.exports = {
/* config options here */
}
```
## Useful Links
- [Introduction to next.config.js](/docs/pages/api-reference/config/next-config-js)