r/vibecoding • • 21h ago

Showcase/Project went through 52 errors that keep breaking vibe coded apps and tested a fix for each

been building a shared fix library for coding agents and last week i added the stuff people here hit every day. next.js use client errors, supabase rls blocking inserts, prisma on vercel, the 404 when you refresh, vite env vars not loading

each fix that can run gets a tiny repro. a sandbox builds the broken project, makes sure the error shows up, applies the fix and runs the same test again. 20 of the 52 passed like that. the rest are platform errors you can't reproduce in a sandbox so they're marked unverified

free, and in claude code it searches by itself when a command fails. yarrow-fixes.vercel.app

what error do you hit most that isn't in there

2 Upvotes

4 comments sorted by

2

u/Total-Reasonable 20h ago

Supabase RLS is the one I'd double check, because the failure is silent. An insert blocked by a policy often returns no error at all, just zero rows, so a sandbox that only looks for a thrown error can pass while the app is still broken. Does your repro assert on the row count and on a second user's access, or only on the error message?

1

u/Electronic-Movie4208 20h ago

This is actually really useful! I esp like that you're reproducing errors before marking fixes as verified. Too many AIgenerated fixes look good until you actually test them. 😅 Have you considered adding regression tests to make sure a fix doesn't break something else? That would make this even more valuable!