Firebase has put Crashlytics for web into public preview. It watches for JavaScript errors that happen in your users’ browsers and can alert you when a new error appears or a fixed one comes back. Firebase says it points to the exact spot in your code where the crash happens, as Crashlytics has done for Android and iOS apps.
Browser errors are easy to miss because tests can pass and server logs can look fine while JavaScript crashes in the browser. A checkout button that throws an error in one browser version leaves nothing in your server logs.
What you get
Firebase lists native support for Next.js, React and Angular. Other JavaScript frameworks can report exceptions from the place where the framework handles errors. For React Router apps, Crashlytics records the route pattern, such as /profile/:userId, so errors group by page type instead of by individual user.
You can set it up in the Firebase console, with the Firebase command-line tool (firebase crashlytics:setup), or with agent skills, which are instructions your coding agent can follow. In a React app, you add one component near the root of the app and pass it your app version.
Web alerts are off by default. You can turn them on for new issues and for regressions, meaning closed issues that come back.
Readable stack traces need source maps
Production JavaScript is usually compressed, so a raw crash report points at unreadable code. Source maps are files that translate it back to your original code. Firebase’s command firebase crashlytics:sourcemap:upload --app FIREBASE_WEB_APP_ID --clean dist uploads them. The --clean flag removes the local map files afterward, so they are not left in the build folder you deploy.
Firebase also suggests asking your coding agent to investigate an issue and ship a fix. Read the proposed change before you merge it, since a fix that hides an error is not the same as one that removes the cause.
It requires the Blaze plan
Crashlytics for web is built on Google Cloud Observability and OpenTelemetry, so it requires the pay-as-you-go Blaze plan, which Firebase says includes a generous no-cost tier. A small app may stay inside it, but a busy app should check Firebase’s pricing before turning it on. Lowering the sampling rate reduces how much data is collected and what it costs.
The same foundation lets browser crashes appear alongside server logs from services such as Cloud Run. Errors your backend already reports through Error Reporting are grouped into the same issues.
End of article