Angular

@mochart/angular wraps @mochart/core in Angular components. Config and data changes get mochart's staged animations for free — axis expansion, value change, axis contraction, and gapless stacked transitions — no extra wiring needed.

Install

npm install @mochart/angular @mochart/core @angular/core

The optional stylesheet

If your app uses a global CSS reset (Tailwind's preflight, a normalize.css-style reset), also import the core package's optional stylesheet — it re-asserts the browser defaults the chart's tooltip and message overlays rely on, and never overrides the chart's own styling:

import '@mochart/core/mochart.css';

Quick start

DefaultChart is the simplest entry point — give it a raw config and a plain array-of-objects dataset:

import { Component } from '@angular/core';
import { DefaultChart } from '@mochart/angular';

@Component({
  selector: 'app-revenue',
  imports: [DefaultChart],
  template: '<mochart-default-chart [config]="config" [data]="data" [width]="640" [height]="400" />'
})
export class Revenue {
  config = {
    title: { text: 'Revenue' },
    categoryAxis: { property: 'month', type: 'string', scale: 'ordinal' },
    seriesDefaults: { renderer: 'bar' },
    series: [{ property: 'revenue', title: 'Revenue' }]
  };

  data = [
    { month: 'Jan', revenue: 10 },
    { month: 'Feb', revenue: 20 }
  ];
}

Chart is the lower-level component for hosts that manage config enhancement and data providers themselves:

import { Component } from '@angular/core';
import { enhanceConfig, ArrayOfObjectsDataProvider } from '@mochart/core';
import { Chart } from '@mochart/angular';

@Component({
  selector: 'app-revenue',
  imports: [Chart],
  template: '<mochart-chart [mochartConfig]="mochartConfig" [dataProvider]="dataProvider" [width]="640" [height]="400" />'
})
export class Revenue {
  mochartConfig = enhanceConfig(config);
  dataProvider = new ArrayOfObjectsDataProvider(data, 'month');
}

Sizing

width and height are optional. The component's own host element (<mochart-chart> / <mochart-default-chart>) is the container the chart mounts into; whichever dimension you omit tracks that element's size via ResizeObserver. class and style set on the element style that same container, so size it however you like and the chart follows it:

<mochart-chart [mochartConfig]="mochartConfig" [dataProvider]="dataProvider" style="width: 100%; height: 400px" />

Explicit width/height inputs win over conflicting style values.

Any other attribute written on the element (id, data-testid, aria-…) naturally lands on that same container. The optional dataTestId input is the same surface the other bindings offer — it sets and removes data-testid dynamically, and a static data-testid attribute is left untouched when the input is never used.

When the data changes

Config and data changes are detected by reference identity: the chart compares the inputs it receives, not their contents. An in-place push leaves the input reference unchanged, so change detection has nothing new to pass on — reassign instead of mutate:

// ✓ a new array — the chart animates to it
this.data = [...this.data, { month: 'Mar', revenue: 30 }];

// ✗ invisible — same reference, the input never changes
this.data.push({ month: 'Mar', revenue: 30 });

The same rule applies to config on mochart-default-chart and to mochartConfig/dataProvider on mochart-chart — pass a new object (or provider) to change them.

For hosts that do mutate data in place, the components expose the core refresh() escape hatch as a public method — it re-reads the current config/data, re-indexing the built-in providers. Reach it through a template reference variable or @ViewChild:

@ViewChild('chart') chart!: DefaultChart;

addRow(row: DataRow) {
  this.data.push(row);
  this.chart.refresh();
}

<mochart-default-chart #chart [config]="config" [data]="data" />

Both components extend the exported abstract BaseChart, which carries everything except the config/data inputs — sizing, the state and placeholder inputs, the controlled focus/filter inputs, every output, and refresh(). Type a @ViewChild (or a helper accepting either component) as BaseChart when it shouldn't care which chart it gets.

Inputs, outputs, and states

Both components emit the chart callbacks as outputs, dropping the core on prefix — onChartClick becomes chartClick, onSliceClick becomes sliceClick — usable as (chartClick)="..." in templates; only subscribed outputs are wired into the chart. The one exception is onFocus, exposed as focusChange — a bare (focus) would collide with the native focus event. They also accept a placeholder input per state. Each placeholder input takes an Angular component class whose declared inputs among the chart state context names (width, height, error, …) are kept up to date while the chart is in that state. Both components also accept loading and error to force the loading or error state.

Every input and output, with its type and its core counterpart, is listed in Framework props.

Controlled state

Focus and legend filtering are chart-managed by default, but each piece of that state has a matching input that takes over while it is set (not undefined): focusedCategoryIndex (-1 = none), focusedSeriesId and focusedValueAxisId (null = none), and filteredSeriesIds (a map of series id → true = filtered out). Pass back what the focusChange and seriesFilter outputs emit to keep focus and filtering in sync across several charts (the round-trip is shown in Controlled focus and filtering); leave an input undefined to let the chart keep managing that piece itself.

See it in action

The Angular demo gallery is a full application built on @mochart/angular (Angular router, zoneless); its source lives in packages/mochart-demo-angular.