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
Introducing Flare’s next big feature: performance monitoring
Flare's new Performance Monitoring feature is now live, giving you complete visibility into your Laravel app's HTTP routes, queued jobs, Artisan commands, and database queries.
Freek
Lessons from the deep end
20 months ago, we started building Performance Monitoring as Flare’s next big feature, never expecting Laravel’s rapid commercial growth to put us in direct competition with their own tools. This is our honest take on those 20 months went, how we’re adapting to this new reality, and where we’re heading next while staying true to who we are. A dive into the deep end, without knowing how far down it goes.
Alex
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates
