BulletChart
Show sequence, schedule or attribution over rows you prepared.
@luc/ui/chartsWhat it shows
Compare an actual value with a target and qualitative ranges in a compact row.
Live preview
A measured value, a target and qualitative bands — the ranges are context, not thresholds the chart enforces.
<BulletChart
rows={[
{ label: "Coverage", value: 84, target: 90, ranges: [60, 80, 100] },
{ label: "Latency", value: 72, target: 70, ranges: [50, 75, 100] },
{ label: "Uptime", value: 98, target: 99, ranges: [95, 98, 100] },
]}
valueLabel="Actual"
targetLabel="Target"
format={{ kind: "integer", suffix: "%" }}
height={280}
ariaLabel="Actual against target"
/>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 { BulletChart } from "@luc/ui/charts";
<BulletChart
rows={[
{ label: "Coverage", value: 84, target: 90, ranges: [60, 80, 100] },
{ label: "Latency", value: 72, target: 70, ranges: [50, 75, 100] },
{ label: "Uptime", value: 98, target: 99, ranges: [95, 98, 100] },
]}
valueLabel="Actual"
targetLabel="Target"
format={{ kind: "integer", suffix: "%" }}
height={280}
ariaLabel="Actual against target"
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 `BulletChart` from Luc UI. It is: Show sequence, schedule or attribution over rows you prepared.
Import it with: import { BulletChart } 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={280}`, `state="ready"`, `ariaLabel="Actual against target"`.
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
<BulletChart
rows={[
{ label: "Coverage", value: 84, target: 90, ranges: [60, 80, 100] },
{ label: "Latency", value: 72, target: 70, ranges: [50, 75, 100] },
{ label: "Uptime", value: 98, target: 99, ranges: [95, 98, 100] },
]}
valueLabel="Actual"
targetLabel="Target"
format={{ kind: "integer", suffix: "%" }}
height={280}
ariaLabel="Actual against target"
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 { BulletChart } from "@luc/ui/charts";<BulletChart
rows={[
{ label: "Coverage", value: 84, target: 90, ranges: [60, 80, 100] },
{ label: "Latency", value: 72, target: 70, ranges: [50, 75, 100] },
{ label: "Uptime", value: 98, target: 99, ranges: [95, 98, 100] },
]}
valueLabel="Actual"
targetLabel="Target"
format={{ kind: "integer", suffix: "%" }}
height={280}
ariaLabel="Actual against target"
/>Data contract
`rows` contain `label`, `value`, `target` and ordered `ranges`; `valueLabel` and `targetLabel` name the marks; `format` describes the unit. Ranges are context, not automatic thresholds.
Important configuration
Keep range order ascending, name the target, and format the actual and target with one unit.
Guidelines
When not to use
Do not use qualitative ranges as if they were statistically derived thresholds; their meaning must be defined by the caller.
Configuration
| Export | Kind | Signature |
|---|---|---|
BulletChart | 14 documented props | ({ rows, format, valueLabel, targetLabel, title, description, state, height, className, ariaLabel, ariaDescription, onReady, onEvent, eager, }: BulletChartProps) => import("@types/react").JSX.Element |
BulletChart props
Type: BulletChartProps
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. |
format? | ChartFormat | undefined | — | |
height? | string | number | undefined | — | |
onEvent? | ((event: EChartEvent) => void) | undefined | — | |
onReady? | ((chart: EChartsInstance) => void) | undefined | — | |
rows | readonly BulletRow[] | — | |
state? | ChartState | undefined | — | |
targetLabel? | string | undefined | — | |
title? | string | undefined | — | |
valueLabel? | 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