usignal v0.7.0 - Githubissues

Breaking Changes

effect signature has changed into effect(fn[, value[, options]]) and unless you were using sync or async export this will break previous code/examples. The signature is now aligned with solid-js createEffect one, plus an optional options argument to define the async behavior, still false by default.

signal signature now accepts an optional options argument like it is for solid-js createSignal utility. It is now possible to define the equals field as true (default), false (always signal updates), or (prev, next) => boolean callback to allow edge cases or deeper comparisons among "states".
computed signature now accepts also an optional initial value to pass along during the first time the computed gets executed, updated automatically as the previous value, whenever accessed later on while computing. It also accepts an optional options argument to replicate solid-js createMemo utility.
effect signature now accept an optional initial value like computed, plus an optional options object which, currently, only supports the {async: ...} field.