Components

Wirechat registers Livewire components for panel pages, embedded widgets, modals, drawers, settings screens, group tools, and content surfaces.

Wirechat exposes public Livewire component identifiers for applications that replace registered components with custom classes. For the full embedded chat surface, see Standalone Widget.

When To Replace A Component

Publish and customize views when you only need markup changes. Replace a component class when your application needs behavior changes, additional actions, or custom state that belongs in Livewire code.

Most applications should start with Wirechat panel routes or the main wirechat widget. Lower-level components expect Wirechat state such as a panel, conversation, invite, or drawer context, and are usually opened by Wirechat actions.

Primary Components

For layout examples, see Standalone Widget and Tray Widget.

Modal And Drawer Shells

These components host other Wirechat components. They are normally rendered by Wirechat assets and actions, not mounted repeatedly by your application.

Chats List Components

Chat Info And Content

The content preview and viewer power the Pro Content Viewer feature.

Group Members And Permissions

Group Invite Links And Join Requests

Legacy Aliases

Wirechat still registers older group component aliases for existing integrations. Use the newer identifiers for new code.

Replace A Component

Register your custom class under the same Livewire identifier after Wirechat has booted.

namespace App\Livewire\Wirechat;

use Wirechat\Wirechat\Livewire\Chats\Chats as BaseChats;

class Chats extends BaseChats
{
    // Add application-specific behavior here.
}

use App\Livewire\Wirechat\Chats;
use Livewire\Livewire;

public function boot(): void
{
    Livewire::component('wirechat.chats', Chats::class);
}

php artisan vendor:publish --tag=wirechat-views