Suspense!

[jaredpalmer]

Opening up discussion for what Suspense-based API will look like.

[krazyjakee]

@jaredpalmer at a high level, how do you envisage this affecting afterjs? What could be the benefits or problems?

Here is an article on suspense and SSR: https://blogg.svt.se/svti/react-suspense-server-rendering/

[jaredpalmer]

single pass rendering.

[jaredpalmer]

no need for after.js lol

[jaredpalmer]

but seriously, there will still need to be some way to hydrate even with streaming. so after.js would handle that if React pushes some of that to user land. it's hard to say.

[stale]

Hola! So here's the deal, between open source and my day job and life and what not, I have a lot to manage, so I use a GitHub bot to automate a few things here and there. This particular GitHub bot is going to mark this as stale because it has not had recent activity for a while. It will be closed if no further activity occurs in a few days. Do not take this personally--seriously--this is a completely automated action. If this is a mistake, just make a comment, DM me, send a carrier pidgeon, or a smoke signal.

[krazyjakee]

"fizz" updates have been made to react enabling enable a better path for sssr facebook/react#14144

[renatorroliveira]

Man, so many things happening, hard to follow hahaha

So, I am just researching a better way to migrate an application on React 16 + React Router 4 + Redux Sagas to a SSR solution. I was almost decided to go with After since Next.js is "too opinionated" for my taste and Electrode seems "too complicated" (I think of it like a war machine for my simples SSR for SEO needs... maybe I am mistaken, but the bootstrapped app seems already too complicated).

Should I wait or try using alpha versions of React 17? I am divided right know between After and try React 17 by hand. @jaredpalmer It would be too hard to migrate an After based SSR app to the new approach introduced by React 17?

[krazyjakee]

@renatorroliveira check my comment here #133 (comment)

As I see it essentially removes the need for getInitialProps which both next and Afterjs use.

I'm very sure it will be simple to move logic out of getInitialProps and into a function called by suspense. Both return props so I'm confident it would be simple.

[jaredpalmer]

It's hard to say for sure, but yes we could do what @krazyjakee described. However, the entire premise of getInitialProps would be theoretically void when SSR suspense arrives because you no longer would be forced to inject data top-down.

[krazyjakee]

@jaredpalmer unrelated question. In a post-getInitialProps world, where would a component receive the afterjs context to, for example, set the response status code?

Edit: Related tweet https://twitter.com/jaredpalmer/status/1090261003655409664?s=19

[stale]

Hola! So here's the deal, between open source and my day job and life and what not, I have a lot to manage, so I use a GitHub bot to automate a few things here and there. This particular GitHub bot is going to mark this as stale because it has not had recent activity for a while. It will be closed if no further activity occurs in a few days. Do not take this personally--seriously--this is a completely automated action. If this is a mistake, just make a comment, DM me, send a carrier pidgeon, or a smoke signal.

[krazyjakee]

Nooooo don't you dare. Palmdawg needs this issue.

[stale]

Hola! So here's the deal, between open source and my day job and life and what not, I have a lot to manage, so I use a GitHub bot to automate a few things here and there. This particular GitHub bot is going to mark this as stale because it has not had recent activity for a while. It will be closed if no further activity occurs in a few days. Do not take this personally--seriously--this is a completely automated action. If this is a mistake, just make a comment, DM me, send a carrier pidgeon, or a smoke signal.

[stale]

Closed due to inactivity. Holler if this is a mistake, and we'll re-open it.

[Ricki-BumbleDev]

Just found react-lightyear, which exposes a renderToStringAsync function and threw it together with fetch-suspense, which exposes a useFetch hook supporting Suspense. And it actually works! (Only thing I had to do is to tweak fetch-suspense to use isomorphic-fetch)

[krazyjakee]

@Ricki-BumbleDev got a minimal project we can look at?

[Ricki-BumbleDev]

Here you go: https://github.com/Ricki-BumbleDev/react-fetch-suspense-ssr-demo

[Ephem]

@Ricki-BumbleDev Glad you found it useful! 😄

@krazyjakee There are also a couple of examples in the repo itself, for using with Redux, Apollo (using the unofficial react-apollo-hooks) or urql.

Checking out After.js has been on my list for a while but I haven't gotten around to it. After finding this issue I skimmed the Custom/Async Rendering-part of the documentation and there should be no problem just switching out the renderToString from React to renderToStringAsync from react-lightyear instead and everything should just work!

Whether it actually makes sense to use After.js for this instead of just using Razzle directly (which I do in the examples) I couldn't say. 😄