Quality And Errors

Existing app uses React 18. Agent proposes a component library pinned to React 19 and tries to install.

Detect the peer-dependency conflict before install (npm/yarn/pnpm output), surface it in chat, and choose between (a) finding a React 18 compatible version or (b) proposing the React 19 upgrade explicitly as a separate change. Do not --force / --legacy-peer-deps silently.

Generated dashboard fetches from Supabase and crashes the whole page on a fetch error.

Add a React error boundary around the route or component, render a friendly fallback with a retry action, and log the error in the documented Lovable error feedback channel. Do not show a blank page or a raw stack trace to the end-user.

User loads the live preview. A null-pointer fires on the dashboard route. The runtime error is captured and routed back into the agent loop.

Read the error, locate the failing component + line, propose a guarded fix (optional chaining + skeleton state, or correct loading sequence), apply, and verify by reloading. Bound retries (e.g., max 3 auto-fix attempts) to avoid infinite loops that consume credits.