Update dependency @preact/signals to v2 #124
Open
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.3.2
->2.0.1
Release Notes
preactjs/signals (@preact/signals)
v2.0.1
Compare Source
Patch Changes
#647
655905b
Thanks @jviide! - Ensure that text effects get disposed#630
4b9144f
Thanks @JoviDeCroock! - Change the way we deal with state settling hooks, when we know we are dealing with hooks that can settle their A -> B -> A state (and wind up at the same value). We should not verbatim rerender in our custom shouldComponentUpdate. Instead we should trust that hooks have handled their own state settling.v2.0.0
Compare Source
Major Changes
#604
fea3e8d
Thanks @JoviDeCroock! - Defer all DOM updates by an animation frame, this should make it sothat any previously synchronous DOM update will be instead delayed by an
animation frame. This allows Preact to first perform its own render
cycle and then our direct DOM updates to occur. These will now
be performed in a batched way which is more performant as the browser
is prepared to handle these during the animation frame.
This does impact how Preact based signals are tested, when
you perform a signal update, you'll need to wrap it in
act
. In a waythis was always the case, as a signal update that resulted in
a Preact state update would require it to be wrapped in
act
, butnow this is the norm.
Minor Changes
499428a
Thanks @JoviDeCroock! - Align signal effects with animation-frames for better performancePatch Changes
8e6e2de
Thanks @JoviDeCroock! - Change timing to a double microtask so we are behind the Preact render queue but can't delay as much as a user-input coming in.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.