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
One core, many clients: the new Flare JavaScript client architecture
We recently reshaped the Flare JavaScript client from a single browser library and a few thin framework specific packages into a small family of packages built on a shared, platform-agnostic core. This post explains why we did it, what the core package exposes, how the browser and Node SDKs are built on top of it, why the React, Vue, and Svelte packages sit one level higher, and how anyone can use the same core to write a Flare JS client for a platform we do not ship ourselves.
Dries
Logging is here!
Logging is now available for all Flare users! Send any log from your app to Flare and use our polished interface to filter and search your logs in real-time.
Jimi
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates
