Weave Code
Charts Laravel Package
zaimealabs/charts
zaimealabs/charts is a Laravel/PHP charting package for creating and rendering charts with a simple, expressive API. It helps turn datasets into clear visualizations for dashboards, reports, and app views.
zaimealabs/charts is a lightweight Laravel package for building interactive, responsive charts with a clean, fluent PHP API. It integrates smoothly with Blade, letting you define datasets, labels, and options in PHP and render ready-to-use chart components without frontend boilerplate.
- Fluent, chainable chart configuration
- Support for common chart types such as line, bar, and pie
- Blade component and direct rendering support
- Customizable datasets, labels, colors, and options
- Lightweight frontend integration with sensible defaults
Frequently asked questions about Charts
- How do I install zaimealabs/charts in a Laravel app?
- Install it with composer require zaimealabs/charts. Laravel package discovery should register the service provider automatically, then run vendor:publish to publish any config and front-end assets. Confirm the exact publish tags in the README before wiring it into views.
- Which PHP and Laravel versions does zaimealabs/charts support?
- The 1.0 release notes do not list supported PHP or Laravel ranges, so check composer.json and the README before adopting it. Treat version constraints as unverified until you confirm them in a test application. Pin to ^1.0 and run your own compatibility check.
- Does zaimealabs/charts work with Livewire?
- Livewire support is not confirmed in the available release notes. Because ApexCharts is JavaScript-backed, verify that charts re-render correctly after Livewire morphs before using it in reactive components. Test the actual update path rather than assuming one-shot rendering will work.
- Is zaimealabs/charts compatible with Inertia.js?
- Inertia compatibility is not documented in the provided materials. In practice you would pass serialized chart configuration as props and re-initialize on navigation. Confirm client-side initialization behavior before choosing it for an Inertia pilot.
- Does zaimealabs/charts load ApexCharts from a CDN or bundle the assets?
- The available notes do not state whether assets are bundled, published, or CDN-loaded. That choice affects CSP rules, offline behavior, and asset versioning. Check the README and published assets before deploying to a locked-down production environment.
- How do I publish zaimealabs/charts config and assets?
- Use Laravel's vendor:publish command after requiring the package. The package is described as having publishable config and front-end assets, but the exact tags are not listed in the release notes. Run php artisan vendor:publish and select the zaimealabs/charts provider or tag shown in the README.
- Is zaimealabs/charts stable enough for production?
- The 1.0 tag signals a stable public API and SemVer commitment, but the release contains no functional changes beyond dependency bumps. The package is maintained by a single organization with bot-only external contributions, so continuity risk is high. Pin to ^1.0 and cover chart output with your own contract tests.
- Can I test chart rendering from zaimealabs/charts?
- The release notes do not describe a test matrix or documented test types. For your own coverage, assert the generated markup or chart configuration rather than trying to render ApexCharts in PHP unit tests. Treat the chart output as a contract you control.
- Does zaimealabs/charts render charts server-side?
- The package is described as an ApexCharts integration, which is typically client-side JavaScript rendering. The available notes do not confirm server-side SVG or PNG output. Verify renderer behavior before assuming server-rendered charts or CSP-safe output.
- How is zaimealabs/charts maintained and what are the security risks?
- The repository is single-maintainer and Dependabot is configured for GitHub Actions only, not runtime Composer dependencies. That means transitive PHP vulnerability updates are not automated by the maintainer. Run your own dependency scanning and keep the package behind an internal abstraction to reduce swap cost.
Weaver
How can I help you explore Laravel packages today?