Bump @lisse/react from 0.3.2 to 0.6.2

[dependabot]

Bumps @lisse/react from 0.3.2 to 0.6.2.

Release notes

Sourced from @​lisse/react's releases.

@​lisse/react@​0.6.2

Patch Changes

• 7a5d7bd: Outer effects now work on an element that is itself the layout target, with no wrapper div.

  The SVG effects overlay was stretched over its anchor with position: absolute; inset: 0, which assumed the anchor's padding box was the clipped element's border box. It rarely was. Anchoring to the element itself nested the overlay inside its own clip-path, which clips the whole subtree, so an outerBorder was cut away entirely; anchoring to a shared parent put every overlay at the parent's origin, so a grid of buttons drew all its rings stacked on the first cell. Between them there was no way to get an outer border, focus ring included, without wrapping the element and giving up its place in the layout.

  The overlay is now sized and positioned over its own target inside the anchor, so the element keeps its position as a direct grid/flex item and its role as the keyboard-focus target. Placement stays exact through anchor borders and padding, scrolled anchors, ancestor transform: scale(), and fractional offsets, and it follows the element when a container reflows it without resizing it. An anchor ref pointing at the clipped element itself is now ignored in favour of its parent, since a nested overlay could never paint an outer border.

  Positioning the overlay needs the element's offset, and reading that inside the resize flush's write pass would force a synchronous relayout per element — 119 layouts became 36,000 across 300 elements in an early cut of this. The offset now rides along with the size the shared ResizeObserver already measures in its batched read pass, so layout work stays flat in the number of elements. resize-storm gained a case that renders actual effects (the existing one renders none, so it never ran this code) and asserts on the layout counter rather than frame timing, which is too hardware-dependent to catch it.

  Sharing one anchor between many elements also exposed an unref-counted isolation: isolate: the drop shadow saved and restored that style per handle, so the second handle on a container captured the first's isolate and wrote it back on teardown, stranding a stacking context. It is now ref-counted like position.

  <SmoothCorners> renders pixel-for-pixel as before whenever its wrapper starts where the element starts, which is the usual case. It is not purely additive there, though: the wrapper is a block <div> and as="button" renders an inline-block child, so under text-align: center — or anything else that offsets the element inside its wrapper — the effects overlay used to sit at the wrapper's corner while the element sat elsewhere. It now follows the element.

• Updated dependencies [7a5d7bd]

  • @​lisse/core@​0.6.2

@​lisse/react@​0.6.1

Patch Changes

• Updated dependencies [cf56f97]
  • @​lisse/core@​0.6.1

@​lisse/react@​0.6.0

Minor Changes

• e4820bb: Default corner smoothing is now 0.65 (APPLE_SMOOTHING) — the closest Figma-curve match to Apple's continuous corners. Figma's labeled "iOS" preset remains available as FIGMA_SMOOTHING (0.6).

  Migration

  • If you omitted smoothing and want the old look: set smoothing: FIGMA_SMOOTHING (or 0.6).
  • If you already pass smoothing: 0.6 explicitly, nothing changes.
  • Prefer the named constants over magic numbers going forward.

• b229eb0: Library-wide performance pass and audit fixes.

  • Core: allocation-free corner distribution with a uniform fast path, superellipse fit hoisted out of the per-orient loop, persistent LRU path cache that re-serializes on in-place options mutation, ResizeObserver border-box sizes threaded to callbacks (no more per-tick getComputedStyle), read/write-split rAF flush, single batched style read at mount.
  • React/Vue: server-rendered markup now carries an inline border-radius fallback so corners are rounded before hydration; it's cleared once the clip-path lands and never fights the squircle. New core export cornerOptionsToBorderRadius backs it.
  • React: shadows no longer vanish when shadowStrategy flips back to "svg"; non-hex shadow colors (oklch/lab) emit valid box-shadow chains with opacity composed via color-mix; Slot composes refs via memo so child refs aren't re-attached every render.
  • Vue/Svelte: change guards skip path regeneration and effect writes when size and options are unchanged; Vue drops deep watchers for keyed ones.
  • Published dist is now minified and tarballs no longer ship CJS sourcemaps (core unpacked size 140 kB → 86 kB).

Patch Changes

• f9aabec: composeRefs preserves React 19 callback-ref cleanup return values so teardown from composed refs actually runs.
• Updated dependencies [e4820bb]
• Updated dependencies [b229eb0]
  • @​lisse/core@​0.6.0

... (truncated)

Changelog

Sourced from @​lisse/react's changelog.

0.6.2

Patch Changes

• 7a5d7bd: Outer effects now work on an element that is itself the layout target, with no wrapper div.

  The SVG effects overlay was stretched over its anchor with position: absolute; inset: 0, which assumed the anchor's padding box was the clipped element's border box. It rarely was. Anchoring to the element itself nested the overlay inside its own clip-path, which clips the whole subtree, so an outerBorder was cut away entirely; anchoring to a shared parent put every overlay at the parent's origin, so a grid of buttons drew all its rings stacked on the first cell. Between them there was no way to get an outer border, focus ring included, without wrapping the element and giving up its place in the layout.

  The overlay is now sized and positioned over its own target inside the anchor, so the element keeps its position as a direct grid/flex item and its role as the keyboard-focus target. Placement stays exact through anchor borders and padding, scrolled anchors, ancestor transform: scale(), and fractional offsets, and it follows the element when a container reflows it without resizing it. An anchor ref pointing at the clipped element itself is now ignored in favour of its parent, since a nested overlay could never paint an outer border.

  Positioning the overlay needs the element's offset, and reading that inside the resize flush's write pass would force a synchronous relayout per element — 119 layouts became 36,000 across 300 elements in an early cut of this. The offset now rides along with the size the shared ResizeObserver already measures in its batched read pass, so layout work stays flat in the number of elements. resize-storm gained a case that renders actual effects (the existing one renders none, so it never ran this code) and asserts on the layout counter rather than frame timing, which is too hardware-dependent to catch it.

  Sharing one anchor between many elements also exposed an unref-counted isolation: isolate: the drop shadow saved and restored that style per handle, so the second handle on a container captured the first's isolate and wrote it back on teardown, stranding a stacking context. It is now ref-counted like position.

  <SmoothCorners> renders pixel-for-pixel as before whenever its wrapper starts where the element starts, which is the usual case. It is not purely additive there, though: the wrapper is a block <div> and as="button" renders an inline-block child, so under text-align: center — or anything else that offsets the element inside its wrapper — the effects overlay used to sit at the wrapper's corner while the element sat elsewhere. It now follows the element.

• Updated dependencies [7a5d7bd]

  • @​lisse/core@​0.6.2

0.6.1

Patch Changes

• Updated dependencies [cf56f97]
  • @​lisse/core@​0.6.1

0.6.0

Minor Changes

• e4820bb: Default corner smoothing is now 0.65 (APPLE_SMOOTHING) — the closest Figma-curve match to Apple's continuous corners. Figma's labeled "iOS" preset remains available as FIGMA_SMOOTHING (0.6).

  Migration

  • If you omitted smoothing and want the old look: set smoothing: FIGMA_SMOOTHING (or 0.6).
  • If you already pass smoothing: 0.6 explicitly, nothing changes.
  • Prefer the named constants over magic numbers going forward.

• b229eb0: Library-wide performance pass and audit fixes.

  • Core: allocation-free corner distribution with a uniform fast path, superellipse fit hoisted out of the per-orient loop, persistent LRU path cache that re-serializes on in-place options mutation, ResizeObserver border-box sizes threaded to callbacks (no more per-tick getComputedStyle), read/write-split rAF flush, single batched style read at mount.
  • React/Vue: server-rendered markup now carries an inline border-radius fallback so corners are rounded before hydration; it's cleared once the clip-path lands and never fights the squircle. New core export cornerOptionsToBorderRadius backs it.
  • React: shadows no longer vanish when shadowStrategy flips back to "svg"; non-hex shadow colors (oklch/lab) emit valid box-shadow chains with opacity composed via color-mix; Slot composes refs via memo so child refs aren't re-attached every render.
  • Vue/Svelte: change guards skip path regeneration and effect writes when size and options are unchanged; Vue drops deep watchers for keyed ones.
  • Published dist is now minified and tarballs no longer ship CJS sourcemaps (core unpacked size 140 kB → 86 kB).

Patch Changes

• f9aabec: composeRefs preserves React 19 callback-ref cleanup return values so teardown from composed refs actually runs.
• Updated dependencies [e4820bb]

... (truncated)

Commits

• 87fed15 chore: version packages
• 7a5d7bd fix: outer effects on direct clipped elements (no wrapper div) (#119)
• 73596c5 chore: version packages (#112)
• cf56f97 fix: stale clip-paths mid-resize, and extension clipping on Lisse-owned pages...
• 114b5c6 chore: version packages (#107)
• b229eb0 perf: library-wide optimization pass, audit fixes, and distilled internals (#...
• f9aabec chore(audit): fix ref cleanups and ResizeObserver crashes (#105)
• fd248bd chore: version packages (#98)
• b55a572 chore: version packages (#96)
• 594f418 fix(react): re-clip at commit time so animated sizes never paint a stale clip...
• 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 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)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
crib-shortlist	Ready	Preview	Jul 31, 2026 7:55pm