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
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