motionpr demo

Capture the bundled demo app in two versions, compare them and open a real report.

On this page
  1. The changes it contains
Shell
npx motionpr demo [options]

Captures the bundled demonstration app (Halcyon Studio, a fictional design studio) twice — the baseline variant and a candidate with deliberate motion changes — compares them and opens the report. It needs a browser (npx motionpr install, Chromium by default) but no project and no config.

OptionDescription
-o, --output <dir>Where to write the demo output (default: the system temp directory)
-s, --scenario <id>Only some demo scenarios; repeatable
--browser <name>chromium (default), firefox or webkit
--open / --no-openOpen the report (default: when interactive)

The changes it contains

ScenarioEngineChange in the candidate
navigationCSS transitionpanel duration 320 → 560 ms, easing expo-out → ease-in-out
modalCSS animationdialog entrance easing now overshoots
work-gridWAAPIstagger 70 → 120 ms; a decorative glow without an id changes
faqCSS transitionanswer reveal gains a 120 ms delay
cta-hoverCSS transitionhover lift −2 → −6 px with a scale-up
image-revealCSS animationclip-path reveal removed
featuresCSS animationa new "New" badge animation is added
gsap-introGSAPtimeline ease power3.out → back.out(1.7), duration 0.6 s → 0.9 s
anime-servicesAnime.jsstagger 60 → 110 ms
anime-processAnime.js timeline"design" moves from -=120 to +=120; bar 700 → 900 ms
lenis-journalLenis + GSAPLenis lerp 0.1 → 0.06; ScrollTrigger parallax starts at "top 70%"

Every one of these is found, and nothing else is reported: the repository's end-to-end suite (e2e/demo-expectations.spec.ts) checks both, in Chromium, Firefox and WebKit. The result is 55 differences in Chromium and Firefox: 1 critical, 35 warnings, 18 info and 1 uncertain. WebKit finds the same critical and warning differences and adds one to three informational notes that vary between runs: at its 30 fps, trigger latency and the Lenis scroll's curve shape are measured more coarsely. The comparison fails on purpose (an animation was removed, which is critical by default); demo itself exits 0, and with --json it prints the exitCode that run would have returned (1).

Shell
npx @erenthedeveloper0/motionpr@alpha demo                 # without installing anything
npx motionpr demo -s navigation -s gsap-intro --no-open     # two scenarios, print the path
npx motionpr demo --browser firefox                        # the same demo in Firefox

The same report is published on the website: demo report.