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
Introducing Flare’s next big feature: performance monitoring
Flare's new Performance Monitoring feature is now live, giving you complete visibility into your Laravel app's HTTP routes, queued jobs, Artisan commands, and database queries.
Freek
Lessons from the deep end
20 months ago, we started building Performance Monitoring as Flare’s next big feature, never expecting Laravel’s rapid commercial growth to put us in direct competition with their own tools. This is our honest take on those 20 months went, how we’re adapting to this new reality, and where we’re heading next while staying true to who we are. A dive into the deep end, without knowing how far down it goes.
Alex
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates
