Livewire

wire:navigate intercepts the click, fetches the new page in the background and swaps in its body, title and URL without a full reload; @persist('name') keeps a matching element alive across those swaps instead of replacing it.

wire:poll makes the browser send a component request on an interval, calling $refresh or a named action; in Livewire 4.4.7 the default interval is 2 seconds, so every open tab adds steady server load.

#[Authorize('ability', 'argument')] runs a Gate check before a Livewire action executes and returns 403 on failure. The argument resolves as a class name, a type-hinted method parameter, or a component property.

Every Livewire public property is serialized into the page's wire:snapshot attribute and every update response as readable JSON. The checksum only proves the snapshot was not altered; it does not hide anything, so secrets must stay server-side.

Chain Livewire::actingAs($member) and Livewire::withQueryParams(['ref' => 'footer']) before test(), then set('contacts', UploadedFile::fake()->create('contacts.csv', 4, 'text/csv')); Livewire simulates the whole temporary-upload flow for you.

temporaryUrl() returns a signed URL that serves the private temporary file for previewing; it only works for extensions listed in temporary_file_upload.preview_mimes, so a PDF throws FileNotPreviewableException unless you check isPreviewable() first.

Livewire's upload endpoint only enforces the global rules, so the component must validate the temporary file against the field's own rules before storing it; the original file name the user sent must still be treated as untrusted input.

#[Renderless] or skipRender() skip re-rendering after an action the view does not reflect, such as logging. Livewire 4's #[Async] runs an action in parallel instead of queued; if it mutates state, parallel requests share a snapshot and lose updates.

Livewire 4 interceptors wrap network traffic at three levels, action, message and request, with onSend, onSuccess, onError and onFinish callbacks; Livewire.hook() remains for component, element and morph lifecycle events. A global request interceptor handles 419s.

Give each Livewire field the timing it needs: debounce the query (wire:model.live.debounce.400ms), send price inputs on blur or Enter, keep rarely used filters deferred behind an Apply button, and show wire:dirty or loading states so users know input is pending.

A public Eloquent collection is dehydrated to class and keys, then reloaded by key on later requests without its select(), eager loads or global scopes. Keep scalar filters public, move the list to #[Computed], and persist only arrays on Laravel 13.

Livewire restores public state, then runs boot(), hydrate() and hydrateFoo(), booted(), the updating hooks as values are written, all updated hooks, the called actions, rendering()/rendered() around the view, and finally dehydrate() before taking the new snapshot.

An @island region re-renders independently: an action inside it, or one scoped with wire:island, re-renders only that region, and a normal component re-render skips it; state and hydration still belong to the whole component.

Only the model's class, or its morph-map alias, and primary key go into the Livewire snapshot. On each later request Livewire re-queries the row with firstOrFail, so unsaved attribute changes, loaded relations and select() constraints are gone.

Livewire updates hit one shared endpoint, so the page route's middleware would not run again. Livewire re-applies only middleware on its persistent list, such as auth and can; custom middleware needs Livewire::addPersistentMiddleware() in a service provider.

Livewire::test() runs the component's PHP round trips with route middleware disabled and no browser, so it misses JavaScript, Alpine, wire:model modifiers, missing inputs, routing and middleware. An assertSeeLivewire HTTP test and a few browser tests cover those.

Setting the temporary disk to an S3 disk makes the browser upload straight to the bucket with a presigned URL, bypassing the app server; you then need a bucket lifecycle rule for cleanup, component validation for every file, and single-file inputs.

Livewire calls trait hooks named after the hook plus the trait's class basename, such as bootHasOrderTotals() or updatedHasOrderTotals(), so several traits can each hook the same lifecycle point without colliding method names.

$this->stream() flushes a chunk of content to the browser while the action is still running; Livewire inserts it into the element marked wire:stream with the same name, appending by default, and renders normally when the action finishes.