Documentation

Components

Use the tested mw.* React Native component proxy.

Components

mw.* parses animate-* tokens at runtime, passes ordinary classes to NativeWind, combines existing style with a Reanimated style, and forwards refs and native props.

The explicitly mapped components are:

API	Native base	Animated base
`mw.View`	`View`	`Animated.View`
`mw.Text`	`Text`	`Animated.Text`
`mw.Image`	`Image`	`Animated.Image`
`mw.ScrollView`	`ScrollView`	`Animated.ScrollView` plus scroll context
`mw.FlatList`	`FlatList`	`Animated.FlatList`
`mw.Pressable`	`Pressable`	Animated `Pressable`
`mw.TextInput`	`TextInput`	Animated `TextInput`

mw.SectionList can pass through without animation classes, but is not an animated mapping in v2. Unknown proxy names fall back to a View and must not be used as an implicit custom-component factory.

<mw.Pressable
  accessibilityRole="button"
  className="bg-blue-500 p-4 animate-tap:scale-95 animate-spring"
  style={{ minHeight: 48 }}
>
  <mw.Text className="text-white">Save</mw.Text>
</mw.Pressable>

Use a press-capable component for animate-tap:*. A plain View does not promise the same responder behavior on every platform.

Unconfigured parsed class strings use a bounded cache; provider-configured strings are evaluated against that configuration. Components without recognized motion data render their plain mapped component; with motion data, they render the animated mapping and subscribe only to the properties in that parsed result.