EvoUI v1.1.1: Component Runtime Boundary for Manager Modules

EvoUI v1.1.1 continues the 1.1 line of the shared UI foundation for modern Evolution CMS manager modules. The main change is architectural: consumer packages can now register reactive manager components through EvoUI itself instead of wiring directly into Livewire.

What changed

• EvoUI::registerComponent() is now the public registration boundary for package components.
• Consumer components can extend EvoUI\Components\Component, keeping module code tied to EvoUI rather than directly to Livewire internals.
• Component declarations made before runtime boot are queued and flushed automatically, while late registrations are activated immediately.
• Module table refresh now uses the Alpine-safe evo-ui:module-tab-refresh event.
• Tables refresh only when the active manager tab is targeted, avoiding unnecessary manager frame reloads.
• The package baseline now targets PHP 8.4 and newer.

Why it matters

This makes EvoUI a cleaner runtime contract for packages such as sArticles, sSeo, sLang, sSettings, sTask, and future manager modules. The practical result is less repeated Livewire setup code, safer tab refresh behavior, and a more predictable module UI layer.

Upgrade notes

• Projects using EvoUI 1.1.x should run on PHP 8.4 or newer.
• Package authors can replace direct Livewire::component() calls with EvoUI::registerComponent().
• Existing EvoUI 1.0.x modules should be reviewed when moving to the 1.1 runtime boundary.

Open the EvoUI v1.1.1 release on GitHub