@rootnative/inertia 0.0.1 → 0.0.2

package/CHANGELOG.md

@@ -4,6 +4,18 @@ All notable changes to `@rootnative/inertia` are documented here. The format fol
 
 ## [Unreleased]
 
+## [0.0.2] - 2026-07-24
+
+### Added
+
+- **`useAnimator()` — imperative writes that resolve named transitions and respect reduced motion.** The imperative counterpart to `useAnimation`: returns an identity-stable `(value, to, transition?)` setter to call from event handlers (hover-in, focus, press) rather than from an effect. It closes the two footguns of the hand-written `value.value = resolveTransition(config, to)` escape hatch: a registered `TransitionName` now resolves through the nearest `<MotionConfig transitions>` (a bare `resolveTransition` can't reach the context registry, so imperative call sites otherwise rebuild configs the provider already owns — surfaced by the RootNative UI Slider rebuilding `state-hover` / `state-focus` by hand), and the write routes through the same `no-animation` reduced-motion downgrade `useAnimation` applies (raw `resolveTransition` writes silently bypass `<MotionConfig reducedMotion>` — a correctness fix). Not a new animation API — the hooks-layer equivalent of `useMotionValue` + `resolveTransition`, minus the footguns. New `Animator` type exported from the root barrel.
+- **`useColorCascade(rest, layers, options?)` — priority-ordered layered color crossfade.** Composites a stack of color layers over a base `rest` color; each layer carries its own `progress` shared value and blends toward its color as that progress rises, later layers winning over earlier ones (the values-layer form of the `gesture` prop's fixed-priority cascade, Decision 5). Exactly equivalent to the hand-chained nested-`interpolateColor` shape `focus(error(hover(rest)))`, collapsed into one hook and one worklet — the shape the RootNative UI TextField hand-writes three times (label color, filled indicator, outlined border). `options.key` reuses `ColorStyleKey` (default `backgroundColor`). Memoized on a colors+key signature so an equal-but-fresh `layers` literal produces no new UI-thread closure. Color-only by design; cascade a numeric key via `useInterpolatedStyle` + `useTransform` max. `useColorTransition` remains the single-layer fast path. New `ColorCascadeLayer` / `UseColorCascadeOptions` types exported from the root barrel.
+
+### Changed
+
+- **A prop-less `Motion.*` primitive is now a zero-cost plain host.** An instance carrying none of the animation-driving props (`initial` / `animate` / `exit` / `transition` / `variants` / `controller` / `gesture` / `layout` / `layoutId` / `onAnimationEnd`) previously still allocated the full animated body — ~25 per-key shared values, four gesture-progress shared values, gesture `useState`s, and a `useAnimatedStyle` worklet — every render. It now renders straight through `Animated.createAnimatedComponent(Component)` with `style` / `ref` / `onLayout` forwarded and no animation allocation, so a prop-less `Motion.View` is a genuine drop-in for `Animated.View` when hosting an animated-style fragment from `useColorTransition` / `useShadow` / `useInterpolatedStyle` / `useColorCascade` (no `/reanimated` import needed — closes proposal item 5). The plain host stays `<Presence>`-aware (it self-removes on exit via a context read + unmount effect, no worklet). Adding an animation prop opts the instance back into the full body; because the two paths are distinct component types, crossing that boundary remounts the element (give it a stable `key` if the remount matters). New guard test (`plain-host.test.tsx`) pins that a prop-less primitive calls neither `useSharedValue` nor `useAnimatedStyle`.
+- **Value hooks and the `Motion.*` factory now cancel in-flight animations on unmount.** `useMotionValue`, `useSpring`, `useBooleanSpring`, and `useAnimation` — and every per-key / gesture-layer shared value inside a `Motion.*` primitive — register an unmount cleanup that calls `cancelAnimation` on the shared value they own. Previously a mid-flight (or `repeat: 'infinite'`) `withSpring` / `withTiming` / `withDecay` kept ticking its worklet for frames after the owning component was gone; consumers who cared had to import `cancelAnimation` from the `/reanimated` interop subpath and hand-write the effect (surfaced by the RootNative UI Slider's 22-line 8-value teardown). The shared values are identity-stable and component-owned, so cancelling on unmount is always safe. `cancelAnimation` stays exported from the interop subpath for _mid-life_ cancellation — this change only covers the unmount case. Behavior change (no API change).
+
 ## [0.0.1] - 2026-07-23
 
 **First stable release.** Graduates the `0.0.0-alpha.x` line, absorbing Milestones 1–3 in a single tag: the declarative core (primitives, per-property transitions, sequences/keyframes, unified `repeat`, variants, `gesture` prop, `<Presence>`, `<MotionConfig>` with reduced-motion + named transitions), the value-layer hooks, the `layout` prop and rect-only `layoutId` shared-element transitions, and the `inertia-gestures` / `inertia-gradients` / `inertia-svg` adapter packages (released in lockstep). See the alpha entries below for the per-change history.

package/dist/{chunk-ALRHDFZE.mjs → chunk-2DHKV2XY.mjs}

@@ -1,4 +1,4 @@
-import { createMotionComponent } from './chunk-DWCLIBYO.mjs';
+import { createMotionComponent } from './chunk-LYMLQ6WQ.mjs';
 import { Image } from 'react-native';
 
 var MotionImage = createMotionComponent(Image);

package/dist/chunk-34Q4UM6V.js

@@ -0,0 +1,8 @@
+'use strict';
+
+var chunkIWLU3VDE_js = require('./chunk-IWLU3VDE.js');
+var reactNative = require('react-native');
+
+var MotionImage = chunkIWLU3VDE_js.createMotionComponent(reactNative.Image);
+
+exports.MotionImage = MotionImage;

package/dist/{chunk-CWLFUYIY.mjs → chunk-HFDZAHWP.mjs}

@@ -1,4 +1,4 @@
-import { createMotionComponent } from './chunk-DWCLIBYO.mjs';
+import { createMotionComponent } from './chunk-LYMLQ6WQ.mjs';
 import { ScrollView } from 'react-native';
 
 var MotionScrollView = createMotionComponent(ScrollView);