Insights
New teams will now see an example project
Freek
When people first create their Flare account (or create a new team within their account), they are greeted with instructions on how to send a first error to Flare. They would only see what an error in Flare looked like once they'd sent one themselves.
For people new to Flare, we wanted to make it easier to immediately see what errors look like and showcase some of the cool things we do when rendering particular errors. That's why new accounts and teams will now see an example project added to their account.

This project contains some nice example errors, like this one where we have code highlighting for the SQL query.

There's also an example error where we show the list of URLs where it occurred (all fictional URLs for this example).

And, of course, we also show an error that uses one of our defining features: solutions.

We hope this example project makes it easier for people to see that Flare can beautifully display all errors.
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