News for hackers. Stuff that matters.
Re:React Router v4 FAQ by meira on Thursday September 15, 2016 @11:49PM (#12511691)
Great! I removed React router from a project yesterday, now it seems an even better decision.

Edit: I didn't have any big issue with React router and don't dislike it. It just don't work well with clojurescript/rum. I'm now using a cljs lib called 'bidi' for bidirecional routing (data only) and a small logic to change content reactively based on selected route.

Re:React Router v4 FAQ by tptacek on Thursday September 15, 2016 @11:55PM (#12511719)
Same! react-router is the only thing I've dealt with in this ecosystem that I truly, viscerally disliked.
Re:React Router v4 FAQ by marshallford on Thursday September 15, 2016 @11:55PM (#12511718)
I'm curious, did you replace react-router with something else or are you managing the url "manually"?
Re:React Router v4 FAQ by meira on Friday September 16, 2016 @12:21AM (#12511792)
With a tiny cljs lib (bidi) and some 10 lines of code to change content reactively
Re:React Router v4 FAQ by kbeckmann on Thursday September 15, 2016 @11:56PM (#12511722)
What are you using instead, can you recommend a nice alternative?
Re:React Router v4 FAQ by wesleytodd on Friday September 16, 2016 @08:55AM (#12513635)
My team uses this: https://github.com/wesleytodd/nighthawk

Basically it is just the Express router wrapped with logic from Page.js for catching link clicks and what not.

We do universal rendering with a simple middleware and share all our middleware, rendering and route definitions on both the FE and BE.