Skip to content
SlashClone
Made by@shipcheck

Deploy doctor

@shipcheck/deploy-doctor

Paste a failed Vercel or Netlify build log and get the most likely cause and a fix you can apply. Recognizes about twenty common failures: letter-case import errors, missing packages, missing env vars, prerender errors, window is not defined, lockfile drift, peer dependency conflicts, wrong Node version, out of memory, wrong output or root folder, oversized functions, and more.

SkillDevOpsv1.0.0 (latest)Tested
Activity
New: be the first to try it
  1. 1Running build in Washington, D.C., USA (East), iad1
  2. 2Cloning completed: 412.330ms
  3. 3Restored build cache from previous deployment
  4. 4Running "vercel build"
  5. 5Vercel CLI 39.1.0
  6. 6Installing dependencies...
  7. 7up to date in 2s
  8. 8Detected Next.js version: 15.0.3
  9. 9Running "npm run build"
  10. 10> demo-app@0.1.0 build
  11. 11> next build
  12. 12 ▲ Next.js 15.0.3
  13. 13 Creating an optimized production build ...
  14. 14 ✓ Compiled successfully
  15. 15 Linting and checking validity of types ...
  16. 16 Collecting page data ...
  17. 17 Generating static pages (0/8) ...
  18. 18Error: supabaseUrl is required.
  19. 19 at new SupabaseClient (/vercel/path0/node_modules/@supabase/supabase-js/dist/main/SupabaseClient.js:45:19)
  20. 20 at createClient (/vercel/path0/.next/server/chunks/412.js:1:2203)
  21. 21Error occurred prerendering page "/pricing". Read more: https://nextjs.org/docs/messages/prerender-error
  22. 22Export encountered an error on /pricing/page: /pricing, exiting the build.
  23. 23 ⨯ Next.js build worker exited with code: 1 and signal: null
  24. 24Error: Command "npm run build" exited with 1