Custom Extensions

TanStack Charts exposes narrow inversion-of-control boundaries around its scene compiler. Prefer composition with built-in marks first. Add an extension when the chart requires geometry or behavior that cannot be expressed without distorting its data model.

Custom marks#

import { createMark } from '@tanstack/charts'

function createMark<
  TDatum,
  TXValue extends ChartValue = ChartValue,
  TYValue extends ChartValue = ChartValue,
>(
  initialize: (
    context: MarkInitializeContext,
  ) => InitializedMark<TDatum, TXValue, TYValue>,
): ChartMark<TDatum, TXValue, TYValue>

Initialization runs once per scene compilation and receives the mark's layer index:

interface MarkInitializeContext {
  markIndex: number
}

interface InitializedMark<
  TDatum = unknown,
  TXValue extends ChartValue = ChartValue,
  TYValue extends ChartValue = ChartValue,
> {
  id: string
  channels: Readonly<Record<string, MaterializedChannel>>
  render(context: MarkRenderContext): MarkScene<TDatum, TXValue, TYValue>
}

Materialized channels declare semantic values before scale resolution:

interface MaterializedChannel {
  scale?: string
  values: readonly unknown[]
  includeZero?: boolean
}

Use scale: 'x', scale: 'y', or scale: 'color' for shared chart scales. includeZero is a hint available to a custom scale resolver. Filter invalid values before materializing them.

The render context provides final geometry and shared presentation:

interface MarkRenderContext {
  markIndex: number
  chart: ChartBounds
  scales: Readonly<Record<string, ResolvedScale>>
  theme: ChartTheme
  color(value: ChartKey | null | undefined): string
  layout: ChartLayoutOptions
}

Return keyed scene nodes and, when the mark participates in native interaction, typed points:

interface MarkScene<
  TDatum = unknown,
  TXValue extends ChartValue = ChartValue,
  TYValue extends ChartValue = ChartValue,
> {
  nodes: readonly SceneNode[]
  points?: readonly ChartPoint<TDatum, TXValue, TYValue>[]
}

Mark requirements#

• Give the mark a stable ID. Derive a fallback from markIndex only when layer order is stable.
• Materialize every value needed to establish scale domains before rendering.
• Map through context.scales; do not recalculate responsive ranges.
• Give each scene node and point a deterministic key.
• Emit finite geometry only.
• Preserve the original datum and index in every interaction point.
• Use one honest focus coordinate and semantic x/y pair per point.
• Keep preprocessing outside render.

The scene node and point shapes are documented in Runtime and scene.

Distinct point and scale values#

Interval geometry may materialize endpoint value types that differ from its interaction anchor types. Use the exceptional subpath:

import { createMarkWithScaleValues } from '@tanstack/charts/mark/scale-values'

function createMarkWithScaleValues<
  TDatum,
  TXPointValue extends ChartValue,
  TYPointValue extends ChartValue,
  TXScaleValue extends ChartValue,
  TYScaleValue extends ChartValue,
>(
  initialize: (
    context: MarkInitializeContext,
  ) => InitializedMark<TDatum, TXPointValue, TYPointValue>,
): ChartMark<TDatum, TXPointValue, TYPointValue, TXScaleValue, TYScaleValue>

The subpath also exports ChartMarkPointX, ChartMarkPointY, ChartMarkScaleX, and ChartMarkScaleY. Use it only when the distinction is real; ordinary custom marks should use createMark.

Curves#

ChartCurve supplies precomputed path data for line and y-oriented area marks:

interface ChartCurve {
  line(points: readonly (readonly [number, number])[]): string
  area(
    top: readonly (readonly [number, number])[],
    bottom: readonly (readonly [number, number])[],
  ): string
}

AreaXCurve has the transposed contract:

interface AreaXCurve {
  areaX(
    right: readonly (readonly [number, number])[],
    left: readonly (readonly [number, number])[],
  ): string
}

The optional bridges d3Curve from @tanstack/charts/d3/shape and d3AreaXCurve from @tanstack/charts/d3/area-x adapt a supplied curve factory to these contracts. D3 module ownership and granular imports are documented in Scales and D3.

Custom positional scales#

A custom ChartScale resolves semantic values and the responsive range into a complete mapping and tick set. This is an unchecked math boundary; prefer a configured callable scale when possible.

See Advanced custom scales for the exact context and return type.

Custom color scales and legends#

ChartColorScale maps observed values, domain/range hints, and theme tokens to a ResolvedColorScale. ChartColorLegend independently reserves layout height and emits a scene node.

See Color and Custom legends.

Custom text measurement#

ChartTextMeasurer lets nonbrowser rendering, special fonts, or an application-owned typography engine provide painted glyph bounds. It affects guide geometry, not mark text rendering.

See Automatic guide layout for the contract.

Spatial indexes#

ChartSpatialIndexFactory replaces the default linear pointer lookup without changing scene compilation. Build the index from supplied points and return the nearest point within the requested distance. The host recreates it when the scene or factory changes.

See Spatial indexes. The appropriate granular spatial primitive can be brought through the boundary described in Scales and D3.

Custom focus and gestures#

ChartFocusStrategy owns pointer resolution, focus grouping, and keyboard task order. Rich gestures can instead disable chart-owned focus and maintain selection or viewport state in the application.

See Focus and interaction.

Custom renderers#

A ChartRenderer owns both deterministic server markup and one mounted ChartSurface. The surface renders scenes, converts browser coordinates to scene coordinates, paints focus, and releases renderer-owned resources. mountChartRenderer keeps responsive sizing, runtime updates, focus, keyboard, tooltip, and selection behavior shared across renderers.

Use @tanstack/charts/renderer directly or the framework /core entries. The optional built-in implementation at @tanstack/charts/canvas demonstrates the boundary without changing the default SVG imports.

For an SVG-only serialization change, pass a ChartSvgRenderer as renderSvg to the compatibility host or adapt it with createSvgChartRenderer from @tanstack/charts/svg/renderer. Preserve the SVG root, stable DOM keys, accessible name, coordinate system, and focus marker expected by that adapter.

Resource-aware SVG is already available through renderChartSvgWithResources; see Rendering and export.