Documentation
Frameworks
Choose the tested Motionwind v2 adapter for React, Vue, JavaScript, or React Native.
Frameworks
Motionwind v2 keeps one class grammar and one parser while allowing each runtime to expose an honest capability set.
Vite & Next.js — compile static tokens with no runtime parser.
npm i motionwind-react@2 motion motionwind-core@2Expo beta — runtime mw.* components powered by Reanimated.
npm i motionwind-react-native@2 motionwind-core@2A build-time template transform → Motion for Vue.
npm i motionwind-vue@2 motion-v motionwind-core@2A runtime DOM scan → Motion. No build step, drop in a script.
npm i motionwind-vanilla@2 motion motionwind-core@2| Target | Package | Tier | Default path |
|---|---|---|---|
| Next.js and React/Vite | motionwind-react | Stable | Build-time JSX transform |
| Vue/Vite and Nuxt | motionwind-vue | Stable | Template transform or runtime component |
| Browser JavaScript | motionwind-vanilla | Stable | Runtime DOM scan |
| React Native and Expo | motionwind-react-native | Beta | Runtime mw.* components |
The same syntax does not mean every platform has the same primitives. Web hover, SVG paths, layout projection, native scroll views, and drag recognizers have different runtime requirements. Motionwind checks the adapter's declared capabilities and reports unsupported syntax; consult the Compatibility Matrix when sharing classes.
All official paths are installed and exercised from packed npm artifacts in CI. The suite covers framework builds plus interaction, keyboard, reduced-motion, SSR/hydration, diagnostics, source-map, tree-shaking, and bundle-budget cases where the target supports them.