ShipReady rates this medium. Fix soon. Meaningfully weakens a defence or degrades how the site works.

Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.

Can I check my own site?

Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check. The free report lists every issue it finds and shows full evidence and a fix prompt for the critical and high-severity ones; medium and low findings are counted and unlock on Pro.

All checks

Production Readinessmediumdevelopment-build-in-productionchecked on every page we scan

A development build is being served to real visitors

"A development build is being served to real visitors" is a medium-severity production readiness finding ShipReady reports when it observes the condition directly on your site. Fix soon. Meaningfully weakens a defence or degrades how the site works.

How ShipReady detects it

Launch signals carried by a PAGE's own markup: basic metadata, and a default framework title left in place. Genuinely per-page - a polished homepage routinely hides a /pricing that still says "Create Next App", which is exactly the defect this catches. Reads only the already-fetched HTML and issues no requests of its own.

Detection is deterministic. ShipReady reports this only when it observes the condition directly, and prefers to miss a real problem over inventing one. Rule version 1.10.0.

How to fix it

This is the prompt ShipReady puts in your report — written to be pasted straight into Cursor, Claude Code, or whichever assistant built the app.

Your live site is serving a development build — the scan found a test-mode key. Development builds are several times larger, run slower because every framework debug check and warning is retained, and expose component names and internal state that a production build strips. Fix the deploy, not the code: make sure your host runs the production build command (`next build` then `next start`, `vite build`, `ng build --configuration production`) rather than the dev server, and that NODE_ENV is set to production in the deployed environment — a platform that runs `npm run dev` because that is the default start script is the single most common cause. If you use a Dockerfile, check it is not copying a dev-time node_modules or running the dev entrypoint. Redeploy, then confirm the marker is gone from the served JavaScript and that no /@vite/client or hot-reload script remains in the HTML.

Frequently asked questions

What does "A development build is being served to real visitors" mean?: "A development build is being served to real visitors" is a medium-severity production readiness finding ShipReady reports when it observes the condition directly on your site. Fix soon. Meaningfully weakens a defence or degrades how the site works.
How serious is it?: ShipReady rates this medium. Fix soon. Meaningfully weakens a defence or degrades how the site works.
How do I fix it?: Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.
Can I check my own site?: Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check. The free report lists every issue it finds and shows full evidence and a fix prompt for the critical and high-severity ones; medium and low findings are counted and unlock on Pro.

Related checks

Run this check on your site

ShipReady checks this and 193 other things across up to ten pages of your site, with an AI-ready fix for each. Free, no signup.

Scan your site free View pricing