[fatih-erikli]

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.

[chrismorgan]

Please don’t encourage using a single route and the hash; people should just ensure that suitable document is served from all routable URLs—whether it be a consistent bootstrap file, or (generally preferably) that you do server-side rendering. Using the fragment for routing is only something to do when you can’t do it the proper way, not a tool to reach for from the start.

[ReactNative22]

> 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".

Could you explain this one a bit more / maybe some example code I could borrow from? :)

[math-dev]

Interesting - thanks for the tip!

[ReactNative22]

Thanks for this!