universal-router VS wouter

I use it like that and I am pretty happy with it.

There's one thing, you should redirect all the pages to one single endpoint in server side order to use "pushState". Otherwise it will return 404 when you hit the refresh button. If you don't own a server, you can support routing with hashtag "#" and listen to "onhashchange" event instead of "popstate".

Also, if you would like to support nested and dynamic routes (it's not possible with that code snippet in the github repository since it just checks like `path===currentPath`), you might look at the following solution:

https://github.com/fatih-erikli/universal-router/blob/main/u...

I use that solution in server-side and client-side so it works like Nextjs.

We're using wouter with great success. It's simple and effective for what we need from a router

If you feel like React Router is a bit too over-engineered and you just need simple routing, you can have a look at https://github.com/molefrog/wouter

I changed over to using wouter instead of react-router, and I love it!

Just to add alternatives. I'm a fan of Wouter its 1/10th in size compared with react-router.

Other options than react-router are also available, like wouter, if you can't use react-router for some specific reason.

Single page just means one index.html is served and then JavaScript takes over to display content. You can use a client side router to simulate pages. There are some to choose from, I can recommend wouter. https://github.com/molefrog/wouter

Routing: At this point you should understand how routing in React works. You can use react-router to enhance it. There is a small library called wouter which you might want to have a look at.