preactjs / preactjs/preact-render-to-string
Improve async handling
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 726
- Forks
- 101
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 6
Description
Hi
It would be good to have an interface like this:
render(
<Provider store={store}>
<Root/>
</Provider>
).then(({html, context, state}) => { /* all done, serve to client now */ }
So the render promise will only resolve once everything has been rendered and all async actions have been finished. This would make it easier to get the redux state too and you wouldn't have to get the redux state artificially before calling render (plus artificially figuring out the route n stuff - all the things that make the server side different from the client side).
Basically run the complete application server side until its stabilized and ready to render.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the render entry point and trace how server-side rendering currently handles asynchronous actions and Redux state. Define the stabilization boundary and the returned html, context, and state values described in the issue; done means the render promise resolves only after the complete application is ready to serve.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100