Which command produces the static build?

`npx nuxt generate` prerenders every route into `.output/public`. Upload that directory: the entry `index.html` becomes the report body and the assets upload alongside.

Do hydrated Vue components still work at the link?

Yes. The prerendered HTML hydrates client-side and scripts run inside a sandboxed iframe, so menus, tabs and client-side routing between prerendered pages behave normally.

Why not deploy a preview?

Deploy one when you have somewhere to deploy to. This covers the cases where you do not, or where the preview should be behind a password rather than on a public URL a client could forward.

How do I keep one link across rebuilds?

PATCH the same report id after each `nuxt generate`. The reviewer's URL shows the current build, earlier builds stay as revisions, and the comment threads carry over.

Share a Nuxt static site preview

nuxt generate takes about as long as it takes to read this sentence, and produces a complete prerendered site in .output/public. Then the review stalls on logistics: a bucket, a preview environment, or "run it locally and I'll screen-share".

Publish the build

npx nuxt generate

Drag .output/public/ (or a zip of it) into the app:

index.html becomes the report body.
CSS, JS, fonts and images upload as assets with their references rewritten to the uploaded copies — which is what makes the difference between a rendered preview and a page with no styles.
Scripts run inside a sandboxed iframe, so hydration, the nav menu and client-side routing between prerendered pages all work.

Keep app.baseURL at its default for a preview build; a base URL points at a deployment that does not exist yet.

What is not in a static build

Nitro server routes and any server-side runtime behaviour are not part of nuxt generate output. Client-side fetches to an external API still run from the reviewer's browser, subject to that API being reachable and CORS-permissive. For a content and design review — the usual reason for a preview — neither is a blocker.

Private by default

Every report is private until you change it: team, email-domain gate, named reviewers, or a password-protected link for a client. See the sharing model. Pre-launch pages should not be sitting on a URL someone can forward by accident.

Feedback lands on the page

Anchored threads on the specific heading, image, or price — see commenting on HTML.
Revisions. PATCH the same report id and the reviewer sees the new build at the URL they already have, with the old one still readable.
An agent can read the comments back through MCP.

Limits

Entry HTML: 5 MB. Assets: 25 MB per file, 250 MB and 500 files total — a content site with a page per tag plus per-route payloads can exceed 500 files. Generate a subset for review when it does.
60 requests/minute per token.

Try it

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

Create your first report →