BumpChart
Show sequence, schedule or attribution over rows you prepared.
@luc/ui/chartsWhat it shows
Show how ranks change across ordered periods, where a crossing is more important than the absolute level.
Live preview
Ranks per quarter with an explicit null where a series was not scored — a gap, never a zero.
<BumpChart
periods={["Q1", "Q2", "Q3", "Q4"]}
series={[
{ label: "Momentum", tone: "warning", ranks: [1, 1, 2, 3] },
{ label: "Value", tone: "positive", ranks: [3, 2, 1, 1] },
{ label: "Carry", tone: "accent", ranks: [2, 3, 3, 2] },
{ label: "Quality", tone: "neutral", ranks: [4, 4, null, 4] },
]}
rankLabel="Rank"
height={320}
ariaLabel="Rank by quarter"
/>Controls
Height
A chart measures its container, so it always needs a definite height.
State
The surface the chart is in — loading, empty and error are drawn by the component.
Accessible name
A drawing is not readable by a screen reader, so it needs a name that states what it shows.
The same fixture as the live preview above; the controls change how it is drawn, not what it measures.
Code
import { BumpChart } from "@luc/ui/charts";
<BumpChart
periods={["Q1", "Q2", "Q3", "Q4"]}
series={[
{ label: "Momentum", tone: "warning", ranks: [1, 1, 2, 3] },
{ label: "Value", tone: "positive", ranks: [3, 2, 1, 1] },
{ label: "Carry", tone: "accent", ranks: [2, 3, 3, 2] },
{ label: "Quality", tone: "neutral", ranks: [4, 4, null, 4] },
]}
rankLabel="Rank"
height={320}
ariaLabel="Rank by quarter"
state="ready"
/>Not controllable here
series / rows— The numbers are the caller's; the fixture above is the example.
Copy for an AI agentA specification an agent can act on: the import, the setup, the chosen props, the data contract and the accessibility expectation.
Implement `BumpChart` from Luc UI. It is: Show sequence, schedule or attribution over rows you prepared.
Import it with: import { BumpChart } from "@luc/ui/charts";
Requires: react ^19.0.0; react-dom ^19.0.0; react-hook-form ^7.0.0 (optional, for @luc/ui/forms/react-hook-form); tailwindcss ^4.0.0; node >= 22 (repository tools). Import the stylesheet once at the app root and wrap the tree in `LucProvider`. Both come from the package that publishes @luc.
Chosen configuration: `height={320}`, `state="ready"`, `ariaLabel="Rank by quarter"`.
Accessibility: keep the component's own semantics. Do not re-implement its ARIA wiring, do not add roles it does not declare, and make sure every interactive element is reachable and operable from the keyboard with a visible focus state.
Styling: use Luc UI design tokens and the component's own props. Do not restyle with raw colour literals and do not override the component's internal structure with page CSS.
Motion: respect `prefers-reduced-motion`. The component already does, so do not disable it.
Reproduce this state:
```tsx
<BumpChart
periods={["Q1", "Q2", "Q3", "Q4"]}
series={[
{ label: "Momentum", tone: "warning", ranks: [1, 1, 2, 3] },
{ label: "Value", tone: "positive", ranks: [3, 2, 1, 1] },
{ label: "Carry", tone: "accent", ranks: [2, 3, 3, 2] },
{ label: "Quality", tone: "neutral", ranks: [4, 4, null, 4] },
]}
rankLabel="Rank"
height={320}
ariaLabel="Rank by quarter"
state="ready"
/>
```Usage
The values are prepared by the caller: this component draws the points it is given and computes no statistic of its own, so units, scaling and any summary have to be settled before the data reaches it.
It is drawn by the ECharts engine.
Worked examples with real data are on the family overview: Workflow & operations
import { BumpChart } from "@luc/ui/charts";<BumpChart
periods={["Q1", "Q2", "Q3", "Q4"]}
series={[
{ label: "Momentum", tone: "warning", ranks: [1, 1, 2, 3] },
{ label: "Value", tone: "positive", ranks: [3, 2, 1, 1] },
{ label: "Carry", tone: "accent", ranks: [2, 3, 3, 2] },
{ label: "Quality", tone: "neutral", ranks: [4, 4, null, 4] },
]}
rankLabel="Rank"
height={320}
ariaLabel="Rank by quarter"
/>Data contract
`periods` is the ordered x axis; each `series` supplies one rank per period, with `null` for an unranked period. Ranks are supplied and are not derived from values.
Important configuration
Keep `rankLabel` visible, preserve period order, and use a distinct tone for the series in focus.
Guidelines
When not to use
Do not use a bump chart for raw values or encode an unranked period as rank zero; it would invent a position.
Configuration
| Export | Kind | Signature |
|---|---|---|
BumpChart | 13 documented props | ({ periods, series, rankLabel, title, description, state, height, className, ariaLabel, ariaDescription, onReady, onEvent, eager, }: BumpChartProps) => import("@types/react").JSX.Element |
BumpChart props
Type: BumpChartProps
Values the compiler reads from the declaration.
| Prop | Type | Default | Notes |
|---|---|---|---|
ariaDescription? | string | undefined | — | |
ariaLabel? | string | undefined | — | |
className? | string | undefined | — | |
description? | string | undefined | — | |
eager? | boolean | undefined | — | Create the engine on mount rather than when the surface is approached. |
height? | string | number | undefined | — | |
onEvent? | ((event: EChartEvent) => void) | undefined | — | |
onReady? | ((chart: EChartsInstance) => void) | undefined | — | |
periods | readonly string[] | — | Period labels along the horizontal axis. |
rankLabel? | string | undefined | — | Label the vertical axis, e.g. "Rank". |
series | readonly { label: string; ranks: readonly (number | null)[]; tone?: SeriesTone; }[] | — | |
state? | ChartState | undefined | — | |
title? | string | undefined | — |
Accessibility
A chart is a picture of data, so it needs a name that states what it shows, and the numbers must exist as text somewhere on the page — in a table or a written summary — because a drawing is not readable by a screen reader and cannot be copied.
What happens on the server, and when hydration changes it.
Family
Workflow & operations
Sequence, schedule, comparison and attribution.
Related