When looking for SSR solutions, I noticed the market forced me to abandon my way of doing routing, which meant I couldn't benefit from all the APIs that I get for free with my router.
....
I had to think about my existing projects, which had gained a certain level of complexity, and re-structure everything to fit in either Next's way of doing routing, or Gatsby's way of using templates for static content.
Yep, there is a little difference between Client Side and Server Side, especially in terms of routing and pre-loading data for the route.
That's not a big deal if your data-fetching layer (GraphQL) support it (via double rendering), and not a big deal if your routing is flat, and you can match route before rendering and do some job to get data you need... But react-router will not work out of the box, and razzle cannot change this moment - it is just wrapping your App with StaticRouter which makes it work, but not making it SSR - compatible.
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.
Yep, there is a little difference between Client Side and Server Side, especially in terms of routing and pre-loading data for the route.
That's not a big deal if your data-fetching layer (GraphQL) support it (via double rendering), and not a big deal if your routing is flat, and you can
matchroute before rendering and do some job to get data you need... But react-router will not work out of the box, and razzle cannot change this moment - it is just wrapping yourAppwithStaticRouterwhich makes it work, but not making it SSR - compatible.