Menu

How to Catch Broken Mobile Layouts, Silent 500 API Errors, and AI UI Slop in React, Next.js & Vite Apps
📰

How to Catch Broken Mobile Layouts, Silent 500 API Errors, and AI UI Slop in React, Next.js & Vite Apps

DEV Community: react·VibeFoundry·1 day ago
#NtKW9EZz
#devtoreact#devto#dev#unslop#ghost
Reading 0:00
15s threshold

Passing npm run build and tsc --noEmit only proves your TypeScript syntax compiled. When an AI coding agent builds a frontend feature, the bugs that actually break production happen at runtime in the browser, in the CSS cascade, and in exposed API routes.

To give both human developers and coding agents (Claude Code, Cursor, Windsurf, Copilot) a deterministic verification loop, I built three open-source TypeScript CLI and MCP tools that run locally in seconds.

Step 1: Catch Runtime Browser Failures Across 3 Viewports with ghost-qa

When you run:

npx -y ghost-qa test http://localhost:3000

Enter fullscreen mode

Exit fullscreen mode

ghost-qa ( https://github.com/avivgerz-hue/ghost-qa ) launches headless Playwright against your live dev server ( localhost:3000 or localhost:5173 ), crawls your routes across Desktop ( 1440x900 ) , Tablet ( 768x1024 ) , and Mobile ( 375x812 ) , and inspects 8 runtime traps :

Console & Uncaught Page Exceptions: Hydration mismatches, undefined property reads, and runtime…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.