Fixed computed.peek to get the latest value

[theJian]

computed.peek is not returning the latest value.

const counter = signal(0);
const doubleCounter = computed(() => counter.value * 2)

console.log(doubleCounter.peek()) // print undefined, computed callback was not executed due to laziness.
console.log(doubleCounter.value) // print 0

counter.value = 2
console.log(doubleCounter.peek()) // print 0, again, a stale value from last update is returned due to laziness.

this can be fixed by refreshing the internal signal's value before peek() into it.

[WebReflection]

beside the need to update Node version to 22 or 24 ... this feels like a peek() with side-effects ... are we sure that's desired?

anyway, I need CI green or I am afraid I can't merge this ... please change Node version and change checkouts to v4 within this MR, thank you!

[theJian]

this feels like a peek() with side-effects ... are we sure that's desired?

if you mean a peek() can trigger an immediate evaluation, I tried @preact/signals-core and it does the same.
That feels natural to me since peek() is essentially trying to access the value, do you think of other scenarios.

[WebReflection]

dunno ... these days I am more keen to use something like this instead https://github.com/WebReflection/alien-signals#readme so if you think that's expected/desired and both alien-signals and preact signals work the same ... works for me.

[coveralls]

Pull Request Test Coverage Report for Build 15044707032

Details

• 20 of 20 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 11435340504:	0.0%
Covered Lines:	342
Relevant Lines:	342

---

💛 - Coveralls

[theJian]

Yes, I tried that too, and it does the same.