When you develop a Single Page Application, you have to use a Router. It's a common use case, yet every single framework has its own router, React even has multiple ones you can choose from. And even though each framework is different and every router takes a different approach, they all share the same principles. Understanding those helps us handle routing in our SPA because behind all those simple, different APIs provided by framework specific routers, a more complex architecture is hidden from us.
Let's talk about the different types of routers out there and what makes them different and understand if you really need a router for every front end framework by using Vue Router implementation as an example
YOU MAY ALSO LIKE:
- WebAssembly Deep Dive with Brian Sletten (in London on 21st - 22nd November 2019)
- Free Code Camp - October (in London on 29th October 2019)
- Keynote by Ruben Bridgewater on Performance Optimisations and the Possible Savings Doing So (in London on 30th October 2019)
- Why We Choose React for a Large Scale Financial Trading Platform (SkillsCast recorded in October 2019)
Modern Front End Routing
Eduardo is a Freelance in Front End development who loves Open source. He has been contributing to Open source since he started crafting applications. He mostly maintains Vue.js related projects as Vue itself, vue-router and vuefire but he sometimes helps out somewhere else, to make the web move forward.