# MiniBar (/docs/charts/mini-bar)

MiniBar draws one zero-anchored bar per category, in the order the data arrives, so a row of categories reads at a
glance: which is biggest, and by roughly how much. That order is often information itself: weekday order and funnel
order carry meaning that ranking would destroy, so sorting is an explicit `order` prop and never silent. An explicit
`domain` is widened to include zero, because a bar whose length doesn't start at zero misstates its own magnitude, and
the component refuses to draw one.

```tsx
<MiniBar
  data={[
    { label: "East", value: 940 },
    { label: "West", value: 410 },
    { label: "South", value: 620 },
    { label: "North", value: 120 },
  ]}
  title="Sales by region"
  width={150}
  height={48}
/>
```

## Install

```tsx
import { MiniBar } from "@microcharts/react/mini-bar";

<MiniBar data={regions} title="Sales by region" />
```

Setup (package + stylesheet): [Quickstart](/docs/quickstart#set-up-with-an-ai-agent) or paste [`/agent-setup.md`](/agent-setup.md) into your agent.

## Try it

```tsx
import { MiniBar } from "@microcharts/react/mini-bar/interactive";

<MiniBar
  data={regions}
/>
```

## When to use it

Use it for per-row category mix in tables and small comparisons in KPI cards. Past 8 categories reach for a full bar
chart; for time series use SparkBar.

## Sizing

**table cell**

```tsx
<MiniBar data={row.mix} width={50} height={16} />
```

**signed with polarity**

```tsx
<MiniBar data={signed} positive="up" />
```

## Variants

```tsx
// reordering changes what the chart SAYS, so it's a data prop
<MiniBar data={regions} order="desc" />
<MiniBar data={regions} highlight="South" />
```

```tsx
// bars extend below zero; positive engages the valence tokens
<MiniBar
  data={[
    { label: "Mon", value: 4 },
    { label: "Tue", value: -2 },
    { label: "Wed", value: 6 },
    { label: "Thu", value: -1 },
    { label: "Fri", value: 3 },
  ]}
  positive="up"
/>
```

```tsx
<MiniBar
  data={[
    { label: "East", value: 12400 },
    { label: "West", value: 8600 },
  ]}
  locale="de-DE"
/>
```

The extremes named in the summary follow `format`/`locale`: 12400 reads "12.400" under `de-DE` rather than the English
"12,400".

## Edge cases

```tsx
// a missing category leaves a gap instead of shifting its neighbors
<MiniBar data={[
  { label: "a", value: 5 },
  { label: "b", value: null },
  { label: "c", value: 7 },
]} />
```

```tsx
<MiniBar data={[{ label: "Only", value: 4 }]} />
```

A `null` value draws no bar but keeps its band, so the two real bars around it stay exactly as far apart as in a fully
populated row, and a column of MiniBars stays aligned through missing data. A single category still renders, and its
summary says so plainly ("1 category…") rather than degenerating into a bare-bar special case. Past 8 categories every
bar still renders, with nothing dropped or truncated, but the component logs a dev warning: MiniBar is a cell chart, and
a wider comparison belongs in a full bar chart.

## Four homes

**In a sentence**

```tsx
<p>
  Q3 revenue splits four ways{" "}
  <span className="mc-inline">
    <MiniBar data={regions} width={70} height={16} summary={false} />
  </span>{" "}
  — East alone outsells North more than seven to one.
</p>
```

**In a table cell**

```tsx
<td>
  <MiniBar data={rep.mix} width={70} height={18} />
</td>
```

**In a KPI card**

```tsx
<div className="kpi">
  <span className="figure">East</span>
  <span className="unit">45% of Q3 revenue</span>
  <MiniBar data={regions} highlight="East" width={140} height={40} />
</div>
```

**In a tab header**

```tsx
<button className="tab">
  Region <MiniBar data={regions} width={50} height={14} />
</button>
```

## Accessibility

The accessible name gives the count and the extremes: **"4 categories. Highest East 940, lowest North 120."** The
interactive entry announces each bar with its rank: **"East: 940 — 1st of 4."**

The interactive entry follows the shared [interaction contract](/docs/accessibility#one-interaction-contract):
arrow keys rove between units on both axes, `Home` and `End` jump to the ends, and a click, tap, `Enter` or
`Space` selects a unit — pinning its readout so it survives blur, until you select it again, press `Escape`, or
press outside the chart. On touch, a tap pins and a drag scrubs.

## Props

| Prop | Type | Description |
| --- | --- | --- |
| `data` (required) | `{ label; value }[]` | Categories in meaningful order. |
| `order` | `"data" \| "desc" \| "asc"` | Ranking read vs positional read — data-facing, not styling. |
| `highlight` | `number \| string` | Index or label to emphasize. |
| `orientation` | `"horizontal" \| "vertical"` | Rows for wider, shorter cells. |
| `positive` | `"up" \| "down"` | Engages pos/neg tokens on signed data. |
| `label` | `"none" \| "max"` | Peak-value readout (vertical only; default "none"). |
| `animate` | `boolean` | (interactive) Opt-in entrance motion when the chart mounts client-side — add `import "@microcharts/react/motion"` once. Inert on the server, on hydrated server HTML, and under `prefers-reduced-motion`. |

Plus the shared grammar — `data`, `domain`, `color`, `title`, `summary`, `format` — and the layout props (`width`, `height`, `className`, `style`) that every chart accepts. Interactive entries also share `animate` and `live`, and — wherever a chart has more than one navigable unit — `onActive`, `onSelect`, `selectedIndex` and `defaultSelectedIndex`; and — wherever the chart shows a hover value — `readout`. See [the shared grammar](/docs/quickstart#the-shared-grammar).