Skip to content

Releases: preactjs/signals

@preact/[email protected]

13 Jan 13:54
e4a9174
Compare
Choose a tag to compare

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/[email protected]

13 Jan 10:13
ddfe5f4
Compare
Choose a tag to compare

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.

@preact/[email protected]

13 Jan 13:54
e4a9174
Compare
Choose a tag to compare

Patch Changes

  • #640 503128f Thanks @andrewiggins! - Don't track signals read during an SSR render (e.g. renderToString, renderToStaticMarkup)

@preact/[email protected]

02 Jan 09:14
674c310
Compare
Choose a tag to compare

Major Changes

@preact/[email protected]

02 Jan 09:14
674c310
Compare
Choose a tag to compare

Patch Changes

@preact/[email protected]

17 Dec 07:47
9022d4a
Compare
Choose a tag to compare

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.

@preact/[email protected]

17 Dec 07:47
9022d4a
Compare
Choose a tag to compare

Minor Changes

Patch Changes

  • #611 57a7d38 Thanks @Xstoudi! - Silences noisy warnings about useLayoutEffect whilst using SSR by switching to an isomorphic layout effect hook

  • #624 18b2f29 Thanks @JoviDeCroock! - Fix the stubbed ReactElementType to use the newly added traditional element in v19

@preact/[email protected]

17 Dec 07:47
9022d4a
Compare
Choose a tag to compare

Minor Changes

Patch Changes

  • #628 c3e8e8c Thanks @Artur-! - Avoid cloning the top-level component function when we are
    prepending useSignals. This fixes compatability with fast-refresh
    as it requires the function identity to correctly leverage its
    cache.
  • Updated dependencies [18b2f29, 57a7d38, 18b2f29]:

@preact/[email protected]

27 Nov 19:43
d4ff246
Compare
Choose a tag to compare

Patch Changes

@preact/[email protected]

08 Aug 07:53
e046714
Compare
Choose a tag to compare

Minor Changes