Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 next, this PR will be updated.
next
is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exit
onnext
.Releases
[email protected]
Major Changes
#898
26986f417
Thanks @davidkpiano! - Sending a string event toactor.send('some string')
will now throw a proper error message.#3957
423c5ab72
Thanks @davidkpiano! - The machine.schema
property is now.types
:And the
.tsTypes
property is now.types.typegen
:#3968
eecb31b8f
Thanks @davidkpiano! - ThecreateEmptyActor()
function has been added to make it easier to create actors that do nothing ("empty" actors). This is useful for testing, or for some integrations such asuseActor(actor)
in@xstate/react
that require an actor:#3966
61db63bf4
Thanks @davidkpiano! - You can now import the following fromxstate
:The
send
action was removed from exports; usesendTo(...)
orraise(...)
instead.Patch Changes
ead287257
Thanks @davidkpiano! - Unresolved promises will now be properly persisted. The current behavior is to restart a promise that is unresolved.