-
The "Local state with signals" section covers only `useSignal` and `useComputed` - it doesn't cover effects triggered by local signals.
Can we use normal `useEffect` for that?
Would you specify …
-
**Describe the bug**
When using the `on:event` syntax on HTML elements in JSX in TypeScript the props are considered invalid:
```typescript
null} />
```
```
(JSX attribute) on:click: () => …
-
Tried something like this:
```
import type { ReadonlySignal } from '@preact/signals';
import type { JSX } from 'preact';
type HandProps = {
length: number;
limit?: number;
stationary?: …
-
Hi, I'm playing around with Preact Signals and have a question about an interesting behavior I noticed.
The behavior is a difference between `signal` and `computed`.
Effects that observe `signal…
-
Any one use unocss with next.js 13?
-
Not sure if this is relevant for µsignal, please close if not.
@preact/signals output:
```shell
Activating: red
Red is off
Red is on
Activating: green
Green is on
Green is off
Activating:…
-
A lot of big updates came to Tailwind 3.x that added a lot of advanced styling options. Any plans in place to add 3.x support to twind?
-
**Describe the feature you'd love to see**
I'd like to have some ways to pass reactive values to Preact, for example instead of passing it a string as a child I'd like to pass it something like thi…
-
## Background
When a user writes a module specifier (the string literal after `from` in an import declaration) in a TypeScript file, how should the compiler resolve that string to a file on disk to b…
-
Getting an error in devtools where `currentComponent` is `undefined` inside `useComputed`. The error occurs here:
https://github.com/preactjs/signals/blob/6eeeda7fed08dfa53e8bbb4e563e2a32e4f220f5/p…