- How do I install robert-stanciu/wireless in a Laravel app?
- Install it with Composer using robert-stanciu/wireless:^3.0. There is no publish step, migration, config file, or service provider surface to register. Your app must run PHP 8.2+, Laravel 12, and Livewire ^3.6.
- Which Laravel and Livewire versions does Wireless support?
- Wireless v3 targets PHP 8.2+, Laravel 12, and Livewire ^3.6. The compatibility band is intentionally tight, and Composer will surface conflicts immediately. Older v1.x and v2.x releases remain published, and the package renumbers itself onto Livewire's major version.
- How do I mount and call a Livewire component from an Artisan command?
- Wireless stands up a synthetic Livewire component cycle inside the Laravel container, so you can invoke mount, set, and call from an Artisan command without going through the HTTP kernel. After the cycle you can read back redirect(), dispatched(), and returned() to inspect what the component did. This makes commands, seeders, and webhook handlers viable places to drive component behaviour.
- Can I use Wireless in queued jobs or scheduled tasks?
- Yes, that is the primary architectural fit: triggering meaningful Livewire component behaviour from non-browser contexts such as queue jobs, scheduled tasks, seeders, webhook handlers, and tooling harnesses. Keep in mind that it manipulates process-global container state during each cycle. In long-lived workers, verify that component invariants hold and that nothing leaks between jobs.
- Is Wireless safe with Laravel Octane or long-running queue workers?
- Treat this as a key evaluation question rather than a given. The package reaches into Livewire internals, manipulates the redirector stack, flushes Livewire state, and restores the authenticated user per guard after each cycle. Version 3.0.0 fixed several subtle issues in exactly those areas and added a global test guard against leaked components, frames, and redirectors, but the failure modes are silent rather than loud. Prefer CLI and test contexts where the blast radius is contained.
- How do I read redirects, dispatched events, and return values from a Wireless component?
- After running the synthetic component cycle, Wireless exposes redirect(), dispatched(), and returned() so you can inspect the outcome in plain PHP. You do not need an HTTP round trip or a browser to see where a component redirected, which events it dispatched, or what it returned. This is useful for asserting side effects in jobs, commands, and integration-style tests.
- Does Wireless replace Livewire::test() for component testing?
- No, it is meant to be adopted alongside existing practice rather than as a replacement. Keep Livewire::test() for unit-level component tests, and use Wireless for contexts HTTP cannot reach, such as jobs, commands, and webhooks, or for integration-style tests where you want the real cycle instead of the test harness. That keeps the dependency's blast radius small.
- What is the risk of using a package with zero stars and no dependents?
- The main risk is evidence, not effort: zero stars and zero dependents means there is no production precedent, and your team would be the first consumer of consequence. The public API is small enough to read in an afternoon, which lowers the cost of auditing and forking. Still, assume you can vendor or maintain it in-house before putting it on a production path.
- Will Wireless work when I upgrade to Livewire 4?
- Not automatically. Because the package renumbers itself onto Livewire's major version, every Livewire major is a porting exercise rather than a simple version bump. The livewire:3.x-dev canary helps with drift inside v3, but nothing currently mitigates a move to Livewire 4. Plan for that upgrade as separate work.
- Can I fork or vendor Wireless if the maintainer stops supporting it?
- Probably yes, and you should assume so before adopting. The package has a deliberately small surface: a single Composer dependency, no middleware, no service provider surface, and no config. That makes vendoring or an in-house fork realistic, especially if you only use it in CLI and test contexts.