Matt Perry

The technical reason behind this looks like when the component throws, the `motion.div` doesn't re-render but its `ref` function is passed `null` (an unmount signal). Then, when the component stops...

Thanks to the double invocation of `ref` functions in React 19 strict mode I believe this will be fixed with that.

Yeah the latter. I'm working on a PR that will merge in the logic changes I made for React 19 so it could be fixed before then.

Ah apologises this doesn't seem to have fixed it.

I’ll have to have a closer look when I’m back but your bundler or its setup is almost certainly at fault here, I’ve never even heard of this. It should...

Is it possible to add a test on `inertia` for this behaviour?

Closing as the added failing test was fixed by a update in the meantime (changing the `>` on that line to a `>=`)

Thanks for the PR! Will publish now

Could you please open a new ticket with a working sandbox? For me that opens to a default repo

Hey man thanks for opening this - for some reason I wasn't subscribed. I'll take a look.