An independent review tool for Nuxt 4 developers - not affiliated with Nuxt or NuxtLabs
Nuxt ClinicThe same HTML on the server and the client, one fetch instead of two, and the right route rule.
Paste a page or component, the route it serves and what kind of page it is. Free in your browser: everything that makes the server HTML and the hydrated page differ - Date.now() in the first render, localStorage during SSR, useRoute from vue-router - plus data fetched twice or without a key, lazy data with no loading state, plain <a> links, and which route rule serves the page: never ssr: false on a page that needs SEO, never a shared cache on a signed-in page. A run writes the review, or fixes the page; the page re-scans the fix.
1 Your page free
2 The scan free
Against the rules of the Nuxt 4 skill, for the kind of page above. Nothing leaves your browser for this part.
Where the problems are
The route rule that serves this page
Findings
3 The review or the fix metered
The reply, as it came
Findings
The scan's calls
Caveats
Changes
Kept on purpose
Diff
The fixed file
Caveats
Route rule
Checked against the scan
Saved pages
How it works
The scan reads the .vue file with comments ignored and applies the rules of the nuxt4-patterns skill. It tells render time from event time: Date.now() inside onMounted, a click handler or if (import.meta.client) is fine; at the top of <script setup>, in a computed or in the template it makes the server HTML and the hydrated page differ. It reads your routeRules, finds the entry that serves the route (the most specific pattern wins), and checks it against the kind of page: server HTML for anything that needs SEO, no shared cache for anything personalised.
The review and the fix are written by a language model from your code and the scan's facts. The page holds the reply to the scan: every error and warning must be answered by rule id; a fixed file is re-scanned here, and a prop, emit or exposed name that disappeared is named; the route rule the model proposes must match the route and pass the same SEO and shared-cache checks. Nothing is run; compare the server HTML with nuxi dev.