Fix the app that works on my Mac but breaks live | Vovy
Vovy compares your local setup with production side by side: env variables, build output, URLs and Node version, and finds the difference that breaks it.
Everything works on localhost but it's broken on my live site
How it works
- Run a production build locally: Vovy runs npm run build and then starts the built app, because npm run dev hides problems that only appear in a real build.
- Compare environment variables: It lists the keys in your .env file next to the ones in Vercel's Environment Variables, without showing values, and flags anything missing in Production.
- Hunt for hardcoded localhost: Cursor searches your code for localhost:3000 and http:// links, and checks auth redirect URLs that still point at your Mac.
- Check Node and case-sensitive paths: It compares your local Node version with Vercel's setting and checks imports like ./Header vs header.tsx, which macOS forgives and Linux servers do not.
- Show the difference that matters: You get a comparison table, local vs production, with the mismatch highlighted and the fix ready to apply.
What you provide
- Your project on your Mac
- Access to your Vercel project
What you get
- Local vs production comparison table
- Missing env variables flagged
- Hardcoded URLs found
- A fix for the real cause
FAQ
I added the env variable in Vercel and it still fails. Why?
Env changes only apply to new deployments. Redeploy after adding or editing a variable.
Will Vovy show my secret keys?
No. It compares variable names only and never prints values on screen.
What if it's a database difference?
Many apps use a different Supabase project locally. Vovy checks which project URL each environment points to.
Related tasks
All tasksLoading...