humanspeak / svelte-motion

66%

main: 3%

push

github

feat: useAnimate hook (#339)

* feat: useAnimate hook

Imperative animation API mirroring framer-motion's useAnimate. Returns
[scope, animate] where scope is a Svelte 5 attachment and animate is a
scoped animate() that resolves CSS selectors against scope.current.

Closes #301

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* fix: scope must contain every selector target in useAnimate demo

The demo and docs example attached `{@attach scope}` to the <ul>, but the
sequence's second segment targeted `button.target` — a sibling of the
list, not a descendant. `scope.current.querySelectorAll('button.target')`
matched nothing, so the target button never animated.

Move the scope onto a wrapper `<div>` that contains both the list and
the target, and update the docs snippet to make the requirement
explicit.

Add an e2e test that exercises the second segment by asserting the
target button's computed transform reflects the grow animation —
this would fail if the scope were attached to the <ul> alone.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* fix: address CodeRabbit review on useAnimate

- Widen useAnimate<T> generic bound from HTMLElement to Element so SVG
  roots are valid scope targets, matching motion's AnimationScope<T>.
- Demo and docs example: stop scope.animations and bump a runToken in
  reset() so a Reset click during a running sequence cancels in-flight
  animations and prevents the awaited run() from setting a stale
  status='done'.
- Sitemap generator: preserve identifier-style titles (no whitespace) in
  example descriptions instead of lowercasing unconditionally. Phrase
  titles ("Animated Button" → "animated button") still flow naturally;
  API names ("useAnimate", "AnimatePresence") keep their casing. Regen
  applied to every entry in examples/+page.ts.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

406 of 551 branches covered (73.68%)

Branch coverage included in aggregate %.

12 of 12 new or added lines in 1 file covered. (100.0%)

1559 of 2408 relevant lines covered (64.74%)

8.09 hits per line