Jason Miller

Ahh - you might be interested in the more advanced server renderer I've been pondering: ```js let renderer = createRenderer(); renderer.render( ... ); // later (async) after you get that...

@BerndWessels I've created a JSFiddle demo showing what I described. It's a little less obvious what's going on since it's in a browser context, but this is a server-side renderer...

~~I'd really like to get some benchmarks going for it~~, but I'd actually think it might be slightly faster. `createRenderer()` is just in that fiddle - it's not really much...

Here's what I used: https://gist.github.com/developit/6e117d53f4f32b8f1e63bb43f5f6e937

Hi there - use the gist one, it's faster. I was only using hits to track className so instead I changed it to do that explicitly. The gist is the...

@BerndWessels wow, that is an amazingly complete example. Nice work, I am probably going to steal some of the ideas haha

@Stanback good call! I'd actually recommend one slight change there - instead of just removing the element, un-render it via preact so everything gets nicely disconnected: ```js tearDown: () =>...

@Stanback Makes sense - I figured you had modified it to more closely match the output of `preact-render-to-string`, which seems like a good idea. It will be good to codify...

yikes! We'll need to link to codesandbox/jsfiddle/codepen instead.

(note for myself: prerendering needs to be updated to account for `cli` not having a dropdown in config.json)