AskVibeMarked as helpful by the asker
Stop the loop first. Every "fix the errors" round is working from a worse starting point.
- Undo back to the one-error state (Restore Checkpoint on your first message, or git if you have it).
- Check what changed besides the component. My bet: it touched
tsconfig.json. A very common "fix" is flipping"strict": trueor changingmoduleResolution, which instantly surfaces dozens of existing errors in other files.git diff tsconfig.json - With the original single error, get the full picture yourself:
and paste only that error, with the file, into a fresh chat: "fix this error in this file only, don't change tsconfig or other files".
npx tsc --noEmit
The pattern to watch for: error count going up after a fix = the fix changed something global. Revert, don't pile on.
Because it's the most common one :) Strict is good by the way, turn it on someday on purpose, file by file. katja_s · edited
IT CHANGED STRICT TO TRUE. how did you know. reverted, back to 1 error, fixed that one in 5 minutes jakeypoo · edited
also started using git today because of this whole thing jakeypoo · edited
Error count going up = revert. Writing that on a sticky note. hugo_l · edited
git diff --statand tell us which files changed. ingrid_h · edited