fix: update dependency @preact/signals to v2

[renovate]

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package	Change	Age	Confidence
@preact/signals (source)	^1.2.3 -> ^2.3.1

---

Release Notes

preactjs/signals (@​preact/signals)

v2.3.1

Patch Changes

• #​744 b178480 Thanks @​rschristian! - Correct semver range to support beta releases of Preact v11

v2.3.0

Minor Changes

• #​727 8fe8dec Thanks @​JoviDeCroock! - Call into component tracking of the chrome extension

• #​681 6cc7005 Thanks @​JoviDeCroock! - Allow for naming your singals/computeds/effects

Patch Changes

• #​728 0fd9503 Thanks @​marvinhagemeister! - Fix prefresh HMR not working with useSignal.

• #​729 b45c2b6 Thanks @​rschristian! - Expand semver range to support the upcoming v11 beta release

• Updated dependencies [6cc7005]:

  • @​preact/signals-core@​1.12.0

v2.2.1

Compare Source

Patch Changes

• #​701 01f406c Thanks @​calebeby! - Narrow types for Show utility, the callback is truthy by design

• Updated dependencies [4045d2d]:

  • @​preact/signals-core@​1.11.0

v2.2.0

Compare Source

Minor Changes

• #​634 62bed44 Thanks @​JoviDeCroock! - Add an option to specify a watched/unwatched callback to a signal

Patch Changes

• Updated dependencies [587e702, 62bed44]:
  • @​preact/signals-core@​1.9.0

v2.1.1

Compare Source

Patch Changes

• #​684 a34eab2 Thanks @​JoviDeCroock! - Ensure we build the thing

v2.1.0

Compare Source

Minor Changes

• #​683 4b585a5 Thanks @​JoviDeCroock! - Provide @preact/signals/utils package with some helpers to make working with signals easier in Preact

v2.0.5

Compare Source

Patch Changes

• #​677 b990e7e Thanks @​JoviDeCroock! - We reduce the raf timeout to be just above a timeout that is associated with a 30hz refresh rate. This ensures that for hidden frames the timeout drift can't be too large, the drift being too high could lead to unexpected situations.

• #​679 f51eef4 Thanks @​WeirdConstructor! - Fix accessing signals from Preact Class Component constructor.

v2.0.4

Compare Source

Patch Changes

• #​668 36fcb2e Thanks @​JoviDeCroock! - Correctly set peerDep of signals

v2.0.3

Compare Source

Patch Changes

• #​666 f72e769 Thanks @​JoviDeCroock! - Fix array signals when used as jsx

v2.0.2

Compare Source

Patch Changes

• #​655 6a0284c Thanks @​JoviDeCroock! - Avoid usage of .base and check the _dom on the vnode instead

• #​660 df4df76 Thanks @​JoviDeCroock! - Bail out of the animation frame with a setTimeout in case the origin page is hidden

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 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

• #​595 499428a Thanks @​JoviDeCroock! - Align signal effects with animation-frames for better performance

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.

v1.3.2

Compare Source

Patch Changes

• #​641 e932cfc 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.

v1.3.1

Compare Source

Patch Changes

• #​620 4cda002 Thanks @​developit! - Simplify text update patch to avoid using new internals

• #​618 021c726 Thanks @​JoviDeCroock! - Ensure that the Effects versions are updated when using it as a JSX Signal

v1.3.0

Compare Source

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

---

Configuration

📅 Schedule: Branch creation - "after 10am on monday,before 5pm on monday" in timezone Asia/Tokyo, 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4a66945

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.