Bump apexcharts from 5.12.0 to 5.15.2

[dependabot]

Bumps apexcharts from 5.12.0 to 5.15.2.

Release notes

Sourced from apexcharts's releases.

💎 Version 5.15.2

Fixes

Draw-animation frame no longer touches a destroyed chart

An animated chart (e.g. an area chart) schedules a requestAnimationFrame during render() to run its mask-reveal / draw animation. If the chart was destroyed before that frame fired, the stale callback ran against already-cleared DOM and threw:

TypeError: Cannot read properties of null (reading 'node')   // in runMaskReveal

The classic trigger is React StrictMode, which mounts → unmounts → remounts a component in development: the first mount queues the animation frame, the unmount calls destroy() (which nulls w.dom.elDefs), and the queued frame then fires against the torn-down chart. Any sufficiently rapid unmount hit the same race.

The fix adds an internal isDestroyed flag, set by destroy() (but not by updates), that the deferred draw-animation callbacks - mask reveal, stroke draw, and bulk reveal - check and bail on before touching the DOM. The flag is cleared on the next render, so re-mounting re-arms animations normally.

This complements the detached-chart destroy() fix in 5.15.1; together they resolve the teardown crashes tracked in react-apexcharts#602.

💎 Version 5.15.1

A small patch release with a single stability fix: charts that are torn down before they ever mount no longer throw.

---

Fixes

destroy() no longer throws on an un-mounted / detached chart

Calling destroy() (or an internal clear()) on a chart that never finished rendering threw:

TypeError: Cannot read properties of undefined (reading 'node')

This happened when a chart was constructed against an element that wasn't connected to the DOM - so create() bailed out early before building the SVG, leaving w.dom.Paper undefined - and the chart was then destroyed. Common triggers:

• A React useEffect cleanup (or a Vue unmounted hook) tearing the chart down before the element was ever attached.
• A queued resize/update() firing after the host element had already been removed.

The teardown path now guards on the SVG actually having been created, cancels any pending resize redraw, and tolerates a missing Apex._chartInstances registry, so destroying a never-mounted chart is a safe no-op.

Fixes react-apexcharts#602 and vue-apexcharts#256.

💎 Version 5.15.0

New Features

Violin chart type

A new, tree-shakeable chart.type: 'violin' that renders a kernel-density curve for each category, with an optional overlay of the individual observations ("jitter") that produced it.

... (truncated)

Commits

• 66aeae5 release: 5.15.2
• 495aa30 fix: stop draw-animation rAF callbacks from touching a destroyed chart
• a9d3675 ci: move GitHub Actions off the deprecated Node 20 runtime
• 2aabd6c chore(deps): patch dev-dependency security advisories
• 8309269 release: 5.15.1
• 8f81f7a fix: don't throw on destroy() of an un-mounted/detached chart
• 0163fbf release: 5.15.0
• 212a4e2 fix: in Data.js - let open -> const open (only high/low/close are reassigned ...
• 09a0452 release: 5.15.0
• 01161a0 Merge branch 'main' of https://github.com/apexcharts/apexcharts.js
• Additional commits viewable in compare view

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dependabot]

Superseded by #8353.