Matt Perry

Glad you’re having more luck with it. Definitely feels closer to your use case and won’t add any bloat for people who also use Pose. Sorry I haven’t got round...

Yeah good point, we'll add a deprecation warning at the top of these pages.

Yeah I think it's a great idea. We want to introduce one for the Framer Motion docs too, so I'll try and bundle the two jobs together.

A note on the above: This will only expose imperative APIs (`animate`, `scroll`, `inView`) so won't change the status of layout animations here.

Motion One is fully in Typescript, not sure where you’d find JS files. But it wouldn’t be able to support driver as it’s based on WAAPI

@majido > First it is not clear to me why a stateless animator needs to receive "options" given that its output should only be dependent on its animate() input currentTime....

@majido What's the distinction between `css-animationworklet-1` and `2` labels? IMO this feature is MVP in making this a usable API. From my current hacking around, even animations that are told...

Hi all. Author of Popmotion and Framer Motion here, I've spent a fair amount of time working with value ranges and I'd love to ditch a bunch of code in...

> That's not now JS works, if the constructor is expecting RGB(r, g, b) and you call it with RGB(1), you're passing (1, undefined, undefined), shifting arguments around is a...

> (sigh) I'm not saying it can't be done, I'm saying it shouldn't. It violates the principle of least surprise, e.g. any JS programmer unfamiliar with the API will presume...