-
- [x] I have searched issues for similar feature requests
## What is this feature about (1 sentence)
Consider renaming project to avoid conflict with Cypress
## Why is it needed? What is the va…
-
Not works:
```
function changeUsername(event) {
alert('Stupid Boy');
};
...
Log in
```
Works:
```
Log in
```
-
Consider the following code
```
import { signal, effect } from '@preact/signals'
let a = signal(0)
let b = signal(1)
let common = signal(0)
effect(() => {console.log('- a from c'…
-
### Which @angular/* package(s) are relevant/related to the feature request?
core
### Description
Allow specifying dependencies without the need to call them inside the effect. That is needed…
-
Consider the following code:
```
import { effect } from '@preact/signals-core'
import { deepSignal } from 'deepsignal'
let hugo = deepSignal({
list:[1,2,3]
})
effect(() => {…
-
I found that the signal public interface (`SignalLike`) is not actually used at runtime, but only for types. Under the hood, `@preact/signals` patches the runtime and does all the subscription and inv…
-
Consider the following code:
```
import { deepSignal } from 'https://unpkg.com/deepsignal@1.3.6/dist/deepsignal.module.js'
class TestClass {
_Prop = 0
get Prop () { return this…
-
```tsx
import { signal } from "@preact/signals-react";
const count = signal(0);
function App(){
return {
count.value = count.value + 1;
}}
>
count…
-
The web UI has plenty of deficiencies: poor error handling, no scrub bar (#32), no live view (#59), no support for the "signals" schema (#28) or any kind of analytics, no configuration (#35), not very…
-
When using with preact@10.16.0, I get the following TypeError:
```sh
Argument of type 'string | SignalLike | undefined' is not assignable to parameter of type 'Argument'.
Type 'SignalLike' is not…