I haven't tried the code in the repository but form skimming it a bit it seems to have the same issue I had when I tried this approach - what should I do while

I haven't tried the code in the repository but form skimming it a bit it seems to have the same issue I had when I tried this approach - what should I do while developing? What I mean is that this works, but in production.. I couldn't get this to behave properly due to FS caches of files it puts through the pipeline to finally stream it to the client. So am I supposed to be using the usual React server thing to write code and use this in production? in this case, I can't account for run-time SSR issues that only come up when using this SSR approach.. so I can't trust my releases without "rendering" all the UI to see there are no issues. What I personally ended-up doing is build-time (Jenkins) generation of all public facing pages and saving corresponding HTMLs, React-hydrating these on load.. and a normal skeleton `index.html` with normal React.render for the actual app pages which are behind login.. This of-course is not relevant if you have dynamic public pages you want to serve but that's a different use case than mine.