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

build(deps): bump @preact/signals from 1.3.1 to 2.0.1 #1397

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 14, 2025

Bumps @preact/signals from 1.3.1 to 2.0.1.

Release notes

Sourced from @​preact/signals's releases.

@​preact/signals-react@​2.0.1

Patch Changes

@​preact/signals@​2.0.1

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.

@​preact/signals-react@​2.0.0

2.0.0

Major Changes

  • #467 d7f43ef Thanks @​andrewiggins! - Remove auto tracking using React internals from signals-react package

    Before this change, importing @preact/signals-react would invoke side effects that hook into React internals to automatically track signals. This change removes those side effects and requires consumers to update their code to continue using signals in React.

    We made this breaking change because the mechanism we were using to automatically track signals was fragile and not reliable. We've had multiple issues reported where signals were not being tracked correctly. It would also lead to unexpected errors that were hard to debug.

    For some consumers and apps though, the current mechanism does work. If you'd like to continue using this mechanism, simply add import "@preact/signals/auto"; to the root of your app where you call ReactDOM.render. For our newly supported ways of using signals in React, check out the new Readme for @preact/signals-react.

@​preact/signals@​2.0.0

Major Changes

  • #604 fea3e8d Thanks @​JoviDeCroock! - Defer all DOM updates by an animation frame, this should make it so that 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 way this was always the case, as a signal update that resulted in a Preact state update would require it to be wrapped in act, but now this is the norm.

Minor Changes

Patch Changes

... (truncated)

Changelog

Sourced from @​preact/signals's changelog.

2.0.1

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.

2.0.0

Major Changes

  • #604 fea3e8d Thanks @​JoviDeCroock! - Defer all DOM updates by an animation frame, this should make it so that 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 way this was always the case, as a signal update that resulted in a Preact state update would require it to be wrapped in act, but now this is the norm.

Minor Changes

Patch Changes

  • #609 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.

1.3.0

Minor Changes

  • #578 931404e Thanks @​JoviDeCroock! - Allow for passing no argument to the signal and the type to be automatically inferred as T | undefined

Patch Changes

  • Updated dependencies [931404e]:
    • @​preact/signals-core@​1.7.0

1.2.3

Patch Changes

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot requested review from shakyShane, mgurgel and a team as code owners January 14, 2025 17:06
@dependabot dependabot bot added dependencies Update one or more dependencies version major Increment the major version when merged labels Jan 14, 2025
Copy link

netlify bot commented Jan 14, 2025

Deploy Preview for content-scope-scripts canceled.

Name Link
🔨 Latest commit 7ddaf57
🔍 Latest deploy log https://app.netlify.com/sites/content-scope-scripts/deploys/6798ba7a57ce8f0008460957

Copy link

github-actions bot commented Jan 14, 2025

Temporary Branch Update

The temporary branch has been updated with the latest changes. Below are the details:

Please use the above install command to update to the latest version.

@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/main/preact/signals-2.0.1 branch 5 times, most recently from 2f4072f to 9edbb5b Compare January 21, 2025 10:54
Bumps [@preact/signals](https://github.com/preactjs/signals/tree/HEAD/packages/preact) from 1.3.1 to 2.0.1.
- [Release notes](https://github.com/preactjs/signals/releases)
- [Changelog](https://github.com/preactjs/signals/blob/main/packages/preact/CHANGELOG.md)
- [Commits](https://github.com/preactjs/signals/commits/@preact/[email protected]/packages/preact)

---
updated-dependencies:
- dependency-name: "@preact/signals"
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/main/preact/signals-2.0.1 branch from 9edbb5b to 7ddaf57 Compare January 28, 2025 11:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Update one or more dependencies version major Increment the major version when merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants