Chart Definitions | TanStack Charts Español

A chart definition is the typed boundary between application state and the chart grammar. It owns marks, scales, guides, theme overrides, responsive choices, focus, tooltips, animation, keyboard policy, and spatial indexing.

Static definitions

Pass a complete spec when the chart does not need its resolved surface size:

import { barY, defineChart } from '@tanstack/charts'
import { scaleBand } from '@tanstack/charts/scales/band'
import { scaleLinear } from '@tanstack/charts/scales/linear'

interface AlphabetRow {
  letter: string
  frequency: number
}

const alphabet: readonly AlphabetRow[] = [
  { letter: 'E', frequency: 0.12702 },
  { letter: 'T', frequency: 0.09056 },
  { letter: 'A', frequency: 0.08167 },
  { letter: 'O', frequency: 0.07507 },
  { letter: 'I', frequency: 0.06966 },
]

const letterFrequencies = defineChart({
  marks: [barY(alphabet, { x: 'letter', y: 'frequency' })],
  scales: {
    x: {
      scale: () => scaleBand<string>().padding(0.12),
    },
    y: {
      scale: scaleLinear,
      nice: true,
      grid: true,
      axis: { label: 'Frequency' },
    },
  },
})

Responsive definitions

Pass a builder when tick density, annotations, or mark composition depends on the chart surface:

import { tooltip } from '@tanstack/charts/tooltip'

const productRanking = defineChart({
  tooltip,
  chart: ({ width }) => ({
    marks: [barX(ranked, { x: 'value', y: 'product' })],
    scales: {
      x: {
        scale: scaleLinear,
        nice: true,
        axis: { ticks: { count: width < 480 ? 4 : 7 } },
      },
      y: {
        scale: () => scaleBand<string>().padding(0.1),
      },
    },
  }),
})

The host controls width and height; the builder only reads their resolved values. It also receives the default build-time theme.

Transform beside the definition

Keep analytical work visible in ordinary functions:

function rankProducts(rows: readonly ProductRow[], metric: Metric) {
  return rows
    .map((source) => ({
      id: source.id,
      product: source.product,
      value: source[metric],
      source,
    }))
    .sort((left, right) => right.value - left.value)
}

Derived rows should retain source identity needed by tooltips and selection. Fetching, cancellation, permissions, and server aggregation remain application concerns.

Memoize the complete definition

Definitions capture the values they use. In React:

import { tooltip } from '@tanstack/charts/tooltip'

function ProductRanking({ rows, metric }: Props) {
  const definition = useMemo(() => {
    const ranked = rankProducts(rows, metric)

    return defineChart({
      tooltip,
      chart: ({ width }) => ({
        marks: [barX(ranked, { x: 'value', y: 'product' })],
        scales: {
          x: {
            scale: scaleLinear,
            nice: true,
            axis: { ticks: { count: width < 480 ? 4 : 7 } },
          },
          y: {
            scale: () => scaleBand<string>().padding(0.1),
          },
        },
      }),
    })
  }, [rows, metric])

  return <Chart definition={definition} ariaLabel="Product ranking" />
}

Use computed, createMemo, $derived, or the equivalent native primitive in other frameworks. Memoization is the update contract: preserve definition identity until a captured value changes.

Vanilla updates

Vanilla code makes that boundary explicit:

const createProductRanking = (rows: readonly ProductRow[], metric: Metric) => {
  const ranked = rankProducts(rows, metric)
  return defineChart({
    svgAnimation: true,
    chart: ({ width }) => buildRankingSpec(ranked, width),
  })
}

const options = {
  definition: createProductRanking(rows, 'revenue'),
  height: 360,
  ariaLabel: 'Products ranked by revenue',
}

const host = mountChart(container, options)

host.update({
  ...options,
  definition: createProductRanking(rows, 'orders'),
  ariaLabel: 'Products ranked by orders',
})

Charts owns surface measurement, scene construction, and keyed reconciliation. It does not own application equality or data reactivity.