Documentation

v2 compatibility

The tested Motionwind v2 support matrix for every official framework and capability.

Motionwind v2 treats compatibility as executable data. CI validates this table against each adapter's exported capability contract and installs every starter from packed npm artifacts.

FrameworkTierGesturesScrollLayoutDragVariantsSVGReduced motionSSR / hydration
Next.jsStablePassPassPassPassPassPassPassPass
React + ViteStablePassPassPassPassPassPassPassN/A
Vue + ViteStablePassWarningPassPassPassPassPassN/A
NuxtStablePassWarningPassPassPassPassPassPass
Vanilla JavaScriptStablePassPassUnsupportedUnsupportedUnsupportedPassPassN/A
Expo / React NativeBetaBetaBetaWarningWarningBetaWarningPassN/A

“Warning” means the adapter detects the syntax, explains the capability gap, and leaves direct Motion or platform APIs available. It never means silently ignored. The canonical source is fixtures/compatibility-matrix.json.

The golden suite covers hover, tap, focus and keyboard access, enter/exit, in-view, scroll linkage, drag, layout, variants, SVG paths, presets, strict diagnostics, reduced motion, SSR output, hydration, source maps, tree shaking, and bundle budgets. Framework jobs install and build Next.js, React/Vite, Vue/Vite, Nuxt, vanilla, and Expo from the exact tarballs intended for npm. Their browser scenarios are read from the same matrix, assert declared scale values instead of merely checking for a transform, and fail on runtime, console, hydration, high-severity, or critical security errors.

React Native remains beta: v2 supports the shared parser, presets, plugins, timing adaptation, variants, scroll context, and reduced motion. Drag, layout transitions, in-view orchestration, and SVG report actionable warnings and require direct platform APIs until their adapter fixtures reach parity.