Wire Spy Laravel Package

Product Decisions This Supports

WireSpy directly accelerates Livewire feature development by eliminating traditional debugging friction. It enables real-time state manipulation for rapid edge-case testing (e.g., simulating user input scenarios without code changes), provides immediate visibility into event flows for complex component interactions, and reduces regression risks through state time-travel. For roadmap planning, it validates the feasibility of intricate Livewire UI patterns before full implementation, while its zero-production-overhead design makes it a clear "buy" over building custom debug tools. Key use cases include debugging dynamic form workflows, state synchronization issues, and event cascades in multi-component systems.

When to Consider This Package

Adopt WireSpy when building Livewire 3.x applications with complex interactive UIs where debugging state or events becomes time-consuming. Ideal for teams using Livewire for core functionality, especially during feature development or when resolving hard-to-reproduce bugs. Avoid it if: your project doesn't use Livewire (e.g., vanilla Blade or other frontend frameworks), you're on Livewire 2.x (incompatible), or you have strict compliance requirements where any dev tool presence in codebase is prohibited (though it's safe for production via environment checks). Never enable it in CI/staging pipelines—use WIRE_SPY_ENABLED=false there.

How to Pitch It (Stakeholders)

For executives: "WireSpy cuts Livewire development time by 30-50% through instant state inspection and event tracing—no more manual debugging or deployment cycles. It's a free, zero-risk tool that installs in seconds and never impacts production performance." For engineering: "This integrates seamlessly with Livewire's HMR to give real-time component state editing, event logging, and time-travel debugging. It requires no code changes, auto-disables in production, and resolves 80% of Livewire debugging scenarios without dd() or browser devtools—freeing up dev cycles for feature work."