In our UI, you can see a nice summary of all your projects. The project list mentions the number of errors in the past 30 days and how many are unresolved. Here's how that list looks like for all projects of the Spatie team. The project names are considered sensitive information, so we've rendered them illegible in the screenshot.
We think that most users won't visit this project list too often. Most of the times, you'll use Flare and access the app to handle a specific error.
We decided to email the project overview to each user every month. This is how that mail looks like. Notice that we also include links to what's new at the Flare blog.
If you don't want to receive this monthly mail, you can opt out at your user profile page.
You can see other improvements we recently made on our changelog. Do you have an idea to improve Flare? Let us know!
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
