David Khourshid

The workaround right now is to add the iframe _outside_ of Vue: ```html We're sorry but codesandbox doesn't work properly without JavaScript enabled. Please enable it to continue. ```

There are more potential signals than starting and stopping: ```ts // from XActor + Akka export type ActorSignal = | { type: ActorSignalType.Start } | { type: ActorSignalType.PostStop } |...

cc. @mattpocock @Andarist

> We too were bitten by this issue. I think this is very unintuitive behavior. If I start at some state I expect the machine to work like normal; and...

@nathanhammond Sorry for the delay in reviewing this! @Andarist and I discussed the need for a dynamic `stop(ctx => ctx.child)` and how it could be useful (and simpler) with regard...

Now that #1577 is in, we can simplify these docs: ----- ### Stopping Spawned Machines To stop a spawned machine, use the `actions.stop(...)` action creator and reference the spawned machine...

This is a very difficult TypeScript problem to solve, and we're still thinking about ways to improve typestates for v5, as the current way is unsound. cc. @Andarist

Agree with this. What is returned from `interpret()` should just be an `ActorRef` instead of something special. It was not done this way in v4 for "legacy"/historical reasons (machine interpretation...

@Andarist I fixed it 🔧

Can you share the code that you are using to store the `ctx`?