Bump the node-dependencies group with 2 updates

[dependabot]

Bumps the node-dependencies group with 2 updates: alpinejs and apexcharts.

Updates alpinejs from 3.16.1 to 3.16.2

Release notes

Sourced from alpinejs's releases.

v3.16.2

What's Changed

• Fix fallback storage returning undefined for missing keys by @​hamdyelbatal122 in alpinejs/alpine#4867
• fix(persist): don't persist undefined values by @​Xuepoo in alpinejs/alpine#4876
• Run structural effects before dependent effects by @​calebporzio in alpinejs/alpine#4878
• Upgrade @vue/reactivity to Vue 3.5 by @​oddvalue in alpinejs/alpine#4861

New Contributors

• @​hamdyelbatal122 made their first contribution in alpinejs/alpine#4867
• @​Xuepoo made their first contribution in alpinejs/alpine#4876
• @​oddvalue made their first contribution in alpinejs/alpine#4861

Full Changelog: alpinejs/alpine@v3.16.1...v3.16.2

Commits

• 9ffa27d Bump version to 3.16.2
• 6c1eee8 Upgrade @vue/reactivity to Vue 3.5 (#4861)
• aa4c297 Run structural effects before dependent effects (#4878)
• See full diff in compare view

Updates apexcharts from 6.8.0 to 6.10.0

Release notes

Sourced from apexcharts's releases.

💎 Version 6.10.0

A feature release built around one question: what if the arrangement of a chart's marks were something you could hand it?

The unit chart already drew one dot per thing counted, and 6.9.0 opened a seam for supplying the positions yourself. This release ships the thing that seam was for. apexcharts/unit-shapes is a companion kit of 39 shapes a count can take: a heart, a house, a globe, a checkmark, a heartbeat trace, or the figure 1,024 drawn in 1,024 dots. Each one is a function of the marks and the plot rectangle rather than a picture, so the same shape serves 40 dots in a sparkline and 3,000 in a poster.

Alongside it: outer name labels for those shapes, so a crowd of dots reads without a legend, and a fix worth reading even if you never draw a heart, because it swallowed any update that changed only a callback.

✨ New

apexcharts/unit-shapes, 39 shapes a count can take

A new entry point, tree-shaken per shape. Importing one costs about 4 KB gzipped; importing the catalog is not something you need to do.

import ApexCharts from 'apexcharts'
import { heart } from 'apexcharts/unit-shapes'
new ApexCharts(el, {
chart: { type: 'unit' },
series: [57600, 16800, 4200, 3400],
labels: ['Repeat donors', 'First-time', 'Workplace drives', 'Emergency call-ups'],
plotOptions: {
unit: { layout: 'custom', positions: heart, unitValue: 100 },
},
}).render()

A shape is a plain callable, so positions: heart needs no registration step, and plotOptions.unit.positions already accepted a function: nothing in the chart had to learn about shapes.

The dots are packed, not stamped onto a template. Rows are cut across the outline, each row split into the spans that fall inside it, and the gap between dots is then bisected until the spans hold exactly the number of marks the data asks for. Density follows the shape's own area, which is why one outline covers three orders of magnitude of dot count. A thin limb, fin or tip keeps its single dot rather than dropping out, because that is what stops a shape dissolving as the count falls.

Three kinds, because things in the world are not all areas:

• Silhouettes (29) fill an outline: heart, house, tree, leaf, flame, droplet, fish, sun, human, group, star, crown, trophy, moneybag, funnel, shield, gear, robot, bulb, flask, car, plane, rocket, battery, pin, mountain, cross, bolt, arrow.
• Strokes (7) pack a thickened centreline, for a thing with no interior: check, wifi, pulse, xmark, percent, question, spiral. A dotted checkmark still reads as a checkmark, which is how a stroke degrades where a thin silhouette feature would simply vanish.
• Generated (3) compute their positions from maths and have no outline at all: globe (latitude rings with a tilt), target (concentric bands), pyramid (tiers).

Every shape carries its metadata: which category it belongs to, how it was made, and minUnits, the count below which it stops being recognisable. Ask for fewer and the chart says so in a console warning naming the shape, rather than rendering mush.

Composition, rather than a bigger catalog

outlined(heart)                  // trace the outline instead of filling it
heart.with({ order: 'cols' })    // where each series band lands inside the shape
glyphs('1,024')                  // the number, drawn in that many dots
preview(heart, { series })       // -> an SVG string, no chart and no DOM

outlined() gives all 29 silhouettes a hollow twin for no new artwork, since a stroked closed path is a ring. The fill order is what decides where each category sits: rows bands a shape top to bottom, cols left to right (which is why battery fills like a charge meter), centerOut puts the first series at its heart. preview() renders a shape to standalone SVG, so docs galleries, README images and launch graphics can be generated at build time or on a server from the catalog alone.

... (truncated)

Commits

• 177de62 release: 6.10.0
• 586919e chore: bump version to 6.10.0
• 92ac754 docs(readme): document the unit-shapes kit
• 446a0f5 fix(update): an update that changes only a function no longer vanishes
• 73d9faf fix(unit-shapes): preview() draws series bands, not one flat colour
• 82148a9 feat(unit-shapes): outline variants, digit composer, four more glyphs
• 9d1bfbf docs(samples): demos for the three stroke shapes
• c761847 feat(unit-shapes): stroke region, for shapes made of lines (P3)
• 3fa81d6 refactor(unit-shapes): drop mortarboard, hand and cloud
• 9905051 docs(samples): a demo per category for the new shapes, and a 35 shape gallery
• Additional commits viewable in compare view

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.