Weave Code
Charts Laravel Package
orchid/charts
Chart widgets for the Laravel Orchid admin platform, adding Chart.js-powered visualizations to screens and dashboards via simple layout fields.
orchid/charts is a Laravel package that brings interactive, responsive charts to the Orchid Platform admin panel. Charts are defined as simple PHP classes and rendered as dashboard widgets, with data supplied from Eloquent queries, arrays, or custom sources.
- Built on Chart.js with line, bar, pie, and doughnut types
- Fluent PHP API for labels, datasets, and styling
- Drop-in dashboard widgets for any admin screen
- Configurable axes, colors, tooltips, and legends
- Seamless integration with Laravel models and queries
Frequently asked questions about Charts
- What is orchid/charts used for in Laravel?
- orchid/charts is a Laravel package for adding chart widgets to Orchid Platform admin screens. It lets you define line, bar, pie, and other charts as dashboard widgets with configurable datasets, labels, and options. The package is described as PHP-first server-side SVG rendering with zero JavaScript runtime, although you should verify that against the published artifact before relying on it.
- How do I install orchid/charts with Composer?
- The intended install path is Composer: require orchid/charts in a Laravel application that already uses Orchid Platform. Because the v0.0.10 release notes focus on maintenance and toolchain updates, confirm the README for any service provider, config, or asset publishing steps. Pin the version and test the install in a non-critical admin screen first.
- Is orchid/charts a Composer package or a JavaScript npm package?
- The package is listed as orchid/charts on Composer and described as PHP-first server-side SVG charts for Laravel Orchid. However, the v0.0.10 release notes describe a JavaScript and Node toolchain, so the registry and install mechanism must be confirmed. If it is frontend-consumed, install it through npm and Vite, not as a Composer runtime dependency.
- Which Laravel and Orchid Platform versions does orchid/charts support?
- The provided release information for v0.0.10 does not state PHP, Laravel, or Orchid Platform version constraints. Check the package composer.json and README for the actual support matrix before planning an upgrade. At a 0.0.x version, semver guarantees do not apply, so treat version compatibility as something you verify rather than assume.
- Is orchid/charts production-ready at v0.0.10?
- v0.0.10 is a maintenance release with no new features, no public API changes, and no deprecations, so it is safe to adopt on its own terms. The caution is that it is pre-1.0: semver guarantees do not apply, and the project stability policy and release cadence are not established in the provided context. Start with a scoped pilot in an admin dashboard rather than a business-critical surface.
- What chart types and configuration options does orchid/charts support?
- You can define line, bar, pie, and other chart widgets for Orchid admin dashboards. Charts are configured with datasets, labels, and options for responsive visual dashboards. The exact option surface is not spelled out in the v0.0.10 release notes, so consult the README and source, and pin the version while testing your chart configurations.
- Does orchid/charts render server-side SVG or use Chart.js in the browser?
- The package summary says PHP-first server-side SVG charts with zero JavaScript runtime, while the blurb calls them Chart.js-powered widgets. Those descriptions imply different rendering models, so check the published artifact and README to see whether charts are generated as SVG in PHP or drawn by Chart.js in the browser. This determines whether backend or frontend owns the widget.
- Does orchid/charts have known security advisories?
- The v0.0.10 security notes patch brace-expansion to 5.0.12 and fast-uri to 3.1.8. The braces advisory GHSA-vfj7-8cjw-p6xm remains unpatched transitively through Stylelint, but these findings are dev-only and the published artifact is described as having no runtime dependencies. That keeps advisories out of production code, though CI and build machines can still be exposed and scanners may keep flagging the transitive issue.
- Can I use orchid/charts with Laravel Vite and an existing frontend build?
- If the package is consumed as a frontend asset, it should install alongside Laravel's default Vite setup, but you need to reconcile its Vite 8.3.2 and ESLint 10.x baselines with your app pins. Dev dependencies are not installed for consumers of a published artifact, so those baselines do not have to match unless you build from source. If it is a true Composer package, Vite is not part of the integration path at all.
- What should I verify before adopting orchid/charts, and what are the alternatives?
- Confirm the ecosystem first: is this a PHP Composer package for Orchid or a JavaScript package consumed through npm and Vite? Also check whether it ships a prebuilt dist artifact, where tooltips render, its pre-1.0 stability policy, and whether your security gate blocks dev-dependency advisories. Alternatives include building custom Orchid widgets around Chart.js or using a server-side SVG chart library if you need to avoid JavaScript entirely.
Weaver
How can I help you explore Laravel packages today?