Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version Packages (alpha) #3375

Merged
merged 1 commit into from
Jan 7, 2023
Merged

Version Packages (alpha) #3375

merged 1 commit into from
Jan 7, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jun 1, 2022

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, run changeset pre exit on next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

xstate@5.0.0-alpha.1

Major Changes

  • #3455 ec39214c8 Thanks @davidkpiano! - The interpreter.onStop(...) method has been removed. Use an observer instead via interpreter.subscribe({ complete() { ... } }) instead.

  • #3455 ec39214c8 Thanks @davidkpiano! - The .send(...) method on interpreter.send(...) now requires the first argument (the event to send) to be an object; that is, either:

    • an event object (e.g. { type: 'someEvent' })
    • an SCXML event object.

    The second argument (payload) is no longer supported, and should instead be included within the object:

    -actor.send('SOME_EVENT')
    +actor.send({ type: 'SOME_EVENT' })
    
    -actor.send('EVENT', { some: 'payload' })
    +actor.send({ type: 'EVENT', some: 'payload' })
  • #3455 ec39214c8 Thanks @davidkpiano! - Reading the initial state from an actor via actor.initialState is removed. Use actor.getInitialState() instead.

  • #3455 ec39214c8 Thanks @davidkpiano! - The matchState(...) helper function is removed.

  • #3455 ec39214c8 Thanks @davidkpiano! - The strict: true option for machine config has been removed.

  • #3455 ec39214c8 Thanks @davidkpiano! - The interpreter.onError(...) method has been removed. Use interpreter.subscribe({ error(err) => { ... } }) instead.

  • #3455 ec39214c8 Thanks @davidkpiano! - Interpreter['off'] method has been removed.

  • #3455 ec39214c8 Thanks @davidkpiano! - .nextState method has been removed from the Interpreter. State#can can be used to check if sending a particular event would lead to a state change.

  • #3187 c800dec47 Thanks @davidkpiano! - The createModel() function has been removed in favor of relying on strong types in the machine configuration.

  • #3455 ec39214c8 Thanks @davidkpiano! - sync option has been removed from invoke and spawn.

Minor Changes

  • #3727 5fb3c683d Thanks @Andarist! - exports field has been added to the package.json manifest. It limits what files can be imported from a package - it's no longer possible to import from files that are not considered to be a part of the public API.

Patch Changes

  • #3455 ec39214c8 Thanks @davidkpiano! - Fixed an issue with inline actions not being correctly executed when there was an equally named action provided through the implementations argument.

  • #3487 1b6e3dfb8 Thanks @Andarist, @davidkpiano! - Make it impossible to exit a root state. For example, this means that root-level transitions specified as external transitions will no longer restart root-level invocations. See #3072 for more details.

  • #3389 aa8f5d5fd Thanks @Andarist! - Fixed the declared signature of one of the StateMachine's methods to avoid using a private name this. This makes it possible to emit correct .d.ts for the associated file.

  • #3374 a990f0ed1 Thanks @Andarist! - Fixed an issue with actors not being reinstantiated correctly when an actor with the same ID was first stopped and then invoked/spawned again in the same microstep.

  • #3390 7abc41759 Thanks @Andarist! - Added back UMD builds. Please note that XState now comes with multiple entrypoints and you might need to load all of them (XState, XStateActions, XStateGuards, etc.). It's also worth mentioning that those bundles don't reference each other so they don't actually share any code and some code might be duplicated between them.

@xstate/fsm@3.0.0-alpha.0

Major Changes

  • #3455 ec39214c8 Thanks @davidkpiano! - The .send(...) method on interpreter.send(...) now requires the first argument (the event to send) to be an object, e.g. { type: 'someEvent' }.

    -actor.send('SOME_EVENT')
    +actor.send({ type: 'SOME_EVENT' })

Minor Changes

  • #3727 5fb3c683d Thanks @Andarist! - exports field has been added to the package.json manifest. It limits what files can be imported from a package - it's no longer possible to import from files that are not considered to be a part of the public API.

@xstate/react@4.0.0-alpha.1

Minor Changes

  • #3727 5fb3c683d Thanks @Andarist! - exports field has been added to the package.json manifest. It limits what files can be imported from a package - it's no longer possible to import from files that are not considered to be a part of the public API.

Patch Changes

@xstate/vue@3.0.0-alpha.1

Minor Changes

  • #3727 5fb3c683d Thanks @Andarist! - exports field has been added to the package.json manifest. It limits what files can be imported from a package - it's no longer possible to import from files that are not considered to be a part of the public API.

Patch Changes

@codesandbox-ci
Copy link

codesandbox-ci bot commented Jun 1, 2022

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 6017d0e:

Sandbox Source
XState Example Template Configuration
XState React Template Configuration

@github-actions github-actions bot force-pushed the changeset-release/next branch 3 times, most recently from 6e10749 to 555cbd9 Compare June 8, 2022 12:27
@github-actions github-actions bot force-pushed the changeset-release/next branch 2 times, most recently from 7b5de5e to cae86ba Compare December 28, 2022 11:10
@davidkpiano davidkpiano merged commit 8dd8831 into next Jan 7, 2023
@davidkpiano davidkpiano deleted the changeset-release/next branch January 7, 2023 20:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant