2023-03-17
2474
#react
Peter Ekene Eze
3599
Mar 17, 2023 â‹… 8 min read

How React Hooks can replace React Router

Peter Ekene Eze Learn, Apply, Share

Recent posts:

How To Build Cross-Platform Mobile Applications Using Lynx.js

How to build cross-platform mobile applications using Lynx.js

Use Lynx.js to build cross-platform web and mobile apps, addressing layout, navigation, and performance challenges for consistent UX.

Andrew Baisden
Apr 15, 2025 â‹… 16 min read
PDF report workflow

Struggling with your PDF report workflow? Try this

Streamline your PDF report workflow using React and .NET. Walk through a real-world example and discover cloud-based alternatives.

Andrew Evans
Apr 14, 2025 â‹… 8 min read
a guide to the MUI Grid system

A guide to the MUI grid system

Explore the MUI Grid system in depth, including updates from MUI v5, and learn how to build responsive grid layouts.

Gaurav Singhal
Apr 11, 2025 â‹… 8 min read
Building Progressive Web Apps (PWAs) Using Rust

Building progressive web apps using Rust

Build a progressive web app using Rust, WebAssembly, SurrealDB, and Nostr with local encryption and fast storage.

Mario Zupan
Apr 11, 2025 â‹… 18 min read
View all posts

8 Replies to "How React Hooks can replace React Router"

  1. In your first hooks routing code sample, the o e for routes.js, you forgot to reference each individual component. You import them but they’re not in each of the functions for that Routes object. So the 3 functions return nothing.

  2. How would you setup your hooks router to support modal side panels (which slides out when url starts from /modal/.. for example)? It this possible to describe multiple switches (one will return previous url component, and another one will return modal url component) within one rules object? Is this possible to forcibly pass desired url to router like <Switch location={previousUrl}?

  3. This was a very helpful article thank you. I have encountered one issue with this though. My hook components keep getting called. using a components in a menu placing a break point in the export default function PaymentSettings(props) for example – will result in that breakpoint getting it continuously.

  4. This is cleaner compared to Routes usage for sure. However an issue that keeps coming up in larger applications is the number of components imported for a “routes” file, as it needs each component to render for every path defined. So the more routes you have the more components need importing, I’ve seen 1000’s of lines before with no options outside creating smaller modules or a key based component directory. It would be nice to see this tackled in some other way, if you have any ideas how hooks might help here that would be great?

    Thanks
    JB

  5. Very nice post.
    But I will stay on react-router because I’m using typescript.
    the documentation page states that future releases of hookrouter will not necessarily update the types/hookrouter module

Leave a Reply