Jack, brilliant article. This is a very gentle introduction to pretty much that’s how right now; I had never paired React and Webpack with server side rendering and I’m surprised at how painless a very simple implementation can be.
I do have a question, though. Naturally, the routing works perfectly well on the server when hitting /about directly. When running on the client though, trying to refresh a page from /about directly triggers a route: it’s expecting the hashbang. I was under the impression that react-router took care of this magic on its own but apparently it does not! How does one go on about making sure that seamless routes between server and client are handled correctly?
Once again, thanks for the very clear, concise and well written article!
Ricardo Magalhães
Jack, brilliant article. This is a very gentle introduction to pretty much that’s how right now; I had never paired React and Webpack with server side rendering and I’m surprised at how painless a very simple implementation can be.
I do have a question, though. Naturally, the routing works perfectly well on the server when hitting /about directly. When running on the client though, trying to refresh a page from /about directly triggers a route: it’s expecting the hashbang. I was under the impression that react-router took care of this magic on its own but apparently it does not! How does one go on about making sure that seamless routes between server and client are handled correctly?
Once again, thanks for the very clear, concise and well written article!