Bump @preact/signals from 1.3.0 to 2.10.0 in /packages/design-system

[dependabot]

Bumps @preact/signals from 1.3.0 to 2.10.0.

Release notes

Sourced from @​preact/signals's releases.

@​preact/signals@​2.10.0

Minor Changes

• #954 6b051b5 Thanks @​marvinhagemeister! - Add support for passing functions as fallback to <Show> for lazy instantiation.

  <Show when={toggle} fallback={() => <p>I'm lazy</p>}>
  	<p>foo</p>
  </Show>

  This avoids eager evaluation of whatever is passed to fallback which matters when you're dealing with signals.

Patch Changes

• #959 b38cacf Thanks @​JoviDeCroock! - Name signals created internally by the Preact adapter and useLiveSignal so debugging tools can identify them.

@​preact/signals@​2.9.4

Patch Changes

• #952 89000a2 Thanks @​JoviDeCroock! - Stop treating useContext as hook state in the auto-memoization heuristic. Context updates force-update their subscribers in Preact, bypassing shouldComponentUpdate entirely, so context consumers can safely keep the props-based render skipping.

@​preact/signals@​2.9.3

Patch Changes

• #950 76f9155 Thanks @​joeyTedeschi! - Allow <For> to accept readonly arrays and signals containing readonly arrays.

• #948 6b0a76c Thanks @​JoviDeCroock! - Dispose signal prop updaters when an element re-renders without any signal props.

  The disposal pass only ran when the new render still carried at least one signal-bound prop. When every signal prop was replaced by plain values, the old updater effect stayed subscribed and kept writing the previous signal's values straight into the DOM, overriding whatever Preact rendered.

• Updated dependencies [2910fbf, d40746b]:

  • @​preact/signals-core@​1.14.4

@​preact/signals@​2.9.2

Patch Changes

• #942 e76780c Thanks @​JoviDeCroock! - Fix stale <For> render-prop indexes after removals/reorders by making each cached item's index reactive (a per-item signal) instead of a frozen prop. Cached children are reused and re-render with the new index rather than being recreated, so DOM/component identity is preserved.

• #938 e0ce9fd Thanks @​JoviDeCroock! - Fix Signal-bound DOM props getting stranded at a stale value when Preact reuses a DOM node. The prop-binding effect now writes the applied value back into the rendered props, keeping Preact's diff baseline in sync with the DOM instead of assuming Preact applied every update.

• Updated dependencies [beb84c1]:

  • @​preact/signals-core@​1.14.3

@​preact/signals@​2.9.0

Minor Changes

• #907 904a879 Thanks @​jbalsas! - Add optional getKey prop to <For> component for stable list reconciliation. When provided, getKey generates stable keys for the internal <Item> wrapper, fixing incorrect DOM reuse when items are removed or reordered.

@​preact/signals@​2.8.2

... (truncated)

Changelog

Sourced from @​preact/signals's changelog.

2.10.0

Minor Changes

• #954 6b051b5 Thanks @​marvinhagemeister! - Add support for passing functions as fallback to <Show> for lazy instantiation.

  <Show when={toggle} fallback={() => <p>I'm lazy</p>}>
  	<p>foo</p>
  </Show>

  This avoids eager evaluation of whatever is passed to fallback which matters when you're dealing with signals.

Patch Changes

• #959 b38cacf Thanks @​JoviDeCroock! - Name signals created internally by the Preact adapter and useLiveSignal so debugging tools can identify them.

2.9.4

Patch Changes

• #952 89000a2 Thanks @​JoviDeCroock! - Stop treating useContext as hook state in the auto-memoization heuristic. Context updates force-update their subscribers in Preact, bypassing shouldComponentUpdate entirely, so context consumers can safely keep the props-based render skipping.

2.9.3

Patch Changes

• #950 76f9155 Thanks @​joeyTedeschi! - Allow <For> to accept readonly arrays and signals containing readonly arrays.

• #948 6b0a76c Thanks @​JoviDeCroock! - Dispose signal prop updaters when an element re-renders without any signal props.

  The disposal pass only ran when the new render still carried at least one signal-bound prop. When every signal prop was replaced by plain values, the old updater effect stayed subscribed and kept writing the previous signal's values straight into the DOM, overriding whatever Preact rendered.

• Updated dependencies [2910fbf, d40746b]:

  • @​preact/signals-core@​1.14.4

2.9.2

Patch Changes

• #942 e76780c Thanks @​JoviDeCroock! - Fix stale <For> render-prop indexes after removals/reorders by making each cached item's index reactive (a per-item signal) instead of a frozen prop. Cached children are reused and re-render with the new index rather than being recreated, so DOM/component identity is preserved.

• #938 e0ce9fd Thanks @​JoviDeCroock! - Fix Signal-bound DOM props getting stranded at a stale value when Preact reuses a DOM node. The prop-binding effect now writes the applied value back into the rendered props, keeping Preact's diff baseline in sync with the DOM instead of assuming Preact applied every update.

• Updated dependencies [beb84c1]:

  • @​preact/signals-core@​1.14.3

2.9.1

... (truncated)

Commits

• 3c55a9b Version Packages (#955)
• b38cacf Name internal Preact signals (#959)
• 6b051b5 Support lazy fallback in \<Show>
• 5a85452 Version Packages (#953)
• 89000a2 Remove seeing useContext as HOOKS_STATE (#952)
• f6437f7 Version Packages (#946)
• 76f9155 Allow For to accept readonly arrays (#950)
• 6b0a76c fix(preact): dispose prop updaters when an element loses all signal props (#948)
• 913110a Version Packages (#939)
• e76780c fix(utils): keep For render-prop indexes reactive for cached items (#942)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​preact/signals 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)