Checklists /Lovable + Supabase /Monitoring
Medium
Make production errors visible after launch
The Lovable preview hides a lot of failures. Once real people use the app, a blank screen and an unread browser console are how you lose the first users. You need one place that records server and client errors.
How to check
- Decide where errors will go: Supabase logs, the host's logs, or an error tracker.
- Cause a safe test error in a preview deploy, such as requesting a missing page that your code handles.
- Confirm the failure shows up in that log within a minute.
- Confirm the log does not store passwords, card numbers or full session tokens.
Prompt
Fix prompt
You are working in this repository. Do not add features. Goal: unhandled errors in production should be logged where I can read them, without recording secrets. Steps: 1. Find the app's error boundary or the lack of one. 2. Log a short message and a request id. Strip emails from query strings if they appear, and never log Authorization headers or Stripe secrets. 3. If there is no tracker configured, write errors with console.error as structured JSON so the host can collect them. 4. Show the user a plain message when something fails, rather than a blank page. 5. Tell me where to look after I deploy.