- What is elshaden/apiato-livewire?
- It is an Apiato container that adds Livewire support to views in an Apiato application, so you can build reactive, component-driven interfaces with familiar Livewire syntax. It is not a general-purpose Laravel package; it is built to fit Apiato's modular Porto architecture and its Ship and Container conventions. Use it when you already have or are starting an Apiato project and want Livewire for the UI layer.
- How do I install elshaden/apiato-livewire in an Apiato application?
- Install it with Composer inside an existing Apiato project and then load the container following Apiato's normal container conventions. Because Apiato is an opinionated starter kit rather than a library you add to any app, the realistic path is adding this container to an Apiato codebase you control. Check the repository README and composer.json constraints before installing so the version matches your Apiato and Laravel line.
- Does elshaden/apiato-livewire work with vanilla Laravel or only Apiato?
- It is designed for Apiato applications and assumes Apiato's directory contracts and container structure. In a plain Laravel app you should install Livewire directly instead, since this package's value is in wiring Livewire into Apiato views. Forcing it into a non-Apiato project would mean fighting the conventions it was built around.
- Which Laravel and PHP versions does elshaden/apiato-livewire support?
- Support depends on the Apiato major version the container targets, and Apiato major versions generally track Laravel majors with their own PHP minimums. Confirm the exact constraints in the package's composer.json and in the corresponding Apiato upgrade guide before planning an upgrade. Because Apiato is a fork-and-build framework, a Laravel upgrade usually means a coordinated Apiato upgrade too.
- Do I need to understand Apiato's Porto architecture to use Livewire with it?
- Yes, at least the basics. You should be comfortable with Apiato Containers, Ship, and the Route to Controller to Action to Task layering, because the Livewire container is placed inside that structure rather than beside it. Teams new to Porto should expect onboarding time, since far fewer PHP developers know Apiato conventions than know vanilla Laravel.
- Can I add Livewire components to my existing Apiato container views?
- That is the intended use case: the container provides a simple way to add Livewire to your views so existing Blade templates in Apiato containers can host interactive components. You can adopt it incrementally, starting with one view or container rather than rewriting the whole UI. Keep component classes organized within Apiato's container boundaries so the structure stays consistent.
- How does Livewire fit with Apiato's API-first architecture and response transformers?
- Livewire handles the server-rendered UI layer, while Apiato's API layer, including Routes, Controllers, Requests, Actions, Tasks, and Transformers, continues to serve your JSON endpoints. The two are complementary: you can expose an API contract and still build reactive admin or dashboard screens with Livewire. The container does not replace Apiato's API conventions, so plan for both layers explicitly.
- How do I test Livewire components inside an Apiato container?
- Use Livewire's own testing helpers, such as Livewire::test, within the test structure Apiato provides. Place those tests alongside the container they belong to so Apiato's conventions and test discovery keep working. If you rely on Apiato's base test classes, confirm they are compatible with Livewire's testing traits in your installed versions.
- Is elshaden/apiato-livewire production-ready and actively maintained?
- Treat it as a small-project dependency and evaluate maintenance before committing. Apiato itself is a small-team, largely single-maintainer framework, so adopting a companion container is a bet on continued maintenance as well as code quality. Pin versions in composer.json and composer.lock, review recent commits and releases, and have a plan for wiring Livewire manually if the container stalls.
- What are the alternatives to elshaden/apiato-livewire for reactive UI in Laravel?
- You can install Livewire directly in a plain Laravel app, or wire Livewire into Apiato yourself without this container, which costs more setup but removes a dependency. Other options include building a separate SPA with Inertia, Vue, or React that consumes Apiato's API, or keeping Apiato purely as an API backend with no reactive server-rendered UI. Choose based on whether Apiato's structure is worth the ceremony for your team and service lifetime.