Livewire is quickly gaining traction in the Laravel ecosystem. It allows you to write dynamic web applications without ever even having to touch JavaScript! That's why we've decided to bring first-party support for Livewire components to Flare and Ignition.
Starting from Ignition v2.17 and above, if something goes wrong within your Livewire component's lifecycle, the accompanying error page includes a new tab that looks like this:
This new tab will show up on your local Ignition error page as well as in Flare's reports. It show which component was being rendered when the error occurred, what updates were triggered right before (property updated, method called or event send) and the data used to render the component.
We've also added a couple new solutions to Ignition specifically for Livewire. For example, a typo in a property name will trigger a solution that tries to suggest the corrent name:
The solution is displayed when a method with a typo is wrongfully called in a Livewire component:
Whether an exception is thrown in a Livewire component, Inertia response or a regular Blade view. Flare and Ignition will try to make it as smooth as possible to show you what happened!
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
