Jason Miller

@studentIvan you can already do that using a custom history, since it lets you specify your own `listen()` observer.

hey @marlun78 - are you able to PR your fix here? I'd be happy to merge.

@vpzomtrrfrt is this mounted within a ``? If so `` will perform a Router update in addition to the hashchange. If not, it will perform a full page load. I'm...

Right now `*` is just a ["splat" modifier](https://github.com/pillarjs/path-to-regexp#zero-or-more), the standalone [asterisk](https://github.com/pillarjs/path-to-regexp#asterisk) isn't supported. I'd love to add support for it though! It seems like the second `else if` there could...

One suggestion: links that don't match any routes automatically fall back to the default browser behaviour. If you want to avoid preact-router routing for a given path, you could avoid...

For sure. I've found that in the cases where I need to exempt whole paths on the same domain, I'm not usually rendering the 404's with Preact since those paths...

Ah - that's interesting. Router is definitely always overriding that property value. Interestingly, it only happens if you include `?` in the route.

Sorry for the super long delay in reviewing this @halcaponey! Just a few things I think we can address to get this merged.

Update looks good. Only thing I want to check is if this is triggering a double-render when changing the URL prop. Ideally we'd propagate the state without forcing a second...

Oh wow this is a lot of work, thanks a million. I noticed you published [preact-router-nested](https://www.npmjs.com/package/preact-router-nested) to npm - are you successfully using this PR? That helps make sure it's...