Where Does Nextra Store Config and Output?
Nextra theme config, pages and .next cache inside your docs project on each OS.
Last updated
Nextra is a Next.js docs layer, so config lives beside pages in the project. theme.config.* controls nav, pages hold MDX, and build output lands in .next plus out when exporting.
There is no global config. The project folder is portable. Cache issues clear by deleting .next. Hosts serve either the Node app or the static export.
Where Nextra stores this, by platform
[SiteDir]\theme.config.jsx
Theme config at root with next.config.js and pages under [SiteDir]\pages\. Delete [SiteDir]\.next to fix stale builds. Keep configs and pages in git.
[SiteDir]/theme.config.jsx
Same layout. Exact theme file may be .tsx or .js by version. Node modules stay under the project root. Fresh install reproduces the site.
[SiteDir]/theme.config.jsx
Same arrangement. CI typically runs next build then serves .next or exports to out. Exclude node_modules and .next from version control.
Frequently asked questions
Where is Nextra build output?
In .next after next build, or out after next export for static hosts. Both are disposable. Source is theme config, next config and pages.
My Nextra sidebar looks stale. What do I delete?
Delete .next and rebuild. Cached routes go stale in confusing ways. The framework recreates output cleanly on the next run.
Notice an outdated path? Let us know.