jdelafon
commented
7 years ago The author wrote a page on the subject: "You might not need React-router" that you may find interesting. There are good arguments there.
Some arguments against a home-made router however are that
- You have this hard-coded in your app instead of the modularity of an npm module, although you really don't care about what is in router.js;
- You lose the support and experience from react-router's large users base, and rely entirely on this GitHub page when you have issues.
- You multiply things that should definitely be unique. Nobody wants alternatives if one works perfectly well and the user sees no difference.
- If you find stupid that JSX is used for something not related to UI rendering, you can use react-router without JSX (it just looks worse).
The biggest problem I have had is that I could not make it work with HMR (although it is part of this project). See #166.
Hi there, this project implemented its own routing solution and increased the learning curve to some extent. I was wondering if there is any specific reason React Router is not used in this project? Thanks!