react-async
node-fibers
react-async | node-fibers | |
---|---|---|
1 | 3 | |
445 | 3,559 | |
- | - | |
0.0 | 0.0 | |
over 7 years ago | 7 days ago | |
JavaScript | C++ | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
react-async
-
Strategies for server-side rendering of asynchronously initialized React.js components
React-async. This approach is perfect. It lets me simply define in a special function in each component how to initialize the state (doesn't matter whether synchronously or asynchronously) and these functions are called as the hierarchy is being rendered to HTML. It works in a way that a component is not rendered until the state is completely initialized. The problem is that it requires Fibers which is, as far as I understand, a Node.js extension that alters the standard JavaScript behavior. Although I really like the result, it still seems to me that instead of finding a solution we changed the rules of the game. And I think we shouldn't be forced to do that to use this core feature of React.js. I'm also not sure about the general support of this solution. Is it possible to use Fiber on standard Node.js web hosting?
node-fibers
-
Kinds of Reactive Fibers
It would be cool for the Fiber Proposal to be adopted into the standard, but it's been at stage -1 for several years now. So it's not what they don’t implement it, but on the contrary, even the extension for NodeJS node-fibers was recently completely broken.
-
How to wrap async function calls into a sync function in Node.js or Javascript?
Asynchronous function using callback/promise is the DNA of JavasSript and Node.js. Any non-trivial JS app is probably permeated with this coding style. But this practice can easily lead to so called callback pyramid of doom. Even worse, if any code in any caller in the call chain depends on the result of the async function, those code has to be wrapped in callback function as well, imposing a coding style constraint on caller. From time to time I find the need to encapsulate an async function (often provided in a 3rd party library) into a sync function in order to avoid massive global re-factoring. Searching for a solution on this subject usually ended up with Node Fibers or npm packages derived from it. But Fibers just cannot solve the problem I am facing. Even the example provided by Fibers' author illustrated the deficiency:
-
Strategies for server-side rendering of asynchronously initialized React.js components
React-async. This approach is perfect. It lets me simply define in a special function in each component how to initialize the state (doesn't matter whether synchronously or asynchronously) and these functions are called as the hierarchy is being rendered to HTML. It works in a way that a component is not rendered until the state is completely initialized. The problem is that it requires Fibers which is, as far as I understand, a Node.js extension that alters the standard JavaScript behavior. Although I really like the result, it still seems to me that instead of finding a solution we changed the rules of the game. And I think we shouldn't be forced to do that to use this core feature of React.js. I'm also not sure about the general support of this solution. Is it possible to use Fiber on standard Node.js web hosting?
What are some alternatives?
react-refetch - A simple, declarative, and composable way to fetch data for React components
flux-examples - Isomorphic Flux examples with Fluxible
redux-async-connect - It allows you to request async data, store them in redux state and connect them to your react component.
React - The library for web and native user interfaces.
async-props - Co-located data loading for React Router
redux-connect - Provides decorator for resolving async props in react-router, extremely useful for handling server-side rendering in React
react-resolver - Async rendering & data-fetching for universal React applications.
react-router-relay - [Deprecated] Relay Classic integration for React Router
redial - Universal data fetching and route lifecycle management for React etc.
axios-react - 🌐 HTTP client component for React based on Axios