Preactjs Signals Versions Save

Patch Changes

• #535 58befba Thanks @jviide! - Publish packages with provenance statements

• Updated dependencies [d846def]:

  • @preact/[email protected]

Patch Changes

• #535 58befba Thanks @jviide! - Publish packages with provenance statements

• Updated dependencies [d846def, cb6bdab, d846def, d846def, d846def]:

  • @preact/[email protected]

Patch Changes

• #535 58befba Thanks @jviide! - Publish packages with provenance statements

• Updated dependencies [d846def, cb6bdab, d846def, d846def, d846def]:

  • @preact/[email protected]

Minor Changes

• #525 cb6bdab Thanks @jviide! - Allow setting a signal value inside a computed

Patch Changes

• #535 58befba Thanks @jviide! - Publish packages with provenance statements

• #529 ec5fe42 Thanks @jviide! - Document effect cleanups

• #512 d7f2afa Thanks @jviide! - Always reset the evaluation context upon entering an untracked block

• #531 d17ed0d Thanks @jviide! - Add JSDocs for exported core module members

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.

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.

1.3.8

Patch Changes

• #456 b0b2a5b Thanks @XantreGodlike! - Ensure types are resolved against built .d.ts rather than source .ts

0.2.0

Minor Changes

• #458 0c0d89f Thanks @andrewiggins! - Only prepend useSignals call if we can't determine whether a function is a component or hook

• #459 06d4c10 Thanks @andrewiggins! - Wrap custom hooks in try/finally when using react-transform

• #446 09f3ed7 Thanks @andrewiggins! - Use function expression name to determine if it is a Component and should be transformed.

1.5.1

Patch Changes

• #451 990f1eb Thanks @dcporter! - Removes backward-incompatible type export from signals core.

0.1.1

Patch Changes

• #439 fb6b050 Thanks @andrewiggins! - Remove top-level requirement from react-transform

• #413 ad6305c Thanks @XantreGodlike! - Added 'module:' prefix to readme to babel recognized plugin correctly

• #421 f80b251 Thanks @andrewiggins! - Add an "all" mode to the react transform that transforms all components to be reactive to signals

• #441 4c433c3 Thanks @andrewiggins! - Add support for auto-transforming more ways to specify components: object methods, member assignments, export default components, components wrapped in HoCs like memo and forwardRef

• #444 2939812 Thanks @andrewiggins! - Add support for auto transforming Components declared as object properties

• #442 76babcb Thanks @andrewiggins! - Add debug logging to inspect what components are transformed by plugin