Cagdas Ucar

@JoviDeCroock Thank you for reviewing the PR and your feedback. Partial hydration is certainly an interesting solution but it does not address my problems, primarily because I know that there...

@JoviDeCroock I added another change that should fix the build errors. I disabled async/generator transforms. I'm using generator functions dynamically everywhere for microbundle/rollup to not get confused. Build is working...

@JoviDeCroock I verified that the reason for the bundle size blow up is indeed the async function transformations. Even though I disabled them in babel options, microbundle/rollup is still transpiling...

@JoviDeCroock Here's the new structure with async as a separate bundle. I added a couple of API integration points using option hooks. These are used to override the queue processing...

Here's typical usage: `import { render, renderAsync, h } from 'preact/async'; const mainComponent = h(App, {}); const renderArgs = [ mainComponent, document.getElementById('root'), document.getElementById('root').firstElementChild ]; if (asyncRendering) await renderAsync(...renderArgs); else render(...renderArgs);`

@JoviDeCroock if you would like to be able to test it easier, I published the fork to npm so that I can use it in production. Here's sample usage: Install...

@JoviDeCroock @developit here's an article I wrote about this: https://dev.to/cagdas_ucar/preact-async-rendering-51p2

@amalitsky Thank you. preact async rendering is exactly what's supposed to help with that. I've been using it in production with great success. Blocking time is usually 0. Try https://www.npmjs.com/package/preact-async...

I have the same problem as the first part of this ticket (duplicate CSS). It is causing styling problems due to duplicates ordering. @evanw please help! I feel like the...

I found another solution to this problem. I'm doing what webpack did, which is loading the CSS as string inside the JS. Here's my build file. Note that this markdown...