Jimmy Jia

Code splitting already works. Just use `getComponent` and dynamic imports, and you'll have code splitting for your components. This is an additional optimization that can give a minor performance boost...

Yeah, there isn't really any support for relative routes right now. Essentially the issue is that it's not totally clear what things should be relative _to_. I'm not sure why...

Right, I see. If we define it as a component type, then things extending it can't nicely override `render`. Let's see what we can do – unless you want to...

Unfortunately, I can't find a way to fix this that both allows that override for `` and keeps it valid as a JSX constructor. I'll leave this open for now.

Yes, they're additive. The intent was that for the sake of understandability (and also not traversing the entire route tree every time), that it didn't make a lot of sense...

what happens if you just omit `path="/"` there? i.e. specify the `` without a path?

i suspect what doing `path="/"` there is to add a path that _requires_ the trailing slash

okay, that's totally a bug then. mind if i track it on this issue?

Not going forward with this at the moment. Will revisit if the need arises.

@jquense @eaculb