Signals proxy

[dy]

This changes store to comprise signals, rather than own pubsub.
Also streamlines / cleans code & fixes some non-obvious bugs.
Fixes #9 and addresses #8.

[dy]

@aelbore this PR introduces signals-proxy store. It seems to be a bit less efficient than either just signals or proxy store in terms of performance (negligibly though). Also it adds some extra 2kb, since @preact/signals-core is included. But it is more resilient and supports signals as values.
I wonder what's the way you're anticipating to connect your store to sprae - I'd give it a try before merging to make sure new release is meaningful. Otherwise I'd keep just proxy-based store, since it's minimal, self-isolated and most efficient. You can connect any signals to sprae as

let state = sprae(element, {greeting: 'Huh?'})
let s1 = signal('Hello')
fx(() => state.greeting = s1)

[aelbore]

@aelbore this PR introduces signals-proxy store. It seems to be a bit less efficient than either just signals or proxy store in terms of performance (negligibly though). Also it adds some extra 2kb, since @preact/signals-core is included. But it is more resilient and supports signals as values. I wonder what's the way you're anticipating to connect your store to sprae - I'd give it a try before merging to make sure new release is meaningful. Otherwise I'd keep just proxy-based store, since it's minimal, self-isolated and most efficient. You can connect any signals to sprae as

let state = sprae(element, {greeting: 'Huh?'})
let s1 = signal('Hello')
fx(() => state.greeting = s1)

Hey thanks for this, but actually I just want to reuse my signal store so that I don't want to rewrite it again, logics in the it a bit a lot so no time to rewrite it

if this compromise your library and no performance benefits, I can just Create small adapter or utility to bridge my existing store to state of sprae.

I understand correctly fx is an effect of sprae state?