Composed Chart

Bars, lines and areas on one plot in one unit: actual, plan and forecast together, with a reference rule.

PROGet Composed Chart and 168 other Pro components with pro lifetime — Get Pro

Category
Data & feedback
Access
Pro
Source
202 lines · one file
States
5 drawn

The decision inside it

One axis, on purpose

A second y-scale lets two unrelated lines cross wherever the ranges say, and readers take the crossing as meaning. Different units are two charts, and syncId moves their tooltips together.

When to use it

Use Composed Chart to put bars, lines and areas in the same unit on one plot, such as revenue as bars, plan as a line and forecast as an area, with an optional reference rule. It has one y-axis; different units belong in two charts with the same syncId.

Installation

How you get it

Paste this into Claude Code, Cursor, Codex or any coding agent. It installs the file and uses it as it is, instead of writing a new one.

Use Liro's Composed Chart for this.
Install it: npx shadcn@latest add @liro/composed-chart
(the @liro registry is set up in components.json, with LIRO_KEY in .env.local)
Import it from @/components/ui/composed-chart.
Do not rewrite or restyle it. Pass my data through its props
and keep its built-in states.

For the full brief with every prop and the mistakes assistants usually make, use Copy prompt above. Pro components install through the @liro registry with your CLI token: see the Namespaced tab.

Usage

components/revenue-plan.tsx
import { ComposedChart } from "@/components/ui/composed-chart";

const data = [
  { month: "Aug", revenue: 12100, plan: 11500, forecast: 12900 },
  { month: "Sep", revenue: 13600, plan: 12000, forecast: 14300 },
  { month: "Oct", revenue: 14200, plan: 12500, forecast: 15000 },
];

export function RevenuePlan() {
  return (
    <ComposedChart
      data={data}
      xKey="month"
      format={(v) => "$" + (v / 1000).toFixed(1) + "k"}
      reference={{ value: 12000, label: "Break-even" }}
      description="Revenue against plan and forecast"
      series={[
        { key: "forecast", label: "Forecast", kind: "area" },
        { key: "revenue", label: "Revenue", kind: "bar" },
        { key: "plan", label: "Plan", kind: "line", dashed: true },
      ]}
    />
  );
}

API reference

“Copy prompt” above puts a full brief on your clipboard, install command, dependencies, props, and the mistakes an assistant usually makes with this component.

Props

Read from the component’s own TypeScript interface when the site is built, so this table cannot drift from the file you install.

TypeNotes
dataT[] Yes–
xKeykeyof T & string Yes–
seriesComposedSeries[] Yes–
reference{ value: number; label: string } NoA labelled horizontal rule: a goal or a limit.
stackedboolean NoStack the bars. Default false.
syncIdstring NoSame id on two charts syncs their tooltips.
format(v: number) => string No–
xFormat(v: string) => string No–
heightnumber No–
descriptionstring YesAccessible summary, read before the data table.
loadingboolean No–
errorReact.ReactNode No–
onRetry() => void No–
classNamestring No–

Dependencies

npm packages

clsxrechartstailwind-merge

Liro foundations, installed alongside it

liro-themechart

States

All of them are drawn by the component. None is left for you to design.

  • Bars, line and area
  • Reference rule
  • Loading
  • Empty
  • Error

Accessibility

  • Keyboard reachable throughout, in visual order
  • Focus trapped in overlays, Escape closes them
  • Focus returns to whatever opened it
  • Live regions announce what changed, not that something did
  • Honours prefers-reduced-motion

Responsive behavior

  • Sizes to its container, not the viewport
  • Usable from 320px up
  • Pointer-based interaction, so trackpad and touch both work
  • No hover-only affordances