- What is Larapex Livewire used for?
- Larapex Livewire is a Laravel wrapper that integrates the ApexCharts JavaScript library with Livewire. It provides PHP and Blade components for interactive, responsive charts that update as your Livewire data changes. It is aimed at dashboards, analytics screens, and real-time reporting where charts need to react to server-driven state.
- Does Larapex Livewire support Livewire 3?
- Livewire 2 versus Livewire 3 support is not confirmed in the available package information. The package has a single 2025 release and no published version compatibility matrix. You should run a version-matrix spike against your pinned Livewire major before adopting it.
- How do I install Larapex Livewire?
- The expected flow is a Composer install of larawire-garage/larapex-livewire, followed by publishing assets and configuration, then dropping a Blade or Livewire component into a view. Exact commands and publish tags should be taken from the README. Because downstream usage is not publicly validated, install it first in a scratch Laravel app before touching production code.
- Which Laravel and PHP versions does Larapex Livewire support?
- There is no published compatibility matrix for Laravel or PHP versions in the supplied context. With zero dependents, four stars, and one release in 2025, you should assume narrow support until proven otherwise. Verify the package constraints in Composer and test against your exact Laravel and PHP floor.
- How does Larapex Livewire handle chart updates and Livewire DOM morphing?
- This is the main technical risk: Livewire DOM morphing is hostile to imperative JavaScript chart instances, so the glue layer must correctly tear down and re-instantiate ApexCharts. You need to verify behavior on wire:navigate, polling, and $wire.$refresh with a production-representative chart. Also check whether the package uses native Livewire 3 reactive properties or only legacy emit and listen events.
- Does Larapex Livewire bundle ApexCharts or load it from a CDN?
- The asset strategy is not confirmed in the provided information. Audit whether ApexCharts is bundled through npm or loaded from a CDN, and check the CSP implications of each approach. Decide bundle versus CDN deliberately before standardizing the component internally.
- Is Larapex Livewire production-ready?
- Treat it as high technical risk relative to its novelty. The bus factor is effectively one, with four stars, zero dependents, and a single 2025 release, so expect to own the dependency's future. The MIT license makes forking straightforward, but budget engineering attention for maintaining or reimplementing the glue layer.
- How does Larapex Livewire compare to using ApexCharts directly with Alpine?
- If you currently hand-roll ApexCharts in Blade with Alpine, migrating to this package is mostly a mechanical refactor of chart configuration into PHP properties. It avoids writing manual @script and x-init plumbing and lets Livewire data drive the chart state. It is not a drop-in replacement for other chart libraries such as Chart.js or Filament widgets; treat those migrations as a per-screen rewrite.
- Can I use Larapex Livewire with Inertia, Vue, or React?
- No, it is a poor fit for Inertia, Vue, or React frontends. The package is designed for Laravel applications that use Livewire for reactivity. For JavaScript frontends, use a direct ApexCharts Vue or React wrapper instead.
- Does Larapex Livewire have tests and active maintenance?
- Test coverage and update-path testing are not confirmed in the available information. Support is expected to be GitHub issues only, with uncertain response times and no upstream SLA. Build your own tested reference chart component and keep an internal wrapper so the package remains swappable if maintenance stalls.