- What is gsferro/odometer-easy used for in Laravel?
- It is a Laravel package that wraps the hubspot/odometer JavaScript library to render animated numeric counters in Blade views. It is intended for presentation-layer use such as dashboards, KPI tiles, and landing pages. It does not handle data storage, queues, or business logic.
- How do I install gsferro/odometer-easy?
- Install it with Composer using composer require gsferro/odometer-easy, then publish its assets with php artisan vendor:publish. The exact provider and publish tag are not documented in the available metadata, so confirm them from the package source or README. Test the install in a scratch Laravel app matching your version first.
- Which Laravel and PHP versions does gsferro/odometer-easy support?
- Version constraints are unverified in the available assessment. The package metadata does not confirm tested Laravel or PHP ranges. Inspect composer.json and pin the package explicitly against your Laravel minor and PHP runtime before adopting.
- How do I add an animated counter in a Blade view with odometer-easy?
- The package is described as a thin convenience layer, likely exposing a Blade directive or helper that emits a span with the odometer class and a value. The overview mentions easy configuration for values and formatting. Confirm the exact syntax from the source or README in a sandbox.
- Do I need to publish JS assets for odometer-easy?
- The assessment describes a publishable JavaScript asset and a vendor:publish step. You will need to publish or otherwise include the odometer JavaScript so counters animate. Reconcile that with your Vite or asset pipeline, since you may end up re-bundling the asset anyway.
- Does odometer-easy bundle hubspot/odometer, and does it add jQuery?
- It is described as a wrapper around hubspot/odometer, but whether it bundles upstream as-is or a fork is unverified. The evaluation lists transitive front-end dependencies, including possible jQuery, as an open question. Inspect the published asset and package files before adopting.
- Does gsferro/odometer-easy have tests or test coverage?
- Test coverage is not verified in the provided assessment. Adoption signals are weak: one star, zero dependents, and a single maintainer. Treat missing tests and documentation as a risk and validate behavior in your own sandbox.
- Is gsferro/odometer-easy safe for production use?
- It is a presentation-only package with a very small surface area, but the evaluation rates technical risk high relative to that surface. Weak adoption, a Portuguese-only description, and unverified constraints are decay risks rather than runtime bugs. If adopted, vendor and pin the asset, and do not make it load-bearing for production-critical UI.
- Can I use gsferro/odometer-easy with Laravel Vite?
- The assessment says the package likely predates or ignores modern Laravel build tooling. Published assets may need to be reconciled with Vite or re-bundled. A direct npm or Vite import of upstream odometer is a viable alternative.
- What are alternatives to odometer-easy, and how do I uninstall it?
- Alternatives are a CDN script tag for hubspot/odometer or a Vite/npm import of upstream odometer directly. Uninstall is composer remove plus removing any published assets, though a documented uninstall path is not confirmed. Migration cost in either direction is low, roughly a 30-minute swap.