Lottie Laravel Package

Product Decisions This Supports

• Feature-level polish, not a roadmap item. This is a Filament form/table component that renders Lottie (JSON vector animation) inside the admin panel. It supports decisions like "do we add animated empty states, success confirmations, onboarding illustrations, or loading indicators to the admin UI?" — a delight/UX-consistency decision, not a platform bet.
• Build vs buy. The buildable surface is small (a Blade view, an asset registration, a Filament asset-pipeline hook), so "buy" is justified mainly by avoided maintenance of that glue across Filament upgrades, not by capability. Reasonable buy call at zero/low license cost; revisit if the wrapper lags Filament major versions.
• Asset strategy: Lottie vs GIF/video. JSON animations are small, resolution-independent, themeable, diff-able in git, and work offline — the right choice for admin UI motion where you don't want binary media in the repo or CDN dependencies.
• Dependency-surface decision. The package consolidates under visualbuilder/filament-*, signalling a maintained family rather than a one-off. That's a mild positive for "is this a dependency we can live with for 2 years?"
• Not supported by this release: any decision about customer-facing/anonymous surfaces (use lottie-web or a player directly there) or about motion design ownership (After Effects → JSON pipeline is a design-ops commitment this package does not make for you).

When to Consider This Package

Adopt when:

• You are already on Filament and want motion in panels without hand-rolling a Blade component and asset registration.
• You want animations versioned as JSON in the repo rather than as GIF/video assets.
• You can tolerate a small-vendor, single-namespace package in a non-critical UI layer.

Criteria / gates before adoption:

• Beta gate. 5.0.0 is still pre-release (-beta.2). Treat as a spike until 5.0.0 stable ships; do not put it on a production admin panel on a beta.
• Compatibility check. Confirm the v5 line's supported Filament and PHP versions against your app — this is the single most likely reason to walk away.
• Rename handling (new in this release). The Composer name changed from visualbuilder/lottie to visualbuilder/filament-lottie. PHP namespace Visualbuilder\Lottie and all class names are unchanged, so no application code changes are required; but composer.json, the lockfile, CI caches, and any internal docs/SBOM entries must be updated. Existing installs need composer remove visualbuilder/lottie alongside the new require.
• Security note (new in this release). The esbuild advisory (GHSA-67mh-4wv8-2f99) is a dev-tooling issue in the package's own build chain; it never reaches runtime for consumers. The bump closes Dependabot noise and protects anyone running npm install in the package repo — not a reason to expedite or delay your rollout.

Look elsewhere when:

• You need motion outside Filament (public site, emails, mobile) — use a player directly.
• A CSS/SVG transition would do; Lottie is overkill for fades and spinners.
• Your policy requires stable-only or actively-maintained-by-multiple-contributors dependencies for admin surfaces.
• You need guaranteed long-term support SLAs — nothing here suggests that, and the mid-beta rename is evidence of naming churn.

How to Pitch It (Stakeholders)

To executives: A small, low-cost UI package that lets us add lightweight, high-quality animation to the internal admin app without shipping video or heavy image assets. It is pre-1.0-stable and has a single vendor, so I'm recommending we pilot it on a non-critical screen rather than commit it to the platform baseline. The security item in this release is in the package's build tooling, not in anything we run in production — no exposure to us.

To engineering: Upgrade is mechanical. The Composer package name moved to visualbuilder/filament-lottie as part of a family-wide rename; the PHP namespace and class names are untouched, so use Visualbuilder\Lottie\Components\Lottie; still compiles. Work is: swap the requirement in composer.json, composer remove the old name, refresh the lockfile and CI caches. The esbuild bump is dev-only and has no runtime effect. Remaining risk is Filament version compatibility and beta API stability — pin the exact beta, and budget a review pass when 5.0.0 stable lands.