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
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
