- What is chrysanthos/laravel-nova-future-trend used for?
- It is a Laravel Nova card for visualizing trend metrics directly on your Nova dashboard. It gives developers an at-a-glance chart of how key values move over time without writing custom charting code. It is best suited to Laravel applications already using Nova and looking for a simple trend visualization.
- How do I install laravel-nova-future-trend in a Laravel Nova app?
- Install the package with Composer and then register the card in your Nova service provider or dashboard configuration as described in the README. Make sure your application already has Laravel Nova installed and that your Composer constraints allow the package. After registration, clear caches and verify the card appears on the dashboard.
- Does this Nova card support Laravel 11 and Carbon 3?
- Release 1.1.2 explicitly states that it fixes compatibility with Carbon 3 and Laravel 11. That makes it a better fit for applications on or migrating to those versions. You should still confirm your full Composer dependency graph because transitive packages can affect installation.
- Which Laravel and Nova versions are supported?
- The provided release information only confirms compatibility work for Laravel 11 and Carbon 3 in version 1.1.2. It does not document the full supported range for older Laravel, Carbon, or Nova versions. Check the repository README and composer.json before adopting it on older stacks.
- How do I configure the trend metrics shown on the Nova dashboard?
- Configuration is typically handled when you define and register the card in your Nova dashboard setup. The exact options depend on the package API, so follow the README examples for metric definitions and card placement. Start with one metric and expand once the card renders correctly.
- Can I use laravel-nova-future-trend in production?
- It can be used in production if your Laravel and Nova versions are compatible and you have validated it in staging. Because the 1.1.2 release involves Carbon 3 and Laravel 11 compatibility, treat date and timezone behavior as a regression-test area. Pin the version, run your test suite, and keep a lock-file rollback path.
- How should I test this Nova trend card after upgrading to Laravel 11?
- Run your normal application test suite plus focused checks around date parsing, time zones, scheduling, and reporting where trend values are calculated. Verify the card in staging with representative data and user permissions. Add a small regression test if the dashboard metric is business-critical.
- What are some alternatives to laravel-nova-future-trend?
- Laravel Nova includes native metric and trend cards that may cover simple dashboard needs without an extra package. You can also build a custom Nova card or use other community charting cards. Compare maintenance activity, Nova version support, and whether you need this specific trend visualization.
- Is chrysanthos/laravel-nova-future-trend actively maintained?
- The release information indicates maintenance around Laravel 11 and Carbon 3 compatibility, which is a positive signal. However, the release note is brief and does not provide a full history or support policy. Check the repository issue tracker, recent commits, and release cadence before relying on it long term.
- What risks should I check before upgrading to version 1.1.2?
- The main risks are Composer dependency conflicts, Carbon 3 behavioral differences around dates and time zones, and Laravel 11 deprecations. Upgrade in a branch, refresh the lock file, and run CI plus staging validation before production. If something breaks, rollback is usually straightforward by reverting the package version and lock file.