Your app throws errors in the visitor's browser
Client-side runtime errors
What this means
When a visitor opens your app, its code fails in their browser. Errors like this usually mean part of the page silently stops working — a form does not submit, a list stays empty, a button does nothing — while the page itself still looks fine to you.
Why it matters
A broken screen loses the visitor without telling you: there is no server error to look at, so the failure is invisible from your side. Error text also tends to leak internal details — API paths, service names, sometimes keys — straight into the browser console, where anyone can read it.
When this is not a problem
Errors coming from third-party widgets (analytics, chat, ads) appear in the same console but are not your code. Check the source of each message before changing anything.
How to fix it
- Open the page in your browser, press F12 and look at the Console tab — the same messages are listed there.
- Fix the failing calls first — an error during data loading is what usually leaves a screen empty.
- Make sure the app handles failed requests instead of throwing, so one failed call does not break the whole screen.
- Keep error reporting on in production so these failures reach you instead of only the visitor.
The app throws runtime errors in the browser console. Find the failing code path, handle the failure explicitly, and make sure the UI shows a clear state instead of breaking silently.
How to verify the fix: reload the page with the console open and confirm no errors appear