Bump apexcharts from 5.4.0 to 5.10.3 in /ui/changes

[dependabot]

Bumps apexcharts from 5.4.0 to 5.10.3.

Release notes

Sourced from apexcharts's releases.

💎 Version 5.10.3

Bug Fixes

• SSR: Bar/column charts rendered duplicate elements in renderToString() (1b4bcb1f)

  SSRElement.appendChild and insertBefore were unconditionally pushing the child onto the children array without checking whether the child already had a parent. Because Bar.js creates elDataLabelsWrap, elGoalsMarkers, and elBarShadows once per series but calls elSeries.add() on every data-point iteration, the SSR virtual DOM accumulated N×N bar paths and datalabel groups instead of N. The fix mirrors standard browser DOM move semantics: if a node already has a parent it is detached from that parent before being appended. This affects both appendChild and insertBefore.

💎 Version 5.10.2

Bug Fixes

• Tree-shaking: ESM entry points were incorrectly eliminated by bundlers

  dist/*.esm.js and dist/features/*.esm.js were missing from the sideEffects field in package.json. Bundlers such as Webpack and Rollup treat files not listed as having side effects as safe to drop when they are not explicitly imported, which caused chart type and feature registrations to be silently tree-shaken away in production builds. Adding both glob patterns ensures the self-registering ESM bundles are always retained.

💎 Version 5.10.1

Bug Fixes

Chart Registry Survives Duplicate Module Instances

Problem: When a bundler (Vite, webpack, etc.) accidentally creates two separate copies of the ApexCharts module - for example when mixing CJS and ESM imports, or when optimizeDeps is not configured - ApexCharts.use() would write to one module's registry while the chart renderer read from another. The chart type was effectively never registered, causing a runtime error.

Fix: The chart type registry is now stored on globalThis.__apexcharts_registry__ instead of a module-local variable. All module instances share a single registry on the global object, so registration is never silently lost regardless of how many module copies the bundler created.

This is a defense-in-depth fix. For best results, configure your bundler to deduplicate ApexCharts (Vite: add apexcharts to optimizeDeps.include). The globalThis registry ensures the library degrades gracefully even when deduplication is not configured.

💎 Version 5.10.0

New Features

Per-Type Modular Entry Points

Every public chart type now has its own dedicated entry point matching the chart.type string you already use in config. Previously, users needed to know the internal grouping (e.g. apexcharts/heatmap for treemap charts); now you import by the exact type name.

New entry points:

Import	Chart type(s) registered

... (truncated)

Commits

• dea8e7d fixes #5184; re-add paper() to typescript definitions
• 6c76437 build: 5.10.3
• 1b4bcb1 fix: SSRElement.appendChild now removes child from previous parent before re-...
• 7f97cb5 build: 5.10.2
• 08a42b8 release: 5.10.1
• 0ef2b48 fix: use globalThis for chart registry to survive duplicate module instances
• b225a37 release: 5.10.0
• b90a06d feat: add per-type modular entry points for all chart types
• b9ddfbb release: 5.9.0
• 996d7d7 release: 5.8.2-beta.1
• Additional commits viewable in compare view

Install script changes

This version adds prepare script that runs during installation. Review the package contents before updating.

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)