redux-little-router

Some unsolicited advice from someone who has also been down a similar path. I normally suggest eschewing the javascript class model in favor of using stateless functional components.[0] I've found them simpler to understand and it cuts down on unnecessary typing. I almost never use 'this' in javascript, and instead have favored an OLOO[1] or pure functional style as it fits into a simpler mental model for how things are working. I normally only test the actions that modify state in my javascript applications. I care that I'm correctly changing the state of my application, not what that state renders. (This is similar to rails apps not typically testing html output) I normally use mocha[2] for testing and if something goes wrong I can open up a normal chrome js debugger using the --inspect-brk flag when running via the cli. You will eventu

No, it's simply that OP did not clarify with any specific problem he had with React Router. If React Router is not suiting your needs, there are many other options out there. That's the beauty of the ecosystem: https://github.com/FormidableLabs/redux-little-router https://github.com/react-community/react-navigation I'm glad that even React Router was willing to iterate on its implementation. It takes a couple of hours to do a bit of research and searching to find the solution that fits your needs best.

If you're using redux I would recommend you stay far away from react-router. Using redux-little-router has been a pleasure to use in comparison: https://github.com/FormidableLabs/redux-little-router

Hi HN, I'm comfortable with basic Javascript but I am new to the larger npm ecosystem. I have been suffering 'Javascript fatigue' working out what libraries and technologies to use. In the end I chose the React path. I found 'create-react-app' a great way to get started that initially hides much of the tooling complexity from you. [1] I found 'redux' a fantastic way to manage state. [2] But things became less clear when it came to routing. The first options I could see were: 1. Roll your own. However routing is such a common requirement I'd much rather find a library than reinvent the wheel and deal with things like cross browser issues myself. 2. Use react-router [3]. This appears to be the standard React routing solution and I was going to use this initially. But then I saw the negative reaction to react-router version 4. It seems there

If you're looking to jump ship and your projects use Redux, you might find https://github.com/FormidableLabs/redux-little-router to be a nice alternative. RRv4 still hoards URL state within a component, while Little Router just puts it in the store. This makes deriving most of your app from URL state a reality. Check out https://formidable.com/blog/2016/07/11/let-the-url-do-the-ta... for more on how we differentiate from the RR philosophy.