Nova Apex Chart Laravel Package

Product Decisions This Supports

• Build vs. buy vs. fork for admin analytics. This package is best framed as a reference implementation, not a dependency. It answers "how cheaply can we put real charts into our Nova admin?" — realistically a 3–5 day internal fork versus ~2–3 weeks building a custom Vue card around ApexCharts from scratch. That delta is the decision.
• Dashboard scope on an existing Nova surface. Nova's native metrics (value, trend, partition) are deliberately minimal. This package informs whether richer visualizations — multi-series, mixed bar/line, radial, heatmaps, sparkline-style KPI cards — are worth adding to an internal ops/back-office panel.
• Roadmap sequencing for internal tooling. If Nova is already the admin layer, charting is a low-effort, high-visibility improvement for support, ops, and account teams. Good candidate for a "polish" sprint rather than a roadmap line item.
• Concrete use cases to scope against: revenue and order trends by cohort, per-tenant usage/quota dashboards, support ticket volume vs. resolution time, funnel/mix breakdowns, and KPI cards with a 30/90-day trend.
• A negative decision it also supports: whether any 7-star, single-maintainer package should sit in your production dependency graph. Here the answer is "as vendored source, yes; as a Composer requirement, no." That distinction is the reusable policy.

When to Consider This Package

Adopt (as a fork or vendored starting point) when:

• You are already running Laravel Nova and the version is confirmed compatible — note the last release is 2020-07-24, i.e. Nova 2.x/3.x era. Verify against your Nova major and the ApexCharts version it bundles before promising anything.
• The audience is internal only: staff dashboards, back-office, a customer-success console. No external SLA, no tenant-facing surface.
• You need ApexCharts-specific chart types that Nova's native metrics genuinely cannot express.
• You have engineering capacity to own the code: read it, pin it, fork it, patch it. Assume you are the maintainer on day one.
• It is a timeboxed proof of concept to validate that charting drives adoption of the admin panel before you invest in a proper build.

Look elsewhere when:

• You are on Nova 4/5, PHP 8+, or a recent Laravel. A 2020 card almost certainly needs porting work; budget for it or skip.
• Analytics is customer-facing or a revenue feature — that is a BI/embedding problem (Metabase, Redash, Cube, PostHog), not a Nova card problem.
• You need maintained support, security patching, or active issue triage. With 7 stars, 0 dependents, and no release in ~5 years, there is no ecosystem validation and no signal of ongoing stewardship.
• Alternatives worth pricing first: Nova's native metric cards (free, supported), coroowicaksono/nova-chartjs or similar Chart.js integrations, or a custom Vue card wrapping ApexCharts directly — often the same effort as forking this, with no inherited debt.
• Any situation where "who fixes this when it breaks during a quarter-end reporting crunch?" has no named answer.

How to Pitch It (Stakeholders)

To executives: This is a small, MIT-licensed accelerator for our internal admin dashboard — it lets us add professional-grade charts for roughly a few days of engineering instead of a few weeks. The caveat is stewardship: the project is effectively unmaintained (last release 2020, negligible adoption), so we would adopt it as internal source code we own, not as a vendor-supported dependency. Low cost, low risk to customers, and it does not touch the core product.

To engineering: Thin MIT wrapper that exposes ApexCharts as a Nova card you configure with series and options. ApexCharts itself is mature and well-documented; the wrapper is the fragile part. Recommendation: do not add it as a live Composer requirement — fork or vendor it, pin the ApexCharts version, add a compatibility test against our Nova version, and record it in the tech-debt register with an explicit exit path (replace with a first-party Vue card when we next touch the admin layer). If we are on Nova 4+, scope the port before committing.