statelyai/xstate @xstate/react@4.0.0-beta.4 on GitHub

Major Changes

#3947 5fa3a0c74 Thanks @davidkpiano! - Removed the ability to pass a factory function as argument to useMachine and useInterpret.

#4006 42df9a536 Thanks @davidkpiano! - useActorRef is introduced, which returns an ActorRef from actor logic:

const actorRef = useActorRef(machine, { ... });
const anotherActorRef = useActorRef(fromPromise(...));

~~useMachine~~ is deprecated in favor of useActor, which works with machines and any other kind of logic

-const [state, send] = useMachine(machine);
+const [state, send] = useActor(machine);
const [state, send] = useActor(fromTransition(...));

~~useSpawn~~ is removed in favor of useActorRef

-const actorRef = useSpawn(machine);
+const actorRef = useActorRef(machine);

The previous use of `useActor(actorRef)` is now replaced with just using the `actorRef` directly, and with `useSelector`:

```diff
-const [state, send] = useActor(actorRef);
+const state = useSelector(actorRef, s => s);
// actorRef.send(...)

#4006 42df9a536 Thanks @davidkpiano! - useActor has been removed from the created actor context, you should be able to replace its usage with MyCtx.useSelector and MyCtx.useActorRef.
#3947 5fa3a0c74 Thanks @davidkpiano! - Implementations for machines on useMachine and useInterpret hooks should go directly on the machine via machine.provide(...), and are no longer allowed to be passed in as options.
```
-const [state, send] = useMachine(machine, {
-  actions: {
-    // ...
-  }
-});
+const [state, send] = useMachine(machine.provide({
+  actions: {
+    // ...
+  }
+}));
```
@xstate/react will detect that the machine's config is still the same, and will not produce the "machine has changed" warning.