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
Create richer issues from your errors
When Flare creates an issue on GitHub, GitLab or Linear, you can now pick the assignee and labels right away.
Ruben
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
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates
