Support matrix

Browsers, runtimes, engines and platforms MotionPR is tested with, and how many real-browser tests cover each.

On this page
  1. Browser tests per engine
AreaSupportedHow it is verified
Node.js22.12 or newerengines; doctor checks it. Tests run on Node.js 24 (and the package on 22)
ChromiumChrome for Testing 158.0.8127.18 (Playwright 1.65)Every browser test
FirefoxFirefox 159.0, Playwright build 1572Every browser test except the multi-engine CLI runs
WebKitWebKit 27.2, Playwright build 2388Every browser test except the multi-engine CLI runs
Several engines in one projectVerifiedCLI runs with --browser all, per-engine baselines, cross-browser comparison, 0.1 migration
Native CSS transitions / animationsVerified in all three enginesCapture engine and engine edge-case tests, demo app
Web Animations APIVerified in all three enginesReversed, cancelled, finished, delayed, keyframed, reused
CSS scroll-driven animationsMetadata onlyProgress follows scroll
GSAPVerified with 3.15.1 (range >=3.12 <4)10 browser tests per engine; ScrollTrigger: metadata + live progress
Anime.jsVerified with 4.5.0 (range >=4 <5)22 browser tests per engine, unit tests; v3 is not supported
LenisVerified with 1.3.27 (range >=1.1 <2)15 browser tests per engine; scroll motion, never replayed
macOSVerified (arm64), all three enginesDevelopment machine
LinuxCovered by the repository's CI, all three enginesubuntu-latest, one job per engine
WindowsNot coveredPaths are handled in code; no CI job yet

Browser tests per engine

The browser suites run once per engine (MOTIONPR_TEST_BROWSER=firefox pnpm test:integration); CI runs Chromium in the main job and Firefox and WebKit in a matrix.

SuiteChromiumFirefoxWebKit
Capture engine141414
Engine edge cases (transitions, animations, WAAPI, latency, scroll start, determinism)151515
GSAP adapter101010
Anime.js adapter222222
Lenis adapter151515
CLI end to end151212
Demo app: every intended change, nothing else (e2e)151515

The three CLI tests that only Chromium's run lists start all three engines in one project; they run once, in the main CI job, where every engine is installed.

"Verified" means covered by automated tests against a real browser in this repository. Outside a tested range, an adapter reports the engine as untested and keeps running. How the engines differ, and what is not supported, is in Browser support.