Laradumps Filament Laravel Package

Product Decisions This Supports

• Developer velocity on admin/internal tooling. This package is a Filament plugin that wires Filament's form/Livewire state into LaraDumps, so debugging complex admin forms (multi-step wizards, repeaters, conditional fields) stops being guesswork. The v1.4.0 addition of a DumpFormState attribute extends that from ad-hoc ds() calls to declarative, per-field state logging — a meaningful DX upgrade for teams building non-trivial Filament resources.
• Build vs. buy: buy (adopt free OSS). The capability is narrow and non-differentiating. Replicating it internally means maintaining a Filament-version-coupled debugging shim — poor use of engineering time.
• Roadmap signal, not a roadmap item. Adoption is a team tooling decision, not a customer-facing feature. It should be tracked under engineering enablement / internal DX budgets, evaluated alongside Ray, Telescope, and Clockwork rather than in the product backlog.
• Support and onboarding cost. Faster form debugging shortens ramp-up for engineers new to Filament/Livewire and reduces "can't reproduce in staging" support loops.
• Risk surface is a decision input. A single-maintainer, dev-only package means the real PM decision is containment: dev-only dependency, version pinning, and a documented fallback (ds() calls or Telescope) if it goes stale.

When to Consider This Package

Consider adoption when:

• The team already runs Filament (v3+) and LaraDumps in local/staging environments.
• Engineers routinely debug Filament form state — repeaters, afterStateUpdated hooks, wizard steps — where browser devtools and dd() are slow or destructive.
• You want zero-config, declarative instrumentation (attributes on form/field classes) instead of scattering temporary ds() calls that leak into commits.
• The team accepts small-team OSS with a low bus factor and is willing to pin versions and review upgrades.

Look elsewhere when:

• LaraDumps isn't already part of the stack — adopting a second debug tool for one attribute isn't justified; use Ray, Telescope, or Clockwork.
• You need production-grade observability, tracing, or error aggregation — this is a local DX tool, not monitoring.
• The project isn't on Filament, or is on a Filament major version the plugin doesn't yet track.
• You require vendor SLAs, security review artifacts, or long-term maintenance guarantees.
• Strict dependency governance: verify the package is confined to require-dev and cannot ship to production builds.

Immediate action for v1.4.0: treat as a low-risk additive feature. No breaking changes signaled. Confirm the attribute is inert outside local/debug contexts before rolling out, and pin to ^1.4 if adopted.

How to Pitch It (Stakeholders)

To executives: This is a free, open-source developer tool that makes our Filament admin panels faster to debug and cheaper to maintain. The new release adds declarative form-state logging, which trims time spent chasing UI/state bugs in internal tooling. Cost is zero in licensing; the only commitment is a dev-only dependency we can drop at any time. Recommendation: approve as a team-standard dev dependency, not a product initiative.

To engineering leads: Drop-in Filament plugin that surfaces form and Livewire state in LaraDumps. v1.4.0 adds a DumpFormState attribute so instrumentation lives on the field definition instead of in throwaway ds() calls — cleaner diffs, less accidental leakage into PRs. Keep it in require-dev, pin the minor version, and note the single-maintainer risk with a fallback to Telescope or manual ds() if maintenance lags.

To security/platform: Dev-only, no runtime dependency in production. Verify it stays out of production autoload/build artifacts and review the dependency tree on each minor bump.