When something breaks, the fastest path to a fix is evidence. Paste the exact error, share the failing network response, or take a screenshot of the broken UI. Lovable can read your console and network activity and usually finds the root cause in one shot.
/The debugging playbook
- 01Read the red banner: Vite errors point at the exact file and line — paste that message in chat.
- 02Open the console: Runtime errors, warnings, and your own console.logs live here.
- 03Check the network tab: Look for red status codes and inspect the response body.
- 04Reproduce it deliberately: If you can trigger the bug on demand, it's already half fixed.
- 05Switch to Chat mode: Ask "why is this failing?" — Chat can inspect files without editing them.
Escape error loops
If the same fix has failed three times in a row, the diagnosis is wrong. Stop, describe what you've tried, and ask Lovable to propose a completely different approach.