Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Nova Charts

Nova Charts Laravel Package

vemcogroup/nova-charts

A Laravel Nova package for adding charts and dashboard cards, helping you visualize metrics and build custom analytics widgets with a simple API.

View on GitHub
Deep Wiki
Context7

A Laravel Nova card to show charts from the Chart.js library.

Frequently asked questions about Nova Charts
What is vemcogroup/nova-charts used for?
It is a Laravel Nova card package for showing charts from the Chart.js library. Developers use it to visualize metrics and build custom analytics widgets directly inside Nova dashboards. It is not a general-purpose charting library; its value depends on already using Nova as your admin layer.
How do I install vemcogroup/nova-charts in a Laravel Nova application?
Install it through Composer and follow the package publishing steps for configuration and front-end assets. Integration typically involves confirming Composer constraints, Nova version requirements, PHP version, and any asset build requirements. After publishing, clear caches and smoke test your dashboards.
Does nova-charts 4.0 support Laravel 9 and Nova 4?
Version 4.0 is a major release aligned with Laravel 9 and is intended for Nova 4 compatibility. The release notes are minimal, so verify the exact Composer constraints and Nova requirements before upgrading. If you are still on Laravel 8 or Nova 3, this release is not applicable without a platform upgrade.
Is nova-charts 4.0 compatible with Laravel 8 or Nova 3?
It is unlikely to be compatible, because 4.0 is a major release aligned with Laravel 9 and likely Nova 4. Applications on Laravel 8 or Nova 3 should stay on the prior pinned version, such as 3.0.4, until the platform upgrade is complete. Treat this as a platform-coupled upgrade rather than a drop-in patch.
What are the breaking changes in vemcogroup/nova-charts 4.0?
The release note is sparse, but likely breaking changes include dropped Laravel 8 and Nova 3 support, dependency constraint changes, and possible chart definition or API changes. Review the GitHub compare diff and composer.json before merging. Confirm that existing chart classes, metrics, and dashboard definitions still work.
How do I safely upgrade nova-charts from 3.0.4 to 4.0?
Pin the current 3.0.4 version first, then upgrade Laravel and Nova in a branch before updating nova-charts to ^4.0. Review the diff for custom chart compatibility, re-publish assets and config if required, and run dashboard smoke tests. Compare chart output before production rollout and keep a rollback path to the prior pinned version.
Do I need to publish assets or configuration after installing nova-charts?
Yes, Nova chart packages commonly require publishing configuration and front-end assets as part of installation. Follow the package README for the exact publish commands and confirm whether asset publishing changes in 4.0. After upgrades, re-publish assets if needed and clear caches to avoid missing config or rendering issues.
How should I test nova-charts dashboards before production?
Run visual and functional regression tests on every dashboard in staging, not just a single chart. Confirm that custom chart classes, metrics, and dashboard definitions render correctly after the Nova and package upgrade. Use a feature flag or staged release with a rollback plan if chart rendering is business-critical.
What production performance concerns come with nova-charts?
Chart rendering is typically client-side through Chart.js, but dashboard performance is usually bound by the queries behind the charts. Watch for expensive aggregate queries, large date ranges, and dashboard load concurrency. Cache chart data where possible and avoid using these charts as a real-time reporting layer without query tuning.
Is vemcogroup/nova-charts actively maintained and what alternatives exist?
It is a community or maintainer-supported package with no enterprise SLA implied, and the minimal 4.0 release notes increase the need for internal upgrade documentation. Alternatives include building custom Nova cards or using a separate charting or BI layer, depending on your reporting needs. For Nova-based admin panels, the package remains a lightweight option when pinned and tested deliberately.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console
pnscripts/filament-broadquill-lite
pnscripts/laravel-sentfold-lite
vleap/mx-sdk-laravel-internal
twidpay/utils
htetmyathlaing/scout-elasticsearch-driver
artisan-toolbox/front-awesome
ls/client-assistant
users-au/laravel-client
cgv/localized-resource
noith/settings
kda/laravel-package
kda/filament-dynamic-navigation
bypersoft/signbox
pairus/product-data
fayne/laravel-filament-cms-core
nodisrupt/laravel-agent
sierratecnologia/media-manager