Watercooler ChatMay 24, 2018 at 4:44pm
A place for chit-chat :)
May 24, 2018 at 4:49pm
Me too! I think I'd be looking for a way out of development without it. Moving away from Rails to RS feels the same as moving away from PHP some years back.
Are we moving the main discussion here?
May 25, 2018 at 2:57pm
May 26, 2018 at 1:07pm
May 29, 2018 at 7:31pm
May 30, 2018 at 3:35pm
If you are referring to the dev server, that's different. React-Static is built on webpack and thus built on Node to run the dev server and build the site.
ok, am I correct in thinking that i could build the site and upload it to an aws go server, and once the first load is done the site would run like a normal react app (with aggressive preloaded routes)?
what I'm finding hard to get my head around is if your framework works the way I think it does, i can get away from SSR and have the best of both static fast website loads and then a SPA thereafter. Why wouldn't anyone do this over SSR solutions that tie you to node in production?
React-Static produces a static application, eg. one that doesn't require a server to run (other than a file server)
And you can deploy it to anywhere that serves static files (Netlify, GCS, S3, etc)
So with that, to answer your first question, when any page on the site loads, it automatically bootstraps a react application over the top of the HTML and gives you what you are referring to as a "normal react app"
From that point, you can absolutely treat it as a regular SPA
You can fetch dynamic data, do auth-only routes, build a SASS product, anything you can do with web tech