Using signal doesn't let the state change at the parent component level

[murtuzasyed]

• Check if updating to the latest Preact version resolves the issue

Describe the bug
I have a simple Component(TestComponent.jsx) that has a single state 'loading' that changes after an async action. If I have a signal in a child component, the loading state change doesn't trigger a new render.

To Reproduce
Issue can be reproduced here https://stackblitz.com/edit/create-preact-starter-dbmgvvks?file=src%2FTestChild.jsx

Steps to reproduce the behavior:

1. Go to the link
2. The UI gets stuck at Loading...

Expected behavior
The Loading... text gets replaced with the contents of the chid component TestChild. If I remove the below line from TestChild component it works fine.

import { signal, computed } from '@preact/signals'

[murtuzasyed]

Seems like it doesn't import { signal, computed } from '@preact/signals' but works with signal-core
import { signal, computed } from '@preact/signals-core'

[marvinhagemeister]

I can reproduce it with the stackblitz workspace. But when I update the Preact from 10.17.1 to the latest version 10.26.5 it works as expected. Can you try upgrading Preact?

[rschristian]

Someone mentioned a similar thing here: #4746

Our peer deps might need a bump in @preact/signals perhaps?

[murtuzasyed]

@marvinhagemeister yes, using the latest version fixes the issue but wondering with 10.17.x if there's a appropriate version of @preact/signals to use to fix this issue

[JoviDeCroock]

There's essentially a lot of explanation around the decisions etc in preactjs/signals#630 and #4560. The long and short of it is that I pushed a bug back in 10.16 which had gone unnoticed for a while, it was very finnicky when combining state and hooks. There are versions where this works as outlined in preactjs/signals#630 and if not, I can look into that.

The TLDR is that this got fixed in the 10.25.0 release line, but this is also not a Preact issue it's at this weird intersection of multiple state solutions 😅