Over the next few months, we're committed to fixing bugs - not just in your code, but in our app too. We’ve got a bunch of improvements lined up to make Flare even better!

Our team has received a lot of feedback about errors caused by browser extensions flooding projects. We have listened! In the latest version of our JavaScript client, errors triggered by browser extensions will not be reported anymore.

Secret management isn't the most thrilling part of development, but it's crucial. Let's look at some options, why we chose the 1Password CLI and how to set it up.

Laravel's handy rescue helper to the ... rescue!

From now on, you can quickly retry a failed Laravel Horizon job without hassle.

For any application, handling errors gracefully is crucial for maintaining a smooth user experience. While PHP's try-catch statements are great at catching known exceptions and preventing them from crashing your application, they also make exceptions go unnoticed. What if you also want to log and report an exception without bringing your application to a screeching halt? That's where Laravel's report helper steps into the spotlight.

We now mark exceptions as handled when they don't crash your application.

In PHP 8.0 WeakMaps were added, a mystical feature we never used until we had a complicated issue to solve.

You can now set a priority for each exception to find out what needs to be fixed first.

How to fix bugs for packages used by all versions of Laravel released in the past five years?

Share your errors to Flare from the new default Laravel error page.

From now on, you prefill some info about the error in issues.

In our latest release we've added support for assigning an error to a user of your team.

Flare has long relied on locally running Laravel Envoy for our app deployments. However, as the application and infrastructure evolves, so do the challenges. This article documents some of our endeavors to come up with a more robust solution in 2024 while keeping our deploys as simple as possible.

We're proud to share that errors on Flare can now be associated with Linear. In this post, we'll tell you all about it!

Laravel 11 recently introduced a nice new feature called Context. Ignition and Flare have both been updated to collect and show all context.

Laracon EU 2024 was an awesome conference, we were sponsoring with Flare and having a blast until a DDoS attack hit us.

We've recently switched our database infrastructure from MySQL to Postgres, this is a high level overview on how we used Laravel's query builder to migrate our data.

We released our new suite of JavaScript packages. With updates for our JavaScript, React, Vue, and Vite plugins.

Using custom context and glows adds extra information to error reports, helping you quickly understand and fix problems in your Laravel applications.

It is integration month! After Jira we're launching another integration: Gitlab.

A few days ago, we added a GitLab integration. In this blog post, we'll talk about the road to that integration and our struggles.

Connect your Flare errors with Jira issues

We've improved user management on Flare.

Learn how Cloudflare Workers in Flare enable edge-based API authentication, effectively filtering out unauthorized requests and enhancing performance for your application.

Collaborating in Slack to solve your exceptions just got a lot better with unfurling. We'll also do a bit of a code dive into how to integrate Slack unfurling into a Laravel application.

We created a new structure for external integrations like GitHub and Jira which allows us to add these kinds of integrations a lot quicker.

Errors will inevitably occur in your application. There is no way around it. If you notice them while working locally, you can fix them immediately. However, if your application is already live, it gets more tricky because you are not the only person triggering errors anymore. This is where error tracking software like Flare comes in handy.

Earn money by referring users to Flare

This will make it easier for newcomers to get familiar with Flare

Today we're introducing the error activity feed and notes.

Picture this: a bunch of developers, most of them back-enders, are given a Figma design file to turn into the new homepage for Flare. We set out to build our brand-new marketing site with a sprinkle of animations. Here is how we crafted them.

Here's how you can implement our log in flow in your Laravel app

Secret secrets are no fun, secret secrets hurt someone... unless they're managed right in your Laravel deployment! Say goodbye to plaintext perils and .env file follies. For Flare we explored some alternative solutions like config servers, the env:encrypt command and git-secret to keep your production environment variables safe and sound. Using git-secret's with user-specific access control and PGP encryption, managing environment variables becomes a breeze.

We now show the arguments used with each function or method call, in this blogpost we go through the implementation of it.

These past months, we've been busy redesigning our entire service. We're very proud to launch it today.

Today, we're adding AI-powered solutions to Flare. This means we can suggest a solution for almost any error: the AI will likely suggest a helpful suggestion for most errors.

Debugging errors can leak sensitive information, let's see how we can solve this using PHP 8.2

SSR Inertia and response cache: the ultimate performance and SEO combo!

Good things are coming!

We're still working on our redesign and are close to release. Today we started tackling an issue where the performance of the error page was too slow for us. In the end, we needed to change the structure of the error occurrences table, which is a lot harder than it seems.

The new version of Flare has a lot of graphs, but how do we calculate the data

We're introducing Flare Roulette™ today. Let's make bug-fixing great again!

We're redesigning Flare, but our application became really slow. Let's find out why and fix it!

We're giving our entire service a new coat of paint

Since the early days, Laravel has had an excellent validator available, but sometimes it doesn't work as expected, especially with nested arrays.

We now support the most popular payment methods in Belgium and The Netherlands

According to the React maintainers, React developers reach for the useEffect hook too quickly. It is far from the only hook with many naive usages.

Creating a Flare subscription within the EU was never easier

Here's a rundown of all the things we improved in Flare in the past year.