Mark Deutsch

Yeah I'm running into this as well in a Remix/Vitest/RTL setup. `blur` events on a textfield seems to be what triggers it for me - whether that's via a simulated...

> Hi guys, any workaround on this? Depends what you consider a workaround… We swapped our Vitest unit tests over to ole `jsdom` with zero friction.

> We hope to support aliases in the future, so thank you for opening this issue. We will get back to you if we release a new version that should...

Further debugging shows that `.insert` appears to be broken as well. A quick tweak of that CodeSandbox to use `.insert(..., 0, ...)` instead also fails. This is obviously expected, given...

An interesting behaviour I've noticed is that the `initialValuesEqual` callback I provide isn't being called all the time. I defined it as so: ``` (a, b) => { console.log('isEqual', a,...

The weirdest part I see is that in my form component, `props.form.getState().initialValues` is correct, even when `props.initialValues` isn't. I feel like that should be a clue but it isn't to...

So, I wonder whether this is a case of us being naughty users here. We use the `subscription` prop to specify a few items, but `initialValues` wasn't one of them....