@preact/signals-react 1.1.0

Minor Changes

• #91 fb74bb9 Thanks @JoviDeCroock! - add useSignalEffect hook

@preact/signals-core 1.2.0

This release improves performance of signals across all measurements. We want to especially highlight @jviide 's work in #161 here as it did outstanding strides on reducing memory usage, improving performance and ending up making signals one (if not the) fastest reactive library at the time of this writing 🎉

Minor Changes

• #183 79ff1e7 Thanks @jviide! - Add ability to run custom cleanup logic when an effect is disposed.

  effect(() => {
    console.log("This runs whenever a dependency changes");
    return () => {
      console.log("This runs when the effect is disposed");
    });
  });

• #170 3e31aab Thanks @jviide! - Allow disposing a currently running effect

Patch Changes

• #188 b4611cc Thanks @jviide! - Fix .subscribe() unexpectedly tracking signal access

• #162 9802da5 Thanks @developit! - Add support for Signal.prototype.valueOf

• #161 6ac6923 Thanks @jviide! - Remove all usages of Set, Map and other allocation heavy objects in signals-core. This substaintially increases performance across all measurements.

@preact/signals 1.0.4

Patch Changes

• #147 3556499 Thanks @developit! - Improve performance when rendering Signals as Text in Preact.

• #148 b948745 Thanks @marvinhagemeister! - Move types field in package.json to the top of the entry list to ensure that TypeScript always finds it.

• #153 0da9ce3 Thanks @developit! - Optimize the performance of prop bindings in Preact

@preact/signals-react 1.0.2

Patch Changes

• #147 3556499 Thanks @developit! - Improve performance when rendering Signals as Text in Preact.

• #148 b948745 Thanks @marvinhagemeister! - Move types field in package.json to the top of the entry list to ensure that TypeScript always finds it.

• #146 9e798fd Thanks @CodyJasonBennett! - fix(react): track owners separately, mutate updaters with dispatcher

@preact/signals-core 1.1.1

Patch Changes

• #143 f2ba3d6 Thanks @Pauan! - Simplify batch() to use a single flag instead of a counter

• #150 160ea77 Thanks @marvinhagemeister! - Fix computed signal being re-calculated despite dependencies not having changed

• #137 4385ea8 Thanks @jviide! - Fix .subscribe's TypeScript type

• #148 b948745 Thanks @marvinhagemeister! - Move types field in package.json to the top of the entry list to ensure that TypeScript always finds it.

• #149 00a59c6 Thanks @marvinhagemeister! - Fix invalidated signals inside batch() not being refreshed when read inside a batching operation. This fixes a regression.

@preact/[email protected]

Patch Changes

• 62439c9: Fixes invalid React peer dependency range for environments with strict peerDeps - #105 @rschristian

@preact/signals-core 1.1.0

Minor Changes

• bc0080c: experimental: Add .subscribe()-method to signals to add support for natively using signals with Svelte - #134 @marvinhagemeister

Patch Changes

• 336bb34: Don't mangle Signal class name - #100 @marvinhagemeister
• 7228418: Fix incorrectly named variables and address typos in code comments. - #129 @elliotwaite
• 32abe07: Fix internal API functions being able to unmark non-invalidated signals - #112 @marvinhagemeister
• 4782b41: Fix conditionally signals (lazy branches) not being re-computed upon activation - #127 @marvinhagemeister
• bf6af3b: Fix a memory leak when computed signals and effects are removed - #117 @developit