Repository navigation
Releases: preactjs/signals
Release list
@preact/signals@2.11.4
@preact/signals-core@1.14.5
Patch Changes
-
#987
7528bceThanks @SisyphusZheng! - Dispose captured effects when acreateModelfactory throws. -
#988
500b790Thanks @SisyphusZheng! - End the batch when a self-disposing effect's cleanup throws. -
#984
19e6e73Thanks @SisyphusZheng! - FixcreateModelto also wrap class prototype methods as actions. This includestoString/toJSON, and the actions are not auto-bound.
@preact/signals-agent-vite@0.1.4
Patch Changes
- #993
07b53adThanks @JoviDeCroock! - Fix the injected client splitting element class names on the lettersinstead of whitespace.
@preact/signals@2.11.3
Patch Changes
- #991
04445baThanks @JoviDeCroock! - Don't re-run auseSignalEffectfor a component that was unmounted by the same update. Preact 11 disposes it after paint, so the effect could otherwise run once more against an unmounted component.
@preact/signals-react-transform@0.8.3
Patch Changes
-
#990
1c086baThanks @JoviDeCroock! - Support Babel 8 by widening the@babel/corepeer dependency to^7.0.0 || ^8.0.0 -
#982
21b481dThanks @SisyphusZheng! - Fixtypeof processcheck in the debug logger
@preact/signals-preact-transform@0.1.2
Patch Changes
- #990
1c086baThanks @JoviDeCroock! - Support Babel 8 by widening the@babel/corepeer dependency to^7.0.0 || ^8.0.0
@preact/signals@2.11.2
Patch Changes
- #979
7526ad0Thanks @andrewiggins! - Stop component tracking before Preact reconciles the returned VNode so Signals read by DOM property getters do not subscribe the parent component.
@preact/signals@2.11.1
Patch Changes
- #973
bb9cd0aThanks @developit! - Avoid closing over VNodes in component updater callbacks.
@preact/signals@2.11.0
Minor Changes
-
#968
e83a981Thanks @marvinhagemeister! - Add support for passing functions as fallback to<For>for lazy instantiation.<For each={list} fallback={() => <p>No items</p>}> {item => <p>{item}</p>} </For>
This avoids eager evaluation of the fallback when the collection has items, which matters when you're dealing with signals.
@preact/signals-react@3.12.0
Minor Changes
-
#968
e83a981Thanks @marvinhagemeister! - Add support for passing functions as fallback to<For>for lazy instantiation.<For each={list} fallback={() => <p>No items</p>}> {item => <p>{item}</p>} </For>
This avoids eager evaluation of the fallback when the collection has items, which matters when you're dealing with signals.