Weave Code
Wireuse Laravel Package
foxws/wireuse
A collection of Livewire utilities and components for Laravel: property synthesizers, page components, form traits, state objects, structure scout discovery, infinite scroll and HTML helpers. Requires PHP 8.2+, Laravel 12+ and Livewire 4.2+.
Collection of Livewire traits and utilities
Frequently asked questions about Wireuse
- How do I install foxws/wireuse in a Laravel app?
- Install the package with composer require foxws/wireuse. You can optionally publish the config file using php artisan vendor:publish --tag="wireuse-config". The package requires PHP 8.2 or higher, Laravel 12.x or higher, and Livewire 4.2 or higher. It does not add database migrations or override application routes.
- What Laravel and Livewire versions does WireUse require?
- WireUse requires PHP 8.2+, Laravel 12.x+, and Livewire 4.2+. Projects on older Livewire 3.x or older Laravel versions will need to upgrade before using the package. Re-check the actual composer.json constraints before upgrading, especially if your app pins older framework versions.
- What features does foxws/wireuse provide for Livewire?
- WireUse provides Livewire-focused utilities including property synthesizers, Page components and component traits, form traits, state objects, Structure Scout discovery, infinite scroll, and HTML helpers. It is designed as a complementary trait and utility layer rather than a replacement for Livewire. The package is most useful for CRUD-heavy and form-driven Livewire applications.
- How do property synthesizers work in WireUse?
- Property synthesizers are a WireUse feature that helps force usage of model route-keys instead of model IDs. This can be useful when you want consistent route model binding behavior across Livewire components. Review the property synthesizer documentation and test the behavior in your own components before rolling it out broadly.
- Can I use WireUse state objects like a VueJS store?
- Yes, WireUse state objects are described as being based on states you find in a VueJS Store. They give Livewire components a structured way to manage shared or complex state. Check the state object documentation for usage patterns and test how state changes interact with your component lifecycle.
- What is Structure Scout in WireUse?
- Structure Scout is supported by the spatie/php-structure-discoverer package and helps discover and register components. It also offers benefits such as caching. This can reduce manual component registration work in larger Livewire applications. Confirm the discovery paths and cache behavior in the package documentation.
- How does infinite scroll work in WireUse?
- WireUse includes an infinite scroll utility that loads more results as the user scrolls. It is intended for long result lists in Livewire components where pagination-by-scroll improves the experience. Review the infinite scroll documentation for setup details and test pagination behavior with your data source.
- Is WireUse safe for production and how should I test it?
- WireUse is a specialized Livewire utility package with limited public adoption, so production use should be backed by testing in your own application. Run your app test suite around any components that use WireUse traits, especially forms, state objects, and infinite scroll. The v3.1.0 release is a minor update with no advertised breaking changes, which is a positive maintenance signal but not proof of production hardening.
- Will WireUse traits conflict with my existing Livewire component traits?
- Trait conflicts are possible if WireUse traits overlap with traits already used in your Livewire components. Overlapping methods or properties can cause namespace collisions or unintended behavior. Test components that combine WireUse traits with existing traits, and keep trait usage explicit and well reviewed.
- What are alternatives to WireUse and how is it maintained?
- Alternatives include built-in Livewire features, custom traits, or other Livewire utility packages, depending on which features you need. WireUse shows positive maintenance signals such as Dependabot updates, a documentation site, and a minor v3.1.0 release with no announced breaking changes. Its tight coupling to Livewire 4.2+ remains a risk if the package lags behind future Livewire changes.
Weaver
How can I help you explore Laravel packages today?