Weave Code
Wire Extender Laravel Package
wire-elements/wire-extender
Wire Extender lets you render Livewire components anywhere, even outside your Laravel app. Expose components through a secure API endpoint and mount them on external sites or separate services with the JavaScript client, keeping full interactivity without duplicating code.
Wire Extender allows you to embed any Livewire component on any website or even within a static HTML file.
Frequently asked questions about Wire Extender
- What does wire-elements/wire-extender actually do?
- Wire Extender lets you render Livewire components outside your Laravel application, including on separate websites or inside static HTML files. You expose chosen components through a secure API endpoint and mount them on the external page with the package's JavaScript client. The components stay fully interactive without copying your Blade or PHP code into the other site.
- How do I install wire-extender in a Laravel application?
- Install it with Composer, and the service provider is auto-discovered, so no manual registration is normally needed. Publish the package config and JS assets, then include the published client script in the layout of the page or site that will mount the component. Verify the published JavaScript is rebuilt or re-emitted through your Vite pipeline rather than simply copied, since both Livewire and this package touch Alpine lifecycles.
- Does wire-extender support Livewire 3?
- Version 2.0.4 removes Livewire 3 support, so it is not a safe choice for a Livewire 3 application. Teams staying on Livewire 3 must pin explicitly to 2.0.3, either as an exact version or with a constraint below 2.0.4. Do not float the constraint, because a routine composer update could otherwise pull in an incompatible release.
- Which Livewire version does wire-extender 2.0.4 require?
- Version 2.0.4 targets Livewire 4, and there is no single version range that cleanly serves both Livewire 3 and Livewire 4. Because this compatibility drop shipped as a patch release from 2.0.3, treat the 2.x line as tracking the current Livewire major rather than as a stable compatibility contract. Check the exact composer.json constraint on livewire/livewire before upgrading, since that determines whether Composer protects you automatically or whether the failure appears at boot or component render time.
- What Laravel and PHP versions does wire-extender support?
- The changelog for 2.0.4 only lists the pull request title and does not state Laravel or PHP floor requirements. Confirm compatibility against the composer.json of the specific release before scoping any work. The dominant compatibility axis is the Livewire major version, not Laravel, but Laravel 10, 11 and 12 stacks should still be verified explicitly.
- Is it safe to expose Livewire components through the API endpoint?
- The package is designed around a secure endpoint, but every component you expose becomes part of your public surface area. Treat it like any public API: expose only components you intend to be embeddable, keep secrets and sensitive data out of component state, and validate all incoming actions and parameters. Also consider which domains you allow to mount the components and what authorization the mounted actions should require.
- How do I embed a Livewire component on a static HTML page?
- Include the published JavaScript client on the static page and mount the component by referencing the name or alias you exposed through the endpoint. The page does not need Blade, PHP or a Laravel request lifecycle of its own; it only needs the client script and a mount target in the DOM. Keep the client assets in sync with the package version running on the Laravel side, especially after a Livewire major upgrade.
- Does wire-extender work with Inertia, Vue or React single page applications?
- It is a poor fit for API-only services or front ends built on Inertia, Vue or React, since the package is built to extend Livewire's own mounting behaviour rather than to integrate with other front-end frameworks. It suits Blade-first Laravel monoliths that already use Livewire and need components inside CMS-rendered markup, legacy Blade partials or Alpine-managed regions. It is an additive layer, so adopting it in one bounded area carries low structural risk.
- Is wire-extender actively maintained and what is the upgrade risk?
- It is community maintained with a narrow contributor base, and patch-level releases have dropped support for an entire upstream Livewire major, which is unconventional for semantic versioning. Wire Elements has commercial offerings, but do not assume a documented support SLA or a guaranteed window of bug and security fixes for older releases such as 2.0.3. Expect this pattern to recur at each Livewire major, and plan the Livewire upgrade as the gating event with the wire-extender bump in the same change. Alternatives, such as iframing a Laravel-rendered page, avoid the coupling but give up seamless interactivity.
- How should I test components mounted with wire-extender?
- Test the Livewire components themselves inside the Laravel application using the normal Livewire testing helpers, since that is where the business logic lives. Add an integration check that calls the endpoint and confirms the expected payload and authorization behaviour, then a smoke test that the external page mounts and interacts correctly. Re-run those tests after every Livewire upgrade, because support being removed may mean the JavaScript hooks were not yet ported rather than confirmed broken.
Weaver
How can I help you explore Laravel packages today?