Jason Miller

Hmm - I don't think the plugin interoperability would be an issue here, since devolution would be running at the last stage of compilation long after everything has been converted...

Alright. I will keep you posted.

@alan-agius4 I think the "body" mode could work - it injects styles at the `` location, then adds the `` just before ``.

@alan-agius4 another option would be to have the JS bundle itself flip those preloads to stylesheets (as a backup). It could scan for the preload/disabled `` elements, add an `onload`...

I've been using this: ```js let hasInteracted, toast; function setHasInteracted() { hasInteracted = true } ['popstate','click','touchstart'].forEach(e => { addEventListener(e, setHasInteracted, { passive: true }); }) navigator.serviceWorker.register('/sw.js').then(reg => { reg.onupdatefound =...

I have a demo of this somewhere, I'll dig it up. Using it in WMR requires a bit of tweaking because it needs to use Module Workers directly in development...

2kb 2kb 2kb

@rauschma The main things we have explored related to that are actually implemented using Preact X as it exists today, so I'd put them on an independent timeline from a...

It's really unlikely that we'd ship hooks in core, much more likely that we will move Component out of core. Subpackages are going to become commonplace over the next couple...

30b is compelling, but I'm waffling on this for some reason. I liked the separation we were getting with createRoot. That said, our createRoot was already different from React's in...