React Router
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
2recommend
5warn against
Nov 4, 2025first mention
Sep 5, 2026latest mention
Why people recommend it
“I’ve been delighted with the change and will probably not look back.”
switched from Next.json “We moved Railway's front end off Next.js. Builds wen…”
“is easier to understand and explain than a separate framework wrapping RR”
Caveats and dissent
“is not easy to set up and think about by any means”
“next, react-router, waku”
Show 2 more
“I won't be using react-router for future projects.”
maintains a complex custom SSR setupon “React and Remix choose different futures”
“to avoid dealing with the insanity that is react-router”
Often compared with
Threads where it came up
- React and Remix choose different futures 2 mentions
- Actively exploited sandbox RCE in all Chromium versions 1 mention
- Ask HN: Who wants to be hired? (June 2026) 1 mention
- We moved Railway's front end off Next.js. Builds went from 10 minutes to under 2 1 mention
- No-build, no-NPM, SSR-first JavaScript framework if you hate React, love HTML 1 mention
- Critical RCE Vulnerabilities in React and Next.js 1 mention
Also written as react-router. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 10
“is not easy to set up and think about by any means”
“React Router”
“I’ve been delighted with the change and will probably not look back.”
“The previous Remix was rebranded into React Router.”
“next, react-router, waku”
“is easier to understand and explain than a separate framework wrapping RR”
“I won't be using react-router for future projects.”
“to avoid dealing with the insanity that is react-router”
“this isn't useful in practice in my opinion”
“working on a document analyzing project using React Router as the full-stack framework”