rrtr is dead. Long live my fork of rrtr.
I apologize in advance to everyone for whom this will be really annoying. But this will be better in the long run, I promise. Certainly better for me — maybe even better for you also.
I am now maintaining a fork of the old rrtr as https://github.com/halhenke/rrtr
(When I say “maintaining” I suppose I actually mean “hosting”…sort of…Github is hosting I guess. My name is in the link anyway.)
The problem is that there are probably some problems with rrtr. I’m not sure — I’ve never really used it. But it certainly seems possible.
I’ve never really contributed to it either — as you can see here:
What’s coming next?
- Not much.
- A stable API. Seriously. I cannot overestimate how unlikely you are to see changes in this API. Or any of the code.
- Possibly another fork of this fork if I run into some of the same problems that began to plague the original fork (hereby designated “Fork Zero” for purposes of clarity).
- I’ll be working hard to unpublish both the original React Router and the old rrtr packages from npm. Recent changes have made this more difficult but I am currently in negotiations with the npm team to make a special exception in this case.
And if you’d like to help create another fork of rrtr (either original or improved version), please drop me a line and I’ll be happy to talk you through the process!