Livewire v4.4.2 Released: Bug Fixes, Resilience Improvements, and Alpine 3.16.3
Laravel Livewire #Livewire #Laravel #PHP #Alpine.js #Release Notes

Livewire v4.4.2 Released: Bug Fixes, Resilience Improvements, and Alpine 3.16.3

3 min read Mohamed Said Mohamed Said

Livewire v4.4.2 Is Out — Here's Everything That Changed

Released on 24 August 2026, Livewire v4.4.2 is a focused patch release that closes a broad set of bugs, tightens edge-case behaviour, and bundles Alpine 3.16.3. There are no breaking changes, so a composer update livewire/livewire is all you need.


Key Changes at a Glance

Exception Hook Support for Computed Properties

PR #10543 adds the ability to hook into exceptions thrown inside computed properties. Previously, errors in a computed property could surface in unexpected ways; you can now handle them consistently through Livewire's exception hook mechanism.

Eloquent Cast Fallback When Filling Typed Properties

When Livewire fills a typed property and no explicit cast is defined on the component itself, it now falls back to the Eloquent model's own cast definitions (PR #10548). A related fix (PR #10559) prevents casted Eloquent attributes from bypassing validation under legacy model binding.

Recover from Failed Server Responses

One of the most impactful changes in this release: if a server response fails, Livewire now reverts the rejected updates on the client instead of leaving the UI in an inconsistent state (PR #10438). This makes your components far more resilient to transient network or server errors.

Ignore Repeated Lazy-Load Calls

Duplicate lazy-load requests triggered by rapid user interactions or re-renders are now silently ignored (PR #10562), preventing redundant network round-trips.

Loading State Persists Through navigate Redirects

The wire:loading state now stays active across SPA-style navigate redirects (PR #10539), so your loading indicators no longer flash off prematurely.

Skip Transitions for Top-Layer UI

Elements rendered in the browser's top layer (dialogs, popovers) no longer trigger Livewire's morph transitions, avoiding visual glitches (PR #10552).

Fix wire:action Collisions with Alpine Scope Variables

A naming collision between wire: action directives and Alpine.js scope variables has been resolved (PR #10561), which is especially relevant in components that mix Livewire actions with Alpine x-data objects.

Signed Upload/Preview URL Fix for Proxied Origins

Signed temporary upload and preview URLs no longer break when a reverse proxy's forwarded origin is not in Laravel's trusted proxies list (PR #10574).

Content-Based MIME Detection for Temporary Uploads

MIME type detection for temporary file uploads now uses file content rather than relying solely on the file extension (PR #10581), improving accuracy and security.

Alpine 3.16.3 Bundled

The bundled Alpine.js version has been updated to 3.16.3 (PR #10584).

Additional Fixes

  • Typed-return conflict in Livewire redirector resolved (PR #10555).
  • Resetting component properties no longer unsets form objects (PR #10554).
  • static return type added to page component view macros (PR #10553).
  • Asynchronous morph timing gaps closed (PR #10568).

Real Takeaways

  • Run composer update livewire/livewire — no breaking changes expected.
  • Failed server responses now auto-revert client state, reducing UI inconsistencies.
  • Eloquent cast fallback means less boilerplate when binding typed model properties.
  • Signed upload URLs are now proxy-safe out of the box.
  • Alpine 3.16.3 is included; no separate frontend update needed if you use the bundled build.
  • wire:loading now correctly spans navigate redirects in SPA mode.

Source: Livewire v4.4.2 on GitHub

Found this useful?

Frequently Asked Questions

3 questions
Q01 Does Livewire v4.4.2 introduce any breaking changes?
No. v4.4.2 is a patch release containing only bug fixes and improvements. You can update with `composer update livewire/livewire` without expecting breaking changes.
Q02 What happens when a server request fails in Livewire v4.4.2?
Livewire now reverts any rejected updates on the client side, so the UI returns to its previous consistent state instead of being left in a broken or partial state after a failed server response.
Q03 Do I need to update Alpine.js separately after installing Livewire v4.4.2?
No. If you use Livewire's bundled Alpine build, Alpine 3.16.3 is included automatically. No separate frontend update is required.

Continue reading

More Articles

View all