Hi @8kigai
, yep, definitely a typo, thanks for pointing out.
The 2 routing systems take 2 very different approaches. There's not best one but just tradeoffs.
In my last project we had an architectural setup which made very hard to write custom server configuration to properly handle custom url parameters. They come for almost free with react-router, for example.
The codebase was also very bound to react-router's ability of rendering nested Route components instead of relying on file system routing.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi, is that a typo in the static router closing tag in // next/with-react-router.js ??
And also I am wondering what is the benefit of using react router instead of next/router?
Hi @8kigai , yep, definitely a typo, thanks for pointing out.
The 2 routing systems take 2 very different approaches. There's not best one but just tradeoffs.
In my last project we had an architectural setup which made very hard to write custom server configuration to properly handle custom url parameters. They come for almost free with
react-router, for example.The codebase was also very bound to
react-router's ability of rendering nestedRoutecomponents instead of relying on file system routing.