Deploy the intended rendering mode
Publish the Node, serverless, edge, prerendered or client-rendered build, then confirm every route included in review opens from its direct URL.
Paste a browser-accessible Nuxt deployment, send one review link, and collect comments on the routes your users will actually open. Every note keeps its page, browser, device and screenshot context.












Loved by1,250+Agenciesand companies in 100+ countries
Nuxt can run as a Node server, target serverless or edge platforms, prerender static output, or run as a client-side application. Its deployment behavior is provided through Nitro and platform presets.
Those modes do not expose identical behavior. Four boundaries matter:
The official command starts a server after a build so you can preview the application locally. It is not itself a durable external client-review deployment.
Nuxt's crawler starts from configured entry pages and follows links. Routes that are not linked must be added explicitly if they need static output and review.
A generated static site can be hosted without a server, but Nuxt documents that server functionality is unavailable in that deployment. Use a server build when the review depends on server routes.
Nuxt uses Nitro presets for Node, serverless, edge and other targets. Validate the application on the actual target because runtime capabilities and configuration differ.
How it works
Publish the Node, serverless, edge, prerendered or client-rendered build, then confirm every route included in review opens from its direct URL.
Paste the deployed URL into BugSmash and share the generated link. Reviewers comment on the rendered application without needing repository or hosting access.
Each item carries the page, selected element, screenshot, browser and device. Assign it, update its status, or send it into the team's delivery tools.
Attach feedback to the interface and route the reviewer sees instead of translating it into component or file names.
Review desktop, tablet and mobile states from one link and keep the viewport with each comment.
Browser, device, screenshot and page URL arrive with every report.
Review generated routes directly and catch pages that were not included by crawling or explicit configuration.
Exercise the deployment mode intended for release, including server-backed routes when they are part of the application.
Preserve the review record independently of later builds, regenerated output or platform changes.
BugSmash reviews a browser-accessible Nuxt frontend. The Nitro preset, rendering mode, host and application access controls determine which routes and server features are available.
| Your URL | Review by URL | What to do |
|---|---|---|
| Public Node server deployment | Works | Paste the deployed URL and review the server-backed application. |
| Public serverless or edge deployment | Works | Use the target-platform URL after confirming the selected Nitro preset supports the application. |
| Public prerendered static site | Works | Use the deployed static URL and confirm every review route was generated. |
| Accessible hosting-provider preview | Works | Paste the preview URL after confirming the reviewer can open it. |
| Local nuxt preview or development server | Not directly | Deploy the build or expose the local server through a secure HTTPS tunnel. |
| Application behind login or SSO | Access-dependent | Use a permitted test account for a standard login flow, or install the BugSmash Feedback Widget for stateful or SSO-only sessions. |
Add the BugSmash script to the browser-facing Nuxt application when reviewers must remain inside authenticated or stateful flows. Install it in the rendered frontend regardless of the Nitro preset or rendering mode.
From prerendered marketing pages to server-rendered applications, keep product, engineering and QA teams aligned on the same deployed release.

Review the complete routed experience and responsive states on the Nuxt deployment stakeholders can open.
See how
Receive visual reports with the route, selected element, browser, device and screenshot already attached.
See how
Validate prerender coverage, runtime behavior and direct route access on the intended deployment target.
See howA comment on the deployed application becomes a task with the route, selected element, screenshot, browser and device context already attached.
Context stays attached from comment to completion.
Send to your workflow
The destination changes. The context does not.
Keep the application, product PDF, walkthrough video, campaign images, launch email and presentation in one review project with one approval trail.

product-launch.mp4
Up to 40% offThis year marked our strongest period of growth to date. Revenue climbed 42% year over year while our customer base expanded across eleven new markets, driven by continued investment in product.

Operational efficiency improved as automated workflows reduced manual review time by nearly a third. Looking ahead, we plan to double down on infrastructure, deepen key partnerships, and ship the roadmap our customers have been asking for.

The nuxt preview command starts a local server after a build. Use a deployed URL for a durable external review, or intentionally expose the local server through a secure HTTPS tunnel.
Paste an accessible Nuxt deployment URL and send the first review link in under a minute.
