Valerii Smirnov comments

Results 249 comments of


                                            Valerii Smirnov

`@preact/[email protected]` doesn't tracking signals with forward refs

Should I provide PR?

Cannot set property createElement of [object Module] which has only a getter

This is a problem related with monkeypatching from `@preact/signals-react` versions 1.x.x. Now you can use babel plugin (but not all feature of next.js working with it). Alternatively - you can...

Computed signal with async callback

I've implemented a resource and tested it: https://www.npmjs.com/package/@preact-signals/utils

Computed signal with async callback

@MicahZoltu There is no reactivity system that handles this case, because of design of js. Main solution is to use `resource` like api and pass all deps explicitly: https://docs.solidjs.com/references/api-reference/basic-reactivity/createResource I've...

Computed signal with async callback

You need to write your own wrapper around generators which will start tracking after some promise resolves

Computed signal with async callback

Write it with resource in this way ```ts const [resource, { refetch }] = createResource({ source: () => ({ mySignal: mySignal.value }), fetcher: async ({ mySignal }) => { const...

Computed signal with async callback

I don't think this case should be handled. You have primitives for this case, if you want - you can write your own wrapper around generators, but I don't think...

Computed signal with async callback

> I'm starting a new React.js project, and was looking at replacing react's useEffect, etc. with Singals. But it seems when l populate the signal with the result of an...

Computed signal with async callback

> Can I use > > ```javascript > import { useResource } from "@preact-signals/utils/hooks"; // this import > > ... > const App = () => { > const [layoutResource,...

Computed signal with async callback

Ofc. There are `createResource` function