Wait that barrier? You don't have access to the window object and stuff like local storage on server and you cant access filesystem in browser. Which is both wuite obvious.
What else am I missing?,
Discussion
It's not a barrier, per se. I simply realized after working with it for a little that all the server is doing is creating a container and links to the JS, not rendering the page, and finding when it switched SSR to CSR wasn't immediately apparent.
Now I know that the default React SSR is super basic and doesn't contain any real content. Now I have another avenue to explore.
https://void.cat/d/Ag5kH4Rd8633AMjEwpL7sR.webp
(I didn't realize at first this only ran on the client. I thought this was server-side)
That's not a server side js issue. That's a React issue.
NodeJs on backend works perfectly fine and predictably.
With React things get a little confusing mainly because there is a huge ecosystem around react and everything can be another thing in different setups. (Like React Native vs NextJs vs React with Electron etc)
Once again tho, that is a react specific issue.
Oh! Interesting. Similar in Angular, Vue and other JS stacks or just React?
React specifically has the largest, most confusing and most diverse ecosystem. It's not entirely unique, but due to it's ecosystem's size it has some problems that are unique among it's peers. And even without the size. just like every other framework (no, it's not a library despite claiming to be one) it has unique problems stemming from the nature of how it's designed and/or implemented