Sign in to join this conversation, and others like it, in the communities you care about.
A fast, lightweight, and powerful framework for building static-progressive React applications and websites.
How to refresh route data?
`basePath` doesn't seem to work properly
can someone check my understanding of gatsby, react-static, netlify, netlify cms, and contentful?
[SOLVED] How do you use PostCSS plugins?
Noob question about embedding script tags from other sites
React Static / General
Are we moving the main discussion here?
At least for now.
We need to give spectrum a good college try!
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.
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