Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

xstate@4.14.0

Minor Changes

• 119db8fb #1577 Thanks @davidkpiano! - Expressions can now be used in the stop() action creator:

  // ...
  actions: stop(context => context.someActor);

Patch Changes

• 8c78e120 #1570 Thanks @davidkpiano! - The return type of spawn(machine) will now be Actor<State<TContext, TEvent>, TEvent>, which is a supertype of Interpreter<...>.

• 602687c2 #1566 Thanks @davidkpiano! - Exit actions will now be properly called when an invoked machine reaches its final state. See #1109 for more details.

• 6e44d02a #1553 Thanks @davidkpiano! - The state.children property now properly shows all spawned and invoked actors. See #795 for more details.

• 72b0880e #1504 Thanks @Andarist! - Added status property on the Interpreter - this can be used to differentiate not started, running and stopped interpreters. This property is best compared to values on the new InterpreterStatus export.

@xstate/inspect@0.2.0

Minor Changes

• 1725333a #1599 Thanks @davidkpiano! - The @xstate/inspect package is now built with Rollup which has fixed an issue with TypeScript compiler inserting references to this in the top-level scope of the output modules and thus making it harder for some tools (like Rollup) to re-bundle dist files as this in modules (as they are always in strict mode) is undefined.

@xstate/react@1.0.2

Patch Changes

• c7927083 #1516 Thanks @davidkpiano! - The send function returned from the useService() now can take two arguments (an event type and payload), to match the behavior of @xstate/react version 0.x.

• db77623a #1516 Thanks @davidkpiano! - The send value returned from the useService() hook will now accept a payload, which matches the signature of the send value returned from the useMachine() hook:

  const [state, send] = useService(someService);
  
  // ...
  
  // this is OK:
  send('ADD', { value: 3 });
  
  // which is equivalent to:
  send({ type: 'ADD', value: 3 });

• 93f6db02 #1594 Thanks @Andarist! - Fixed an issue with internal setState in useService being called with 2 arguments instead of 1.

• 72b0880e #1504 Thanks @Andarist! - Fixed issue with useService returning an initial state for services in their final states.

[a-y-u-s-h]

Please merge and publish the minor version bump for @xstate/inspect. It includes a merged pull request which supposedly fixes "Waiting for connection" issue on local projects using Rollup or NextJS.