Jonathan Grimes

Which is why i conceded to your point several comments ago. We just have rollup produce a umd and an esm. Remove src as the module entry point.

If my pr addressed @brettz9 's concerns (I think it did) then you may find mine desirable since it is setup to make rollup output all your various bundle formats...

But I don't really have a preference. Not having any dependencies on babel or core-js would be my only real desire.

See commit: 3df703d01 The standalone build was removed a little over a year ago.

contextual router is mounted under the `/:streamId(/*)` route. The contextual part matches against the remainder bit: `(/*)` Have you tried not starting your link with `/#{@state.steamId}/` instead just do `#{route.path}`?

The history api is used by default as you follow links. Just make links as you normally would (or use the `Link` component) to pages, and setup a `` wrapper...

Redirects are supposed to replace the current entry of history, if you redirect from a route, you aren't supposed to be able to go back... If you are forwarding someone...

Nonetheless, you don't need to directly access or use the history api with this component... it handles it for you.

You are using Links primarily to navigate, right? You shouldn't need to programmatically navigate 99% of the time. Using Redirect to navigate your app in this fashion is fine, I...

@STRML the `{isPopState: true}` should prevent the odd behaviour you were talking about... setPath() short circuits if `isPopState` is true so that it does not re-push the path to history....