You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we are just returning raw HTML from the server. We can use server-side rendering instead, so the server will actually be calling into the client. This has pretty heavy implications, and is where a Next-like design will need to come into play.
We need document, head, and body components
We need the ability to fork client vs server logic in our components (akin to getInitialProps()). Next prefers a fully isomorphic setup, but we want to be able to see a clear separation between what code is running on the client vs the server.
Combining the above two points together, we need to do what Next does to bootstrap a React component tree into a React rendered document. This will be complicated (and fun).
The text was updated successfully, but these errors were encountered:
Right now we are just returning raw HTML from the server. We can use server-side rendering instead, so the server will actually be calling into the client. This has pretty heavy implications, and is where a Next-like design will need to come into play.
The text was updated successfully, but these errors were encountered: