Jason Miller

Hi @redimongo - since routing is synchronous, you can't do a DB lookup to determine if something is a match. Instead, I would recommend rendering your 404 page once that...

Unlike react-router, this router doesn't work outside the confines of Virtual DOM - if you want to render a match for a route you need to render a router with...

I like the idea, will reivew.

This was intentionally left out of the library by default, because it's hard determine when it would be appropriate to scroll to the top of the page (eg: should we...

@bgradin just to clarify - are you doing ``? or did you mean ``?

This is how preact worked in previous versions, but there are too many issues arising from caching DOM - most importantly, it's quite bad for memory management (images & videos...

Hmm interesting. I've never used this with prototypal inheritance, I can see how it'd overwrite itself like that. Not sure what the best solution for this would be, seems like...

Agreed! It's a difficult thing to change now that its there, but what about adding an option and making the default an actual debounce? @pl12133 called this out to me...

Oh nice, I hadn't seen that module! Looks good.

The default values are specified after the colon in the readme: `delay: 0` or `cache: {}`. This could certainly be clearer, though. Good point about actual usage though, that is...