Insights
Browser extension errors begone!
Sebastian
Our team has received a lot of feedback about errors caused by browser extensions flooding projects. We have listened! In the latest version of our JavaScript client, errors triggered by browser extensions will not be reported anymore.
Our JavaScript client sends all errors to Flare. When the error is processing on our servers, we'll check if it's is likely caused by a browser extension. If it is, we won't report it and it won't count towards your monthly usage.
Update to our latest package version rid of those pesky errors, we'll take care of it from there!
npm install "@flareapp/[email protected]"
If you do want to see errors caused by extensions, you can opt in to reporting them by configuring the client.
flare.light();
flare.configure({
reportBrowserExtensionErrors: true,
});
There's no way for a browser to tell us whether an error is triggered by an extension or not. We partially rely on magic (aka regex) to detect them. If you still notice a bunch of errors that shouldn't be there: let us know! We love data we can use to improve our product.
Continue reading
Version 2 of our JavaScript client libraries
We shipped v2 of @flareapp/js, @flareapp/react, @flareapp/vue, and @flareapp/vite. The framework packages now handle error boundaries, automatic context collection, and component prop capture out of the box. The core client talks to a new, faster ingestion endpoint, and the Vite plugin got retry logic and smarter sourcemap handling.
Sébastien
Flare ❤️ Livewire
Flare has deep Livewire visibility: components nested in traces with full hierarchy, per-phase timing (mount, hydrate, render, dehydrate), aggregated component views with bidirectional links, rich error context, and a lot more. Let us show you how Flare can assist in debugging your Livewire project.
Ruben
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates
