- How do I install HyperWire in a Laravel application?
- Install HyperWire with Composer using the package name yehuuu6/hyperwire, then follow the repository setup steps for publishing configuration, assets, and any migrations. Because version 2.0.0 targets Livewire 4, confirm your application is already running Livewire 4 before adding it. The supplied overview does not include exact publish or install commands, so check the repository README for the authoritative sequence.
- Does HyperWire support Laravel 11 or Laravel 12?
- HyperWire inherits its Laravel and PHP support floor from Livewire 4, so the safest answer is to match whatever Laravel versions Livewire 4 supports. The provided materials do not include a Composer manifest or CI matrix, so there is no explicit Laravel version list to cite. Check the package composer.json and the Livewire 4 requirements before committing to an upgrade.
- Is HyperWire compatible with Livewire 3?
- The v2.0.0 release note says HyperWire upgraded from Livewire 3 to Livewire 4, which means the current major version is built for Livewire 4. Livewire 3 and Livewire 4 cannot run side by side in one application, so you cannot mix them per route or per component. If you are still on Livewire 3, you would need an earlier HyperWire release, but its support status is not documented in the provided evidence.
- What is HyperWire used for compared with a normal Livewire starter kit?
- HyperWire is a Laravel Livewire starter kit that deliberately omits Flux and includes toast notifications, a rate limiter, and OTP email verification. It is also positioned around hypermedia-driven UI patterns for Blade and Livewire, aiming to reduce JavaScript for partial-update interfaces. In practice, evaluate it as an integrated starter kit rather than a drop-in utility package.
- How does OTP email verification work in HyperWire?
- HyperWire includes an OTP email verification flow as part of the starter kit, so you should expect verification routes, notification or mail classes, and storage for one-time codes. Configure a working Laravel mail driver and review any published migrations or configuration before testing the flow end to end. The provided overview does not specify code expiry, resend limits, or cleanup behavior, so confirm those details in the source.
- Can I use HyperWire's toast notifications and rate limiter without adopting the whole starter kit?
- That may be possible, but HyperWire is presented as a starter kit tightly coupled to the Livewire component lifecycle, so the features are likely designed to work together. The provided materials do not confirm whether the toast and rate-limiter pieces are independently publishable traits or components. Treat it as an integrated kit unless the repository documents isolated usage.
- How do I test HyperWire components and OTP email flows?
- Use Livewire component testing helpers such as Livewire::test plus Laravel mail and notification fakes to exercise OTP delivery without sending real email. Test expiry, resend throttling, and rate-limiter behavior with time travel and cache assertions. Because Livewire 4 may change testing helpers, run your full suite after upgrading rather than assuming existing assertions still pass.
- Is HyperWire production-ready, and what should I check before deploying?
- Treat v2.0.0 as a breaking major release tied to Livewire 4, and review the repository for maintenance activity, dependency constraints, and a changelog before deploying. Confirm that mail is configured for OTP delivery, that the rate limiter uses a shared cache store in multi-server setups, and that published assets are current. The provided evidence does not include a CI matrix or upgrade guide, so production confidence should come from your own staging tests.
- What are the alternatives to HyperWire for Laravel Livewire starter kits?
- Common alternatives include the official Laravel Livewire starter kit, Laravel Jetstream, Filament-based admin starters, and Flux UI kits. HyperWire differentiates itself by excluding Flux and bundling toast notifications, rate limiting, and OTP email verification. Choose based on whether you need those specific features and whether the alternative is already Livewire 4 ready.
- Why did HyperWire release v2.0.0, and is the upgrade breaking?
- The only supplied release note says HyperWire upgraded Livewire 3 to Livewire 4 under package version 2.0.0. A major package bump alongside a major dependency bump strongly suggests breaking changes to the package API or minimum platform requirements. Because Livewire 3 and 4 cannot coexist, plan a coordinated application-wide cutover and verify that every other Livewire-dependent package is Livewire 4 ready on the same day.