[dependabot]

Bumps react-apexcharts from 1.4.1 to 2.2.0.

Release notes

Sourced from react-apexcharts's releases.

React ApexCharts v2.2.0

🐛 Bug fixes

Passing ref to a chart no longer breaks it on React 19 (#745)

React 19 passes ref to function components as an ordinary prop. The chart wrapper forwarded its remaining props to its container <div>, so a ref you passed replaced the one the chart uses internally. The chart lost its element and failed to render with Element not found.

ref is now ignored by the client, core and hydrate components, so the chart always keeps its own container. Thanks to @​dajiaohuang for tracking this down and fixing it (#753).

⚠️ TypeScript changes

The type definitions now match the implementation:

• react-apexcharts and react-apexcharts/core are declared as function components instead of classes.
• ref is typed as never on all client and hydrate components.

If your code passes ref to a chart, or uses ReactApexChart as a type (for example useRef<ReactApexChart>()), it will now fail to compile. That ref never pointed at anything useful: on React 18 it stayed null, and on React 19 it broke the chart. To reach the ApexCharts instance, use chartRef:

import ApexCharts from "apexcharts";
import Chart from "react-apexcharts";
const chartRef = useRef<ApexCharts | null>(null);
<Chart type="line" series={series} options={options} chartRef={chartRef} />;
chartRef.current?.updateSeries(newSeries);

🧪 Testing

The test suite now runs on GitHub Actions against both React 18 and React 19.

npm i react-apexcharts@^2.2.0

React ApexCharts v2.1.1

🐛 Bug fixes

Fixed a crash on chart teardown — Cannot read properties of undefined (reading 'node') (#602)

When a chart was rendered or updated while its container was detached from the DOM - e.g. it's closed/hidden and reopened, a modal or tab unmounts it, or a queued window-resize redraw fired right after unmount - the underlying chart instance never finished setting up its SVG. The subsequent teardown then dereferenced an undefined element and threw. Because this happened inside React's useEffect cleanup, it could crash the entire component tree, not just the chart. The crash was commonly reported alongside chart.id and responsive options, which share the same teardown/resize path.

The unmount cleanup is now guarded across all client and hydrate entry points, so a teardown error can no longer crash your React tree — on any installed apexcharts version.

This pairs with the root-cause fix in apexcharts@5.15.1. For the complete fix, upgrade both:

npm i apexcharts@^5.15.1 react-apexcharts@^2.1.1
</tr></table> 

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for react-apexcharts since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)