RRTR?

[BerkeleyTrue]

Why the move to RRTR from react-router? There isn't any explanation as to why and what rrtr.

[taion]

Sorry, I'll have a post up shortly.

[taion]

rrtr is my new, actively maintained fork of React Router. See https://medium.com/@taion/react-router-is-dead-long-live-rrtr-d229ca30e318.

The maintenance situation with React Router is extremely bad right now. As it stands, I don't see a way forward to get the functionality I and others need from a routing framework from React Router, as the project is currently managed.

[BerkeleyTrue]

Thanks for the explanation. Seems like a better solution would have been to fork this project and rename it instead, considering this no longer uses React Router and this project is called React-Router-Bootstrap.

I'll need to look into RRTR (What does that stand for anyways?) as there are a lot of things lacking (SSR stuff) from RR that I need. I've always chopped it up to the team behind RR being more front-end oriented.

[jquense]

RRTR is a fork of React-router so it has the same features.

[BerkeleyTrue]

@jquense It may have the same features, but those using this project currently expect it to use RR.

[taion]

rrtr is just "React Router" with a lot of vowels taken out. At the moment, it's almost just a straight fork of React Router. I made the fork so that I'll have the ability to maintain it actively going forward and start building out extra features that I'll need.

In an ideal world, maybe it will be possible to unfork the router down the road, but for now this is the only way forward that I could fine.

Would you care to drop an issue on rrtr regarding what's missing in terms of SSR support? I'd love to expand that part of the feature set if possible.

[BerkeleyTrue]

@taion Sure, and to be clear I'm not saying this is or isn't the right move.

Now that this project uses another router, albeit it is a fork it still is another router under another package name, I now need to peg my projects deps to the last version.

I cannot just move over to another router package as your packages are not the only packages I use that depend on RR. As such, moving to RRTR is not a drop in replacement, but a lot of work that would involve me forking other projects so the peer dependencies all line up.

And if I peg my dep to this project I have to deal with greenkeeper opening up a PR every time you release a new version of this package. Not a big hassle but a hassle nonetheless.

So my options are to either peg RR-bootstrap and deal with the annoyance or fork this project, revert back to the last RR version, and release my own RR-bootstrap to npm.

[taion]

Yeah, the package management is a pain. I'm really sorry about that. I felt like ultimately it'd be the best to keep these legacy projects under their current names to offer the best upgrade path (i.e. only swap out react-router).

I spent a massive chunk of this morning cutting these libraries over. It's a pain. I'm sorry.

[brendan-hurley]

@taion - Thanks for making this - I've used this a bunch of times. I was a little confused by this (it took looking through commits to find myself here!). Maybe put a little note in the readme files, with a link to your article?

[brendan-hurley]

I'd be happy to help out on rrtr if the case is that react-router is falling beind. During a 6 month project the whole underlying API changed about 2-3 times with that package - so I appreciate the move towards a more stable api.

[taion]

That's the problem, pretty much.

rrtr is going to see some API change, but the API changes will be incremental. It really doesn't make sense to completely change the API of a project that's as broadly used as React Router in big bang major releases that require app rewrites.

That's not particularly useful to anyone.

[BerkeleyTrue]

ultimately it'd be the best to keep these legacy projects under their current names to offer the best upgrade path

@taion This is a huge assumption, one that should have been an issue with a conversation instead.

So what is the solution?

[taion]

I don't know. I'm trying to do my best here.

Which libraries do you need?