- How do I install livewire-dusk-testbench in a Laravel package?
- Install it as a dev dependency with composer require --dev joshhanley/livewire-dusk-testbench. There is no service provider configuration or migration to run; the package wires Livewire, Dusk, and Orchestra Testbench together for your package test suite. If you adopt the v3 beta, pin the exact version instead of using a caret constraint. You also need a CI runner or local machine capable of hosting a headless browser.
- Can I run Laravel Dusk browser tests for Livewire components inside Orchestra Testbench?
- Yes. That is exactly the purpose of the package: it lets a package's test suite exercise Livewire components in a real browser through Dusk while running on a Testbench application skeleton. This avoids scaffolding and maintaining a separate full Laravel application just for browser tests. It is a development-only harness, so it does not ship with your package.
- Does livewire-dusk-testbench support Laravel 12, or is it Laravel 13 only?
- The v3.0.0-beta.9 line is explicitly coupled to Laravel 13, Livewire 4, and testbench-dusk 11. The changelog says it adds Livewire 4 support but does not make clear whether that support is additive to Livewire 3 or raises the minimum version. Confirm the exact supported matrix before assuming it works on Laravel 11 or 12. If you are on an older stack, treat adoption as part of a framework upgrade rather than a routine package bump.
- Is joshhanley/livewire-dusk-testbench safe to use in production?
- It is a require-dev package with no production runtime footprint. It never ships to customers, never appears in deploy artifacts, and cannot fail in production. Its risk is bounded to CI pipelines and developer machines. That makes it much lower risk than a runtime dependency, even in beta.
- Do I need livewire-dusk-testbench if I test Livewire inside a normal Laravel app?
- No. Teams testing Livewire components inside a standard Laravel application can use laravel/dusk directly along with Livewire's own testing utilities. This package is aimed at package authors who need Dusk browser coverage on an Orchestra Testbench skeleton. If you do not maintain Livewire components as a package, this evaluation is likely not applicable.
- What is the supported version matrix for livewire-dusk-testbench v3?
- The provided assessment identifies the v3.0.0-beta.9 release as coupled to testbench-dusk 11, Laravel 13, and Livewire 4. Because all three are moving targets and the package is pre-GA, record the full package-version by Livewire by Laravel by testbench-dusk by PHP matrix in your repository. Pin the package exactly and gate CI on that matrix. Recheck the official documentation before adoption because the matrix may change between betas.
- Why is livewire-dusk-testbench still in beta, and what is the path to GA?
- The package is at 3.0.0-beta.9, the ninth beta, with no GA release noted in the material reviewed. It tracks pre-release Laravel 13 and Livewire 4, so beta churn is expected. The assessment recommends asking the maintainer for a stated GA path and keeping a fallback if the package stalls mid-beta. Do not assume beta-to-beta stability.
- How do I prevent version mismatch errors with livewire-dusk-testbench?
- Pin the exact version, such as 3.0.0-beta.9, rather than using a caret constraint. Betas that track pre-release frameworks routinely break patch to patch. Record the complete compatibility matrix in your repo and make CI fail if any layer drifts. Assign an owner for deliberately bumping the package and the related framework versions together.
- What are the alternatives to livewire-dusk-testbench for browser testing Livewire packages?
- Alternatives include running Laravel Dusk against a scaffolded Laravel application, using Livewire's own component testing utilities for non-browser coverage, or a Pest and browser-testing setup if it covers the interactions you need. A full application skeleton gives you the most conventional path but adds maintenance overhead. The package exists to remove that overhead for Testbench-based package suites. First decide whether you actually need real-browser Dusk coverage.
- Who maintains livewire-dusk-testbench, and is the bus factor a concern?
- The assessment describes it as a focused, single-maintainer utility from a Livewire core-team member. That gives high domain credibility but a low bus factor. Because it is dev-only and cannot affect production, the operational risk is limited to CI and local testing. Still, have a fallback plan if the maintainer steps away or the beta line stalls.