- What is xplodman/filament-count-up used for?
- It is a presentation-layer Filament package that adds animated count-up effects to numeric stats, KPI cards, dashboard widgets, and table columns. It is intended for admin dashboards and reporting views where visual polish is useful. It does not add persistence, schema changes, or backend domain logic.
- How do I install xplodman/filament-count-up in a Laravel Filament app?
- Install it with Composer using composer require xplodman/filament-count-up. Then follow the package README for any asset publishing or panel/plugin registration and apply its modifier or API to selected Stat widgets or table columns. Test in staging first because registration and asset steps can vary by Filament version.
- Which Filament and Laravel versions does this package support?
- The available package details do not list exact supported Filament, Laravel, PHP, Livewire, or Alpine versions, so confirm them in the README and composer.json. Treat Filament major-version compatibility as something to prove with a short compatibility spike. If your app is on Filament v4 and the package targets v3 only, gate adoption until compatibility is confirmed.
- Does it work with Filament stat widgets and table columns?
- Yes, the package is described as adding count-up effects to Filament stat widgets and table columns. It decorates existing numeric widgets and columns rather than replacing them. Confirm the exact supported widget and column types in the README before applying it broadly.
- What happens if JavaScript or Alpine.js fails to load?
- Because the animation is client-side, the package should ideally degrade to the final static number when JavaScript or Alpine fails. The available technical assessment flags graceful degradation as a key question rather than a documented guarantee. Verify this in a JavaScript-disabled browser test before relying on it in production.
- Does it respect prefers-reduced-motion and accessibility needs?
- Accessibility is a stated risk area: prefers-reduced-motion, screen-reader announcements of intermediate values, and accessible final values should be validated. The package details do not confirm that it handles these automatically. Run accessibility QA with reduced motion enabled and a screen reader before wider rollout.
- How does it behave with Livewire polling, sorting, pagination, and table re-renders?
- Livewire DOM morphing and polling can cause animations to replay, stall, or show stale intermediate values, according to the technical assessment. Test the package on a polling widget and on tables with sorting and pagination. Limit use to surfaces where re-render behavior is acceptable, or disable animation where needed.
- Does it preserve Filament number, currency, and locale formatting?
- Number-format fidelity is a key evaluation point: locale separators, decimals, currency, negatives, large values, and prefixes or suffixes must be preserved. The available details do not guarantee that Filament's existing formatting is retained. Validate representative formatted values in staging before applying the package to financial or reporting widgets.
- Is there performance overhead when using count-up on many table rows?
- Client-side count-up is lightweight for a few dashboard stats, but applying it to many table rows can add rendering overhead. Pilot it on a small dashboard and measure browser impact before expanding to large tables. Consider row-count limits or per-column configuration if performance degrades.
- Is xplodman/filament-count-up maintained and safe for production?
- The package has low adoption, with 9 stars and 0 dependents in the assessment, so treat it as optional UX polish rather than critical infrastructure. Pin an exact version, review the MIT-licensed source, and keep a fork or vendor fallback. Confirm who maintains it and how quickly they respond to Filament upgrade breakage before production use.