FIX BY SYMPTOM
Environment variables missing in production?
Environment variables go missing in production for two reasons: the framework only exposes prefixed variables to the browser (VITE_, NEXT_PUBLIC_), or they were never set in the host's own settings for that environment and followed by a redeploy. Fix the prefix, set the variable on the host, then rebuild. VibePitstop fixes broken production config as a fixed-price deploy fix.
Browser prefixes by framework
| Framework | Browser prefix | When it is read |
|---|---|---|
| Vite (Lovable, Bolt) | VITE_ | Build time |
| Next.js (v0, many Cursor apps) | NEXT_PUBLIC_ | Inlined at build; server-only vars at runtime |
| Create React App | REACT_APP_ | Build time |
| Expo | EXPO_PUBLIC_ | Build time |
Where to set them
- Vercel: Project Settings, Environment Variables, per environment (Production, Preview, Development). Redeploy after changes.
- Netlify: Site configuration, Environment variables, with the right scopes (builds, functions). Trigger a new deploy.
- Cloudflare: build variables for Pages builds; runtime secrets for Workers with
wrangler secret put. - Replit: secrets in the Publishing pane. Editor secrets do not carry over automatically.
- Supabase Edge Functions:
supabase secrets set NAME=value.
The rule that keeps you safe
Anything with a browser prefix is public. Service role keys, Stripe secret keys and AI provider keys must stay server-side, without a prefix. If one was ever exposed, rotate it: see exposed API keys.
Want it fixed instead?
Deploy or single fix: $400–800, fixed scope, quoted after the $149 diagnosis (credited in full).
Common worries, answered
- Will you mess up my repo? No. We work from read-only access, and every fix arrives as a pull request. Nothing merges until you merge it.
- Is this just more AI? AI coding agents help prepare fixes. A human reviews every fix before it ships.
- What if it still breaks? We keep working until the written scope is done, at no extra cost. Fixed, or we keep working free until it is (within the written scope).
- What about Stripe and my secret keys? Scoped access only. We never take full keys or owner logins; your secrets stay yours.
- How is this different from asking ChatGPT? We don't stop at advice. We fix and launch against a written scope.
Get a $149 diagnosis See pricing Fix my deploy
- Fixed, or we keep working free until it is (within the written scope).
- A human reviews every fix before it ships.
- read-only access; fixes arrive as pull requests you merge
- Your $149 diagnosis is credited in full toward any paid job.
FAQ
Why is process.env undefined in my React app?
Browser code only sees prefixed variables that were present at build time. Add the prefix (for public values only) and rebuild.
Do I need to redeploy after changing env vars?
Yes on Vercel, Netlify and Cloudflare Pages: build-time values are baked into the bundle.
How much does it cost to fix?
A deploy fix is $400–800 fixed, quoted after the $149 diagnosis, which is credited in full.