Livewire v4.4.1 Released: Bug Fixes, Alpine 3.16.2, and Laravel 13 Compatibility
Laravel Livewire #Livewire #Laravel #Alpine.js #PHP #Bug Fix #Release

Livewire v4.4.1 Released: Bug Fixes, Alpine 3.16.2, and Laravel 13 Compatibility

3 min read Mohamed Said Mohamed Said

Livewire v4.4.1 Is Out — Here's What Changed

Released on 18 August 2026, Livewire v4.4.1 is a focused patch release that resolves a range of bugs accumulated since v4.4.0. It also bumps the bundled Alpine.js twice — first to 3.16.1, then to 3.16.2 — and closes several edge cases that were tripping up Laravel 13 users.

Alpine.js Bumped to 3.16.2

Caleb Porzio landed two consecutive Alpine upgrades in this release (3.16.1 via #10530 and 3.16.2 via #10546). If you rely on Livewire's bundled Alpine build, you get both improvements automatically after upgrading.

Cached Computed Properties Fixed for Laravel 13

A regression caused cached computed properties to return broken objects when running on Laravel 13. The fix landed in #10525 and is transparent — no code changes needed on your end.

Nullable Enum Property Now Handles null Correctly

Previously, updating a nullable enum property back to null threw a ValueError. The fix in #10527 ensures the hydration layer gracefully accepts null for these properties:

// This pattern no longer throws a ValueError
public ?Status $status = null;

Reactive Eloquent Models and Lazy-Loaded Relations

A long-standing pain point: accessing a lazy-loaded relation on a reactive Eloquent model incorrectly triggered CannotMutateReactivePropException. Fixed in #10536, so relation access on reactive models now works as expected.

Server Actions Blocked from Reactive Bindings

Server actions were being unintentionally triggered by reactive property bindings. #10484 prevents this, reducing unnecessary round-trips to the server.

Asset Loading Fixes After Navigation

Two separate fixes address asset loading issues introduced in v4.x:

  • Script modules were not reloading after browser back/forward navigation (#10481).
  • Assets following a stylesheet were silently skipped and never loaded (#10482).

Both fixes are by first-time contributor @stebrl.

Route Macros Available to Package Service Providers

The Route::lazy() and Route::defer() macros were not available when called from package service providers. #10533 corrects the registration timing so third-party packages can rely on these macros safely.

Other Notable Fixes

  • _removeUpload for Collection properties now works correctly (#10485).
  • Nested synthesizers are now recursively hydrated during property updates (#10489).
  • Implicit island morphs are batched and output order is preserved (#10529).
  • Unhandled promise rejections from cancelled polls are now caught (#10428).
  • Component namespace matching now only matches on whole path segments, preventing false positives (#10476).
  • Type validation added to CarbonSynth and EnumSynth (#10541).

Key Takeaways

  • Upgrade to v4.4.1 if you are on Laravel 13 and use cached computed properties.
  • Nullable enum properties are now safe to reset to null.
  • Lazy-loaded Eloquent relations on reactive models no longer throw exceptions.
  • Alpine.js is now at 3.16.2 in the bundled build.
  • Script modules and post-stylesheet assets load correctly after navigation.
  • Four new contributors joined the project in this release.

View the full v4.4.1 release on GitHub

Found this useful?

Frequently Asked Questions

3 questions
Q01 What does the Livewire v4.4.1 fix for cached computed properties on Laravel 13?
A regression in Livewire 4.x caused cached computed properties to return broken objects when the application was running on Laravel 13. The fix in PR #10525 restores correct behaviour without requiring any changes to your component code.
Q02 Why did updating a nullable enum property to null throw a ValueError in Livewire 4.x?
The hydration layer was not handling null as a valid value for nullable enum properties, causing a ValueError during the update cycle. PR #10527 adds a null check so the property is correctly set to null instead of attempting an invalid enum cast.
Q03 Are Route::lazy() and Route::defer() macros now available in package service providers?
Yes. Prior to v4.4.1 these macros were registered too late for package service providers to use them. PR #10533 corrects the registration order so third-party packages can safely call Route::lazy() and Route::defer() from their service providers.

Continue reading

More Articles

View all