David Khourshid

@kolorfilm You should not need to specify any generic parameters in your machine.

Closing this as it is now recommended to use `immer` directly with XState (if desired) instead of with `@xstate/immer`: https://stately.ai/docs/immer

> Please correct me if I'm doing something wrong here, but IMHO an API using shared composables would be better suited and more appealing to existing Vue developers, as proposed...

Closing due to drift

> @davidkpiano Do you prefer a separate PR to update github-action to Node 20? (Can also update PR to update github-action) Yes please @chimurai

For "on stop", which is still an important "event" to listen for, we can just listen for the snapshot `status === 'stopped'`, right?

> I really like this idea, but I think it's going to be very easy to forget to use `step()` somewhere, and that would have really unpleasant consequences when trying...

> could we remove first parameter of step? how do you think about using reference check of promise as React's useThenable? If we remove the first parameter, then 1) we...

I'd appreciate a PR for this one if you'd like to fix it @pokey

This is fixed in XState v5 beta: https://codesandbox.io/s/xstate-meta-bug-forked-f2s2l3?file=/src/index.js If you want, you can try your hand at fixing it in v4. It likely has to do with how the `State`...