Jason Miller

I looked into this and added a reproduction to the preact-redux issue. It's not likely to be related to `preact-router`, but rather that rendering a connected component with new props...

I think this would be a nice addition. The 'back' concept gets a bit murky when the user uses forward history navigation, since that also fires the `popstate` event. The...

Definitely worth adding yup. Technically this is a dupe of #129 - if we supported relative paths in `route()` and links, `route('?foo')` would be relative to the current route instead...

There's a PR open for the behavior if you're up for reviewing! #138 and my alternative that abuses the DOM to do it, #177.

I recall TS recently added support for specifying props for a child component, but I've lost the link. That seems like it would be relevant here, where we want to...

Hey @gnaeus - the stable sort is a really good point, since currently there is nothing defining which route gets precedence when two routes have the same length rank. It...

@patrickhulce hmm - are you importing `Link` from `preact-router/match`? I just merged a PR to correct the docs, which were erroneously stating that `{ Link } from 'preact-router'` supports `activeClassName`...

It's a way to reduce the size of the core library. I think it may be worth evaluating what the size impact would be to merge `` and `` into...

This is not supported since it doesn't work with path ranking. I'd recommend looking at another router like enroute or React Router.

Hi there - if you add unique `key` properties to the children of router, it will always unmount and mount: ```js class App extends Component { render () { return...