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 main, this PR will be updated.
Releases
@xstate/vue@1.0.0
Major Changes
#3083
bc592582a
Thanks @Andarist! - The major version of this package had to be bumped to allow integrating with the typegen. This package will now require TS version 4.0 or greater.When using hooks from
@xstate/vue
it's recommended to skip providing explicit generics to them. Note that that generics list has changed since v1 and we now only accept a single generic,TMachine
.#3083
bc592582a
Thanks @Andarist! - Removed already deprecateduseService
from@xstate/vue
. You can replace its usage withuseActor
.Patch Changes
862697e29
Thanks @Andarist! - Fixed compatibility with Skypack by exporting some shared utilities from root entry of XState and consuming them directly in other packages (this avoids accessing those things using deep imports and thus it avoids creating those compatibility problems).xstate@4.30.3
Patch Changes
#3088
9f02271a3
Thanks @Andarist! - Added some internal@ts-ignore
comments to fix consuming projects that do not useskipLibCheck
.#3082
8d3f2cfea
Thanks @Andarist! - Fixed an issue with context type being inferred from too many places withincreateMachine
call and possibly ending up asany
for the entire machine.#3027
97ad964bd
Thanks @hedgepigdaniel! - Fixed an issue with not being able to callcreateMachine
in a generic context when the type for the context was generic and not concrete.#3084
50c271dc1
Thanks @Andarist! - Fixed an issue with context type defined usingschema.context
being sometimes widened based onconfig.context
. If both are given theschema.context
should always take precedence and should represent the complete type of the context.#3089
862697e29
Thanks @Andarist! - Fixed compatibility with Skypack by exporting some shared utilities from root entry of XState and consuming them directly in other packages (this avoids accessing those things using deep imports and thus it avoids creating those compatibility problems).#3087
ae9579497
Thanks @Andarist! - Fixed an issue withActorRefFrom
not resolving the typegen metadata from machine types given to it. This could sometimes result in types assignability problems, especially when using machine factories andspawn
.@xstate/graph@1.4.2
Patch Changes
862697e29
Thanks @Andarist! - Fixed compatibility with Skypack by exporting some shared utilities from root entry of XState and consuming them directly in other packages (this avoids accessing those things using deep imports and thus it avoids creating those compatibility problems).@xstate/inspect@0.6.3
Patch Changes
862697e29
Thanks @Andarist! - Fixed compatibility with Skypack by exporting some shared utilities from root entry of XState and consuming them directly in other packages (this avoids accessing those things using deep imports and thus it avoids creating those compatibility problems).@xstate/react@2.0.1
Patch Changes
862697e29
Thanks @Andarist! - Fixed compatibility with Skypack by exporting some shared utilities from root entry of XState and consuming them directly in other packages (this avoids accessing those things using deep imports and thus it avoids creating those compatibility problems).