LaraDumps can also dump and show the latest state of Laravel Livewireopen in new window components.

This feature must be enabled and configured in LaraDumps config file.

You can also disable tracking of specific components in the same config file.

Livewire Events

LaraDumps can also listen to the Livewire Events and Browser Events (dispatch).

LaraDumps will also display a warning if the Event was not received by any other component.

Both features must be enabled. Read more about Livewire Events and Livewire Browser Events configuration.


Livewire Validation

LaraDumps can also listen to the Livewire Validation and dump its fails for you.

This can be useful during development or if you have not included a @error('field') directive in your Blade file.

This feature must be enabled. Read more about Livewire Validation configuration.

Livewire Component Highlight

Pages with multiple components can be overwhelming.

To help you identify each component, LaraDumps can highlight the component in your browser whenever you select it in the Desktop App.


In order to make this feature to work, you must:

1․ Enable this feature. Read more about Livewire Component Highlight configuration.

2․ Add your Pusher credentials in your .env file

3․ Import the highlight in code in your project's app.js. See below:

if (process.env.NODE_ENV === 'development') {

Page reload

In order to keep track of your page components, you will need to clear your LaraDumps App history every time your page is reloaded. LaraDumps can do it automatically for you. Read more about Livewire Auto-Clear functionality.


❗ You might experience performance issues in your application when tracking Livewire components statement with other debug tools.


Interacting with the counter component will be tracked by LaraDumps.

class Counter extends Component
    public int $count = 0;

    public function increment()
        $this->emitTo(Counter2::class, 'count', $this->count);

    public function render()
        return view('livewire.counter');