Version Packages

[github-actions[bot]]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@preact/signals-react@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-react-transform@0.3.0

Minor Changes

• #467 d7f43ef Thanks @andrewiggins! - Change opt-in/opt-out comment to @useSignals and @noUseSignals. Previous comments (@trackSignals & @noTrackSignals) still supported but deprecated.

Patch Changes

• Updated dependencies [d7f43ef]:
  • @preact/signals-react@2.0.0

[netlify[bot]]

❌ Deploy Preview for preact-signals-demo failed.

Name	Link
🔨 Latest commit	a8d5379a3e704078832563d665653ad148d7cf3f
🔍 Latest deploy log	https://app.netlify.com/sites/preact-signals-demo/deploys/6580d52adb740a00087fa0d4