Today we're shipping a small but lovely upgrade to Flare: every query exception now comes with a SQL statement you can actually copy and run.
Here's what query exceptions used to look like:
Query exceptions in Flare have shown the executed SQL for years. Can you spot the problem? Those UUIDs are strings, so they need quotes. Paste this into your database client and you get a syntax error. Laravel builds the message that way on purpose (exception constructors have to stay cheap and safe), so the bindings go in raw.
We weren't happy with that. Flare is where you go to fix things fast, and a broken SQL string slows you down every time you hit one.
So we added a step in the newest laravel-flare client. Before the message is sent to Flare, we walk the bindings and format them properly:
Click, copy, paste, run. The way it should have always been.
Happy debugging!
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
