Christian Silver
Christian Silver
@alexeygrigorev happy to chat about it - send me an email at [email protected]
This took me ages to get to the bottom of when migrating to Vite. Until this gets fixed, you can manually add entries to change the offending modules from esm...
~~Submitted without finishing, oops. I'll edit with the rest :)~~ Done!
Good to know what would line up with your opinions if I were to open a PR. Removing dependencies on `formidable`, `qs` and `async` is very straight-forward. If you change...
One more point, the readme has this line: > - Exploring write-once validation that works on the client and the server. There are some unique advantages to using the same...
@gurkerl83 you're right that this no longer causes the animation to become stuck. But that's because the component never suspends, so it just means it's no longer running into the...
@gurkerl83 there are plenty of workarounds to make sure a component doesn't suspend in isolated cases. Regardless, I'm pretty sure this is a bug in Framer Motion and (in my...
@mattgperry thanks for investigating! Any suggestions for workarounds in the meantime? Is there a way to force an animation to restart?
@mattgperry I don't suppose you've had any time to further investigate this? The bug is particularly problematic with AnimatePresence where a suspense can prevent an element from unmounting successfully.
@mattgperry are you saying that this should work out-of-the-box in React 19, or the required fixes for double-invocation in strict mode will also fix this? [Going by the React 19...