Weave Code
Inertiajs Events Laravel Dusk Laravel Package
protonemedia/inertiajs-events-laravel-dusk
Laravel Dusk helpers for testing Inertia.js events. Adds assertions and utilities so you can verify Inertia events fire as expected in browser tests, making it easier to cover Inertia-powered Laravel flows end to end.
Inertia.js Events for Laravel Dusk
Frequently asked questions about Inertiajs Events Laravel Dusk
- How do I install protonemedia/inertiajs-events-laravel-dusk?
- Install it as a require-dev Composer dependency in a Laravel application that already uses Inertia.js and Laravel Dusk. Version 1.3.0 targets Laravel 9/10, Dusk 7, and PHP 8.1+, so check that your lock file resolves cleanly before adopting it. Apply it to a small set of Inertia navigation tests first to confirm it reduces flakiness or simplifies waits.
- What Laravel, Dusk, and PHP versions does this package support?
- Release 1.3.0 adds Laravel 10, Dusk 7, and PHP 8.2 support while requiring at least Laravel 9 and PHP 8.1. Applications on Laravel 8 or PHP 8.0 must stay on 1.2.x or upgrade their platform first. Because the drop was shipped under a minor version, let Composer constraint resolution drive your pin rather than semver intuition.
- Do I need Laravel Dusk to use this package?
- Yes. The package is specifically a Laravel Dusk helper for Inertia.js event testing, so it only fits applications that already run Laravel, Inertia.js, and Dusk for browser-level end-to-end tests. It is not a production runtime dependency and does not replace other E2E layers such as Pest browser testing, Playwright, or Cypress.
- Is this package a production dependency?
- No. It is a test-only helper intended for require-dev use in Dusk browser tests. That limits production runtime and security exposure, but CI reliability and supply-chain hygiene still matter. Keep it pinned and review it like any other dev dependency.
- What Inertia.js events can I assert with this package?
- The package provides Dusk assertions and utilities for verifying that Inertia.js events fire during browser tests. Its surface is intentionally small, so check the README for the exact events and navigation states exposed by the version you pin. Map those assertions to your highest-value Inertia flows before rolling it out broadly.
- Does this package work with Laravel 8 or PHP 8.0?
- No, 1.3.0 drops Laravel versions below 9 and PHP versions below 8.1. If you still need Laravel 8 or PHP 8.0, remain pinned to 1.2.x or block adoption until the platform upgrade. Confirm the full Laravel, Dusk, Inertia.js, PHP, and browser-driver matrix resolves before changing the pin.
- Is protonemedia/inertiajs-events-laravel-dusk maintained?
- Release 1.3.0 arrived after a long gap, so it shows the package is not necessarily abandoned, but one release does not prove a sustainable cadence. Adoption is low, with roughly 23 stars and no dependents listed, so treat it as a small tactical dev-only utility. Re-check the repository's archived status and plan an internal fork or pin if upstream goes quiet again.
- How do I use it in CI with parallel Dusk tests?
- Because it runs inside Dusk browser tests, validate it against your CI browser matrix, timeouts, and any parallel test execution before relying on it. The package has little external validation, so prove compatibility in your own pipeline rather than assuming it. Start with a pinned require-dev dependency on a branch and a couple of representative Inertia navigation tests.
- What are alternatives to this package for testing Inertia.js events?
- If you already use Dusk with Inertia.js, this package is a narrow helper for asserting Inertia events. Teams using Pest browser testing, Playwright, Cypress, or other E2E layers should use those tools' own assertions and waiting strategies instead. It should not be a reason to stay on Dusk if you are evaluating alternatives.
- Can I fork or vendor this package internally?
- The MIT license allows internal forking or vendoring, which is useful for a dev-only helper with low adoption. Pin the version you validate and, if needed, vendor it under an internal namespace with clear ownership. Define a review trigger, such as re-evaluating if no upstream release ships within 12 months.
Weaver
How can I help you explore Laravel packages today?