Mateusz Burzyński

@mellson with the current shape of this PR - the PR's title should be adjusted to reflect the current set of changes

Note that `actionMeta.state` might not always be what you think it is. For `assign` actions it's the "source state" (the state before transition) and for custom actions (functions) it's the...

> That would be something like you wrote (and could be applicable not only to delay but also to actions, guards and any other function): Yes, this is already supported...

All arguments can be destructured from the arguments object that we call your functions with in v5. `state` (or anything like it) is **not** part of this object though. I...

> So I need help. Is this a bug in @xstate/vue, or am I doing something wrong? It might be a problem with `@xstate/vue`. This package was written by the...

If I understand the issue correctly then this is what happens. 1. we call `child.stop()` in the parent from within parent's `update` (that's why when you "listen" to the parent,...

You can avoid serializing massive objects like this: ```ts inspect({ serialize: (_key, value) => { if (isSocket(value)) { return '[redacted Socket]'; } if (isChannel(value)) { return '[redacted Channel]'; } return...

@SvetlanaMuravlova @valorkin any chance to get some eyes on it? It might be an issue with https://github.com/ng-packagr/ng-packagr , kinda looks like something close to https://github.com/ng-packagr/ng-packagr/pull/2372 but I rechecked and that's...

Note that the issue is probably not specific to nullish coalescing operator. I'd expect this to either break on yields that don't yield an effect *or* on yields that mix...

> external code uses require('redux-saga') that use exports object as function instead its "default" property How is this possible? You can't do this in node today with our package. You...