-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
fix(deps): update xstate monorepo (major) #404
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-xstate-monorepo
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
2 times, most recently
from
October 29, 2023 03:50
6d2571b
to
d800af3
Compare
renovate
bot
changed the title
fix(deps): update dependency @xstate/react to v3
fix(deps): update xstate monorepo (major)
Dec 1, 2023
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
7 times, most recently
from
December 8, 2023 16:51
5a49de6
to
9511084
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
4 times, most recently
from
December 13, 2023 20:08
b60731e
to
c313aed
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
3 times, most recently
from
December 24, 2023 04:42
a35fd53
to
25310c9
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
2 times, most recently
from
January 11, 2024 16:36
e3f6948
to
aaf728a
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
2 times, most recently
from
January 29, 2024 16:24
eb66293
to
0021e5f
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
2 times, most recently
from
February 7, 2024 19:46
733a8e3
to
dce0d00
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
3 times, most recently
from
February 17, 2024 13:40
6b6c324
to
2229291
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
2 times, most recently
from
February 27, 2024 19:52
b32349a
to
6eabf19
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
2 times, most recently
from
March 2, 2024 08:49
527aee7
to
eb4606b
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
from
March 3, 2024 03:47
eb4606b
to
c60e61a
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
3 times, most recently
from
April 16, 2024 14:41
40c48b3
to
19884fa
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
from
April 17, 2024 01:28
19884fa
to
10276b0
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
from
April 24, 2024 21:56
10276b0
to
59248be
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
from
May 5, 2024 00:05
59248be
to
6b98e9c
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
2 times, most recently
from
June 6, 2024 16:49
c190a97
to
3707166
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
from
June 11, 2024 13:06
3707166
to
7a9390f
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
from
June 22, 2024 08:40
7a9390f
to
1d1dbff
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
from
July 13, 2024 03:20
1d1dbff
to
ca6f7a4
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
3 times, most recently
from
July 31, 2024 20:09
57a4775
to
e75a1c2
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
3 times, most recently
from
August 15, 2024 16:18
0da368c
to
caf8f2c
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
2 times, most recently
from
September 6, 2024 09:09
2add65b
to
0f8aab2
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
from
September 8, 2024 16:03
0f8aab2
to
b43bb16
Compare
renovate
bot
force-pushed
the
renovate/major-xstate-monorepo
branch
from
September 21, 2024 10:05
b43bb16
to
09fa256
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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 contains the following updates:
1.6.3
->4.1.3
4.38.3
->5.18.2
Release Notes
statelyai/xstate (@xstate/react)
v4.1.3
Compare Source
Patch Changes
25963966c394fc904dc9b701a420b6e204ebe7f7
]:v4.1.2
Compare Source
Patch Changes
#5055
ad38c35c37
Thanks @SandroMaglione! - Updated types ofuseActor
,useMachine
, anduseActorRef
to requireinput
when defined insidetypes/input
.Previously even when
input
was defined insidetypes
,useActor
,useMachine
, anduseActorRef
would not make the input required:With this change the above code will show a type error, since
input
is now required:This avoids runtime errors when forgetting to pass
input
when defined insidetypes
.v4.1.1
Compare Source
Patch Changes
#4844
5aa6eb05c
Thanks @davidkpiano! - TheuseSelector(…)
hook from@xstate/react
is now compatible with stores from@xstate/store
.v4.1.0
Compare Source
Minor Changes
#4231
c2402e7bc
Thanks @davidkpiano! - Theactor
passed touseSelector(actor, selector)
is now allowed to beundefined
for an actor that may not exist yet. For actors that may beundefined
, thesnapshot
provided to theselector
function can also beundefined
:v4.0.3
Compare Source
Patch Changes
#4695
52900a084
Thanks @davidkpiano! - Options increateActorContext
are now properly merged with provider options. Previously, provider options replaced the actor options.v4.0.2
Compare Source
Patch Changes
1f2ccb97c
Thanks @davidkpiano! - Typegen-based types for detecting missing implementations have been removed internally.v4.0.1
Compare Source
Patch Changes
d7f220225
Thanks @davidkpiano! - Fix an issue whereafter
transitions do not work in React strict mode. Delayed events (including fromafter
transitions) should now work as expected in all React modes.v4.0.0
Compare Source
Major Changes
#3947
5fa3a0c74
Thanks @davidkpiano! - Removed the ability to pass a factory function as argument touseMachine
.#4006
42df9a536
Thanks @davidkpiano! -useActorRef
is introduced, which returns anActorRef
from actor logic:~~
useMachine
~~ is deprecated in favor ofuseActor
, which works with machines and any other kind of logic~~
useSpawn
~~ is removed in favor ofuseActorRef
#4050
fc88dc8e6
Thanks @davidkpiano! - Theoptions
prop has been added (back) to theContext.Provider
component returned fromcreateActorContext
:#4006
42df9a536
Thanks @davidkpiano! -useActor
has been removed from the created actor context, you should be able to replace its usage withMyCtx.useSelector
andMyCtx.useActorRef
.#4265
1153b3f9a
Thanks @davidkpiano! - FSM-related functions have been removed.#3947
5fa3a0c74
Thanks @davidkpiano! - Implementations for machines onuseMachine
hooks should go directly on the machine viamachine.provide(...)
, and are no longer allowed to be passed in as options.#3148
7a68cbb61
Thanks @davidkpiano! - RemovedgetSnapshot
parameter from hooks. It is expected that the receivedactorRef
has to have agetSnapshot
method on it that can be used internally.Minor Changes
5fb3c683d
Thanks @Andarist! -exports
field has been added to thepackage.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.409552cf8
Thanks @davidkpiano! - TheuseMachine
function is an alias ofuseActor
.340aee643
Thanks @Andarist! - Fast refresh now works as expected for most use-cases.fc88dc8e6
Thanks @davidkpiano! - TheobserverOrListener
argument has been removed from the 3rd argument ofcreateActorContext(logic, options)
.v3.2.2
Compare Source
Patch Changes
6665f0a32
Thanks @c-w! - Updated the allowed range for theuse-isomorphic-layout-effect
dependency.v3.2.1
Compare Source
Patch Changes
c110c429d
Thanks @Andarist! - Fixed compatibility of the generated TS types forcreateActorContext
with pre-4.7.v3.2.0
Compare Source
Minor Changes
#3814
494203b3d
Thanks @Andarist! - TheProvider
fromcreateActorContext(...)
now accepts theoptions={{...}}
prop that takes the same object as the second argument to theuseMachine(machine, options)
hook.These options are no longer passed as the second argument to the
createActorContext(machine)
function:v3.1.2
Compare Source
Patch Changes
b53856d28
Thanks @farskid! - Interpreter options can now be specified in the second argument of createActorContext(machine, options).v3.1.1
Compare Source
Patch Changes
51d254692
Thanks @Andarist! - Fixed an issue that caused the internally useduseSyncExternalStore
to warn about the computed snapshot not being cached when a not-started machine servive was passed touseActor
.v3.1.0
Compare Source
Minor Changes
#3778
f12248b23
Thanks @davidkpiano! - ThecreateActorContext(...)
helper has been introduced to make global actors easier to use with React. It outputs a React Context object with the following properties:.Provider
- The React Context provider.useActor(...)
- A hook that can be used to get the current state and send events to the actor.useSelector(...)
- A hook that can be used to select some derived state from the actor's state.useActorRef()
- A hook that can be used to get a reference to the actor that can be passed to other componentsUsage:
v3.0.2
Compare Source
Patch Changes
4190c3fd6
Thanks @davidkpiano! - Computing the initial state is now consistent withuseMachine
anduseActor
, avoiding stale initial state problems with nested machinesv3.0.1
Compare Source
Patch Changes
#3456
131d429ab
Thanks @davidkpiano! - AddshallowEqual
helper comparator function.#3500
0dfc6d92f
Thanks @Andarist! - Fixed an issue withuseSelector
always computing fresh snapshots internally for uninitialized services. This avoids the internaluseSyncExternalStore
from warning about the snapshot value not being cached properly.v3.0.0
Compare Source
Major Changes
#2939
360e85462
Thanks @Andarist! - This package now accepts React 18 as a peer dep and the implementation has been rewritten to useuse-sync-external-store
package. This doesn't break compatibility with older versions of React since we are using the shim to keep compatibility with those older versions.#2939
360e85462
Thanks @Andarist! -asEffect
andasLayoutEffect
action creators were removed. They were not fitting the React model that well and could lead to issues as their existence suggested that they are easy to use.To execute actions at those exact times you can always either just call your stuff directly from those effects or send events to the machine from those effects and execute explicit actions in response to said events.
#2939
360e85462
Thanks @Andarist! - The signatures ofuseMachine
anduseService
integrating with@xstate/fsm
were changed. They now only accept a single generic each (TMachine
andTService
respectively). This has been done to match their signatures with the related hooks that integrate withxstate
itself.Patch Changes
#2939
360e85462
Thanks @Andarist! - In v2 we have changed signatures ofuseMachine
anduseInterpret
. Instead of accepting a list of generics they now only support a single generic:TMachine
. This change, erroneously, was only introduced to types targeting [email protected] but the types targeting previous TS releases were still using the older signatures. This has now been fixed and users of older TS versions should now be able to leverage typegen with@xstate/react
.#2939
360e85462
Thanks @Andarist! -useMachine
forxstate
now correctly rerenders with the initial state when the internal service is being restarted. This might happen during Fast Refresh and now you shouldn't be able to observe this stale state that didn't match the actual state of the service.#2939
360e85462
Thanks @Andarist! -useMachine
for@xstate/fsm
now starts the service in an effect. This avoids side-effects in render and improves the compatibility withStrictMode
.#2939
360e85462
Thanks @Andarist! - Implementations given touseMachine
targeting@xstate/fsm
are now updated in a layout effect. This avoid some stale closure problems for actions that are executed in response to events sent from layout effects.Updated dependencies [
360e85462
,360e85462
]:v2.0.1
Compare Source
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).v2.0.0
Compare Source
Major Changes
eeadb7121
Thanks @TkDodo! - - Replaceuse-sync-external-store/shim
withuseSyncExternalStore
from React.getSnapshot
inuseSyncExternalStore
.getServerSnapshot
inuseSyncExternalStore
.store
to always be defined inuseSelector
Configuration
📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday" in timezone Europe/London, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.