- How do I install jonassiewertsen/statamic-livewire in a Laravel app?
- Install it with Composer using composer require jonassiewertsen/statamic-livewire and make sure Laravel Livewire is installed and registered in the same application. Because the package is a thin Antlers-to-Livewire bridge, there is no Node build step or separate asset pipeline to configure. Publish and review any package config, then render a component with the provided Antlers tag to confirm the integration works end to end. Pin the version explicitly in composer.json, since the repository is archived and will not receive future compatibility updates.
- Which Statamic and Livewire versions does statamic-livewire support?
- Check the composer.json constraints in the tagged release you intend to use; the last release was 2024-10-01, which likely predates current Statamic and Livewire majors. The repository is archived, so no new compatibility work is being done. Run a CI matrix job that boots your app against each Statamic and Livewire pair you care about and renders a representative component before you commit.
- Why does my Livewire component reset or lose state in Statamic?
- Statamic's static cache and full-measure caching will cache the server-rendered Livewire HTML, so the browser receives stale markup and Livewire's update endpoint loses sync. Exclude the page or the region containing the component from caching, or render it dynamically outside the cached layout. Verify this with caching enabled in staging, not just locally.
- How do I pass props to a Livewire component inside an Antlers template?
- Use the package's Antlers tag syntax to pass parameters, which are resolved to Livewire's mount directive at render time. Because values pass through an Antlers parse pass before Blade sees them, quotes, arrays, and wire: attributes need careful escaping. Test props containing quotes, nulls, and model IDs, and prefer simple scalar values where possible.
- Can I render Livewire components inside Antlers loops and collections?
- Yes, the tag renders per iteration, but each instance needs a stable key and unique props so Livewire can track components correctly. Nested components and lazy loading are the seams where the thin mapping is most likely to break, so test those cases explicitly. If the tag surface does not cover nested or lazy components, a small custom Antlers tag calling Livewire's mount API is usually cheaper than patching the package.
- Where do Livewire's CSS and JavaScript assets get injected in Statamic?
- The package ships companion Antlers tags for asset injection, but Livewire normally expects to own the head and body-close injection points. In Statamic those are Antlers layouts you control, so verify the styles and scripts appear exactly once on every page that renders a component. Missing or duplicated assets usually show up as components that render but never update.
- Is jonassiewertsen/statamic-livewire still maintained?
- No. The GitHub repository is archived and read-only, with no security patches, no issue triage, and no compatibility work for future Statamic or Livewire majors. It has roughly 90 stars and 0 dependents, so there is no downstream validation and no emerging community fork. The code surface is small, which makes forking or reimplementing it credible, but plan that ownership up front rather than discovering it at upgrade time.
- What should I use if statamic-livewire is abandoned?
- Three options work: vendor the package into an internal namespace, pin the version, and own it; write a small custom Antlers tag that delegates to Livewire's mount API; or bypass the tag layer and render Livewire from a Blade view surfaced through Statamic's partial support. Forking is cheapest if the existing tag surface matches your needs, while reimplementing wins if its internals fight current Antlers or Livewire versions. Check the license before forking to confirm you have clean rights to maintain it internally.
- Does statamic-livewire work with Laravel Octane or multiple app servers?
- The package adds no runtime of its own, so Octane and multi-node PHP-FPM setups are only a concern for Livewire's update endpoint and session handling. If requests from the same browser can hit different nodes, enable session affinity or a shared session store so Livewire state stays consistent. Test the update round trip behind your actual load balancer, not just in a single-process local environment.
- How do I test Livewire components rendered through Antlers tags?
- Test the component class directly with Livewire's testing helpers, since the Antlers tag is only a thin render layer. Add feature tests that request the Statamic page and assert the component markup is present, including the asset tags, and add a test that runs with static caching enabled. If you fork or reimplement the tag, keep a small integration test that renders a component with props and inside a loop so regressions surface early.