How do I get a static build out of Nextra?

Set `output: 'export'` in `next.config.mjs` and run `next build`. Nextra is a Next.js app, so the export writes a self-hosting `out/` directory.

Does Nextra's search work after a static export?

Yes — Nextra builds its FlexSearch index at build time into the exported assets, so search resolves from the same origin as the pages.

Why does out/index.html look unstyled when opened directly?

Next.js references its chunks absolutely under `/_next/`, which resolves against your filesystem root at a `file://` origin. Publishing the folder over HTTP fixes it.

Can each branch have a stable preview URL?

PATCH one report id per branch on every push. The URL stays put and older builds remain as revisions.

Do dynamic routes survive the export?

Any route that can be statically generated does. Routes that need a server at request time cannot be exported — that is a Next.js constraint, not a publishing one.

Share a Nextra site

Nextra is a docs theme on top of Next.js, which means the preview problem is the Next.js preview problem: next dev is yours alone, and the only other copy is whatever is deployed.

Export

// next.config.mjs
export default { output: "export" };

npx next build
# → out/

Opening out/index.html from the Finder gives you unstyled markup — Next references its chunks absolutely under /_next/…, which at a file:// origin points at your filesystem root. Over HTTP with the folder uploaded, those paths resolve.

Publish out/

Drag the folder into the app, or zip and POST it:

cd out && zip -qr ../site.zip . && cd ..

curl -fsS -X POST https://commareports.com/api/v1/reports \
  -H "Authorization: Bearer $COMMA_API_TOKEN" \
  -F "title=Docs — $(git rev-parse --abbrev-ref HEAD)" \
  -F "visibility=team" \
  -F "bundle=@site.zip"

cd into out before zipping so index.html sits at the archive root — see sharing a folder of HTML files.

What the review link gets you

Anchored threads — copy feedback attaches to the sentence on the rendered page. See commenting on HTML.
Revisions at one URL — one report id per branch; the link in the PR is always current.
Access per report — private, team-only, domain-gated, or unlisted. See the sharing model.
Scripts run, sandboxed — client components hydrate inside a sandboxed iframe, so interactive examples work without touching anyone's session.

Limits

Assets: 25 MB per file, 250 MB and 500 files per report. A large Next export can exceed 500 files; delete source maps (**/*.map) before zipping.
Entry HTML: 5 MB.
60 requests/minute per token.

Try it

Comma is free — unlimited reports, unlimited commenters, unlimited revision history.

Publish a site preview →