- What does joshhanley/livewire-checksum-logger do?
- It adds visibility to Livewire checksum failures by logging them with useful request and component context instead of leaving you with only a generic exception. This makes corrupted, stale, or tampered Livewire payloads easier to trace back to the component or request that triggered them. It is a lightweight Laravel package with an auto-discovered service provider, so integration is intended to be drop-in.
- How do I install livewire-checksum-logger in a Laravel app?
- Install it with Composer using composer require joshhanley/livewire-checksum-logger. Laravel package auto-discovery should register the service provider without manual changes to config/app.php. Before installing, check the repository README and composer.json for the exact configuration steps and supported Laravel versions, since the package is still pre-1.0.
- Which Laravel and PHP versions does this package support?
- The available changelog notes that Laravel 9 support was added in v0.0.3, and Laravel 9 itself requires PHP 8.0 or newer. There is no confirmed support matrix for Laravel 10, 11, or 12 in the information provided, so inspect the illuminate/* constraints in composer.json before assuming compatibility. If you are on Laravel 8, verify that v0.0.3 did not drop support, because an added feature is not proof of backward compatibility.
- How do I configure the log channel and log level for checksum failures?
- The package advertises a configurable logging channel and log level, so you can route checksum failures to a dedicated channel rather than your default application log. Check the README for the exact config file, keys, or environment variables exposed by the package. Once configured, confirm entries appear with the request and component context you expect.
- Does livewire-checksum-logger require manual service provider registration?
- No, the package overview states it ships an auto-discovered Laravel service provider, so manual registration in config/app.php should not be necessary on supported Laravel versions. If your application disables package discovery, you would need to register the provider manually. You can confirm the discovery setup by checking the extra.laravel.providers entry in the package composer.json.
- Why am I getting a Livewire checksum mismatch and how does this package help?
- A Livewire checksum mismatch means the checksum sent with a payload does not match what the server expects, which can happen with corrupted, stale, or tampered requests. By default this often surfaces as a generic exception with little diagnostic detail. This package logs the failure with request and component context so you can identify which component or request caused the mismatch and investigate further.
- Is it safe to use a 0.0.x package like this in production?
- Pre-1.0 versioning means there is no public API stability guarantee, and breaking changes are permitted in any release, including patch releases. If you use it in production, pin an exact version and review each update before upgrading. Because it is a logging helper rather than request-path middleware, the blast radius is likely smaller, but you should still validate behavior in your own environment.
- How can I test that Livewire checksum failures are being logged?
- Trigger a checksum failure in a test by tampering with a Livewire payload or sending a modified request to a component endpoint. Then assert that the expected log entry was written, for example by faking a log channel or spying on the logger. Verify that the captured context includes the request and component details you rely on for debugging.
- What are alternatives to using livewire-checksum-logger?
- Livewire throws an exception on checksum failures, so you can catch and log those exceptions yourself in Laravel's exception handler or a custom listener. That approach gives you full control but requires more code and maintenance. This package is essentially a convenience wrapper that adds context to those failures, so it is reasonable to reimplement the small surface area if you prefer fewer dependencies.
- Who maintains livewire-checksum-logger and what if maintenance stops?
- The package is published under the joshhanley namespace, but the available information includes only a thin changelog and no issue-tracker, download, or release-cadence data. Before adopting it, check the repository's recent commits, open issues, CI matrix, and license to assess maintenance health. Because the functionality is small and focused on logging, vendoring or reimplementing the behavior in an exception handler is a practical fallback if maintenance stops.