Matthieu Riegler

The aio tests are flaky, I'll try a rebase.

I not against some help yes. I'm wondering if the issue is maybe related to #50537.

You have the typing the other way around : ` input(false, { transform: booleanAttribute });`

I'll close this as "fixed" by using the Signal inputs which don't suffer the same limitations as decorator inputs !

@jwittekind Could you provide a working repro on a github repo ? This basic example without its context doesn't seem to reproduce the issue.

It's not the websocket per se that is a fault here but the socket IO lib. A open standard Websocket does not prevent the app from becoming stable.

The issue will occur everytime a macrotask is run while initializing the app. For example if the library you're using is calling `setInterval`. I have a draft explanation at #50295...

Shouldn't the `developerPreview` part be a improvement on the doc-infra side ? I think `developerPreview` should be inferred if one of the overloads have it.

Hi, It's not an error but a warning message introduced by #48253 which got shipped in v16. (and later reformatted in #49986).

@alexaka1 What about using the 2nd solution proposed in the error page ?