Ryan Christian

Yep I'd assume it's the official docs for v1, just early and rough (as v1 still is). Contains migration guide and changes from v0.16 to v1: https://twind.style/docs/migration

Things might've changed (I haven't checked in a good few months), but in the past there was no way to feed `.astro` files, raw or their compiled HTML output, into...

Yep, makes perfect sense that it'll use more memory. I had assumed as much and have no issue with that. > You should see a difference in max used GPU...

On a quest of trial and error, I decided to cut my images down from `960x960` to `480x480` which succeeded while confirming that `pipe.enable_attention_slicing()` is in fact working. I hit...

Just to clarify, I'm happy to merge any amount of translations -- every little bit helps! We certainly don't expect you to translate everything, as that'd be a ton of...

> Could you explain possible consequences of this? The consequences are that anyone looking to fully embrace React's concurrent features will not find full support. Preact will instead promote and...

> (note also that @preact/signals-core was [published without a README](https://www.npmjs.com/package/@preact/signals-core).) This at least has already been addressed in https://github.com/preactjs/signals/pull/82, just haven't published since.

(I see this is old, but figured I'd answer some of this anyways) > It looks like `@preact/signals` is just re-exporting everything from `@preact/signals-core` - exports from two different packages,...

Indeed. But as far as I can tell they're not, at least not anymore. Might've gotten fixed at some point if you were seeing that in the past. (Let me...

None of those 3 are using signals in Preact. Those are standalone examples, so using the core lib there is correct.