Insights
You can now give team members access to specific projects
On most projects, you're probably not working alone. That's why Flare has been team-based from day one. Everybody invited to your team on Flare can see all the projects you have in your account.
For small teams, this mostly works fine. When you have a bigger team, people often don't need access to all projects in your Flare account but only a few specific ones they are working on.
That's why we've now added the ability to give team members access to specific projects. In the team settings, you can specify which projects each of your team members should be able to see.

Remember that Flare, as an error tracker, contains potentially sensitive information. So it's also good practice to only expose that information to people who really need to see it.
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