npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@amcharts/amcharts5-react

v5.0.1

Published

React components for amCharts 5: a chart from a JSON config, and a hook for charts written in code

Readme

amCharts 5 for React

React components for amCharts 5: a chart from a JSON config, and a hook for charts written in code. They create and dispose the chart with the component, work in strict mode, and render on a server (Next.js and others) without loading the library there.

npm install @amcharts/amcharts5 @amcharts/amcharts5-react

It needs amCharts 5.21.4 or later and React 18 or later. With amCharts older than 5.21, the build fails with "Cannot resolve @amcharts/amcharts5/element".

A chart written in code

useAmChart gives setup a new root; build the chart in it as in any amCharts example. Put the returned ref on an element with a height.

import { useAmChart } from "@amcharts/amcharts5-react";
import * as am5xy from "@amcharts/amcharts5/xy";
import am5themes_Animated from "@amcharts/amcharts5/themes/Animated";

function VisitsChart({ data }) {
  const { ref } = useAmChart((root) => {
    root.setThemes([am5themes_Animated.new(root)]);

    const chart = root.container.children.push(am5xy.XYChart.new(root, {}));

    const xAxis = chart.xAxes.push(am5xy.CategoryAxis.new(root, {
      categoryField: "country",
      renderer: am5xy.AxisRendererX.new(root, {})
    }));

    const yAxis = chart.yAxes.push(am5xy.ValueAxis.new(root, {
      renderer: am5xy.AxisRendererY.new(root, {})
    }));

    const series = chart.series.push(am5xy.ColumnSeries.new(root, {
      xAxis: xAxis,
      yAxis: yAxis,
      categoryXField: "country",
      valueYField: "visits"
    }));

    xAxis.data.setAll(data);
    series.data.setAll(data);

    return series;
  }, [data]);

  return <div ref={ref} style={{ height: 400 }} />;
}
  • The chart is made again, with setup run again, when a value in the second argument ([data] here) changes. Leave it out to make the chart once.
  • useAmChart also returns root, and result: what setup returned. To change a chart without making it again, keep what you need from result, e.g. result.data.setAll(newData) for the series above.
  • useAmChart(setup, deps, { renderer: "svg" }) draws the chart as SVG.
  • The chart is made when the element with ref is there, also when it is rendered later, e.g. after a loading message, and disposed when it goes.
  • If setup throws, or the library cannot be loaded, the root is disposed and the error goes to the nearest error boundary, as an error in an effect does.

A chart from a JSON config

import { AmChart } from "@amcharts/amcharts5-react";
import am5themes_Animated from "@amcharts/amcharts5/themes/Animated";

<AmChart
  config={config}
  themes={[am5themes_Animated]}
  style={{ height: 400 }}
  onReady={({ root, chart }) => { /* the chart is built */ }}
/>

| Prop | What it is | |---|---| | config | The chart as a JSON config: an object or a JSON string. A config with different content makes the chart again; the same content written inline on every render does not. | | src | A URL to load the config from, used when there is no config. | | themes | Theme classes, e.g. [am5themes_Animated], or a class with its settings: [[am5themes_Adaptive, { baseColor: "#4150a0" }]]. Themes are not part of a config. In a variable of its own, type the list as Array<ChartElementTheme> (from @amcharts/amcharts5/element). | | resources | Geodata and locales the config names, e.g. { am5geodata_worldLow } for "geoJSON": "am5geodata_worldLow". See below. | | renderer | "svg" draws the chart as SVG; the default is canvas. | | onReady | Called with { root, chart } when the chart is built. | | onError | Called when it could not be built. | | id, className, style | For the chart's element. Give it a height; without one it is 400 pixels high. |

The chart types a config uses are loaded when it is built. <AmChart> is the library's <am5-chart> element: a ref on it gives that element, with root, chart and whenReady(), once the element's code has loaded (it is null until then). onReady is the simpler way to get the chart.

A map's config names its geodata ("geoJSON": "am5geodata_worldLow"), and a config may name a locale ("locale": "am5locales_de_DE"), instead of carrying them. With script tags they are globals; with npm imports, import the files the config names and give them in resources, under the same names:

import am5geodata_worldLow from "@amcharts/amcharts5-geodata/worldLow";

<AmChart config={mapConfig} resources={{ am5geodata_worldLow }} style={{ height: 400 }} />

Next.js and other server rendering

Both are client components: they work in a page that is rendered on a server, and the library is loaded only in the browser.

In the Next.js app router, a server component can render <AmChart> with a config, because a config is plain data. Theme classes and useAmChart need a client component (a file that starts with "use client"), because classes and functions cannot be passed from a server component.

Your own imports of @amcharts/amcharts5 in a component rendered on the server are fine in Next.js. React Router (and Remix 2) and Astro leave them to Node on the server, which cannot load the library: add it to the server bundle in the Vite config (vite in astro.config.mjs):

ssr: {
  noExternal: ["@amcharts/amcharts5"]
}

License

Without a commercial amCharts license, the charts show a small amCharts logo: that is the free license, in the LICENSE file. A commercial license removes the logo. Add its key once, when the app starts, before any chart is made:

import * as am5 from "@amcharts/amcharts5";

am5.addLicense("AM5C-...");

Put it in the file that starts your app, e.g. main.tsx. In Next.js, put it at the top of a client component's file. Not in the setup function: a chart decides on the logo when its root is made, before setup runs.

Unit tests

In jsdom (Jest, and Vitest by default) there is no canvas, so a chart cannot be drawn: an error boundary gets the error. In tests that render a component with a chart, mock the package.

With Vitest, e.g.:

vi.mock("@amcharts/amcharts5-react", () => ({
  useAmChart: () => ({ ref: () => {}, root: undefined, result: undefined }),
  AmChart: () => null,
}));

Examples

Each shows a chart in code whose data changes without making it again, and a chart from a JSON config:

  • Vite, with a map whose geodata is given in resources
  • Next.js, with the config chart in a server component
  • React Router, rendered on the server
  • Astro, in a React island

More