react-relay
redux-saga
Our great sponsors
react-relay | redux-saga | |
---|---|---|
50 | 42 | |
18,145 | 22,507 | |
0.3% | 0.0% | |
9.7 | 4.4 | |
5 days ago | 11 days ago | |
Rust | JavaScript | |
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-relay
-
Server-side Rendering (SSR) From Scratch with React
Inside Woovi, our entire codebase is managed by GraphQL using the Relay client framework. To ensure the best UX possible for our final user, we give some useful features in our payment link, like the real-time update after paying a charge. It's all handled by our GraphQL, which won't be solvable by templates in our use case.
-
Seeking advice: Should I continue my Web Developer job or pursue my passion for compilers?
Since you mentioned Node CRUD APIs, I'd probably suggest looking at Relay/GraphQL. Would give you exposure to some interesting and employable skills that wouldn't require you learning an entirely new domain on top of it. They are rewriting the current compiler in Rust, which since you mentioned Rust might be interesting to follow. Uneducated takes, but GraphQL is a schema IDL, so would probably be a good place to start to minimize lexical complexity while still having some cool abstract concepts to learn (interfaces, unions, etc).
-
Compressing GraphQL Global Node ID
You may be familiar with Global Object Identification(GOI), especially if you've used Relay.
-
Top React Data Fetching Libraries
Relay (17k ⭐) -> The production-ready GraphQL client for React, developed by Facebook, was designed to be performant from the ground up, built upon locally declaring data dependencies for components.
-
Twitter open sources Navi: High-Performance Machine Learning Serving Server in Rust
I think open sourcing for free labor is a common misconception. Most corporate led open source projects (eg, https://github.com/bottlerocket-os/bottlerocket from AWS or https://github.com/facebook/relay from Facebook) still require a team of employees.
-
How Woovi uses Relay?
If you look at relay.dev, Relay is the GraphQL client that scales with you. This definition is simple and defines Relay pretty well for the ones that already know all the features that Relay brings to the table.
-
Is it possible to create a symbolic link to a folder to solve case sensitivity?
https://github.com/psf/black/issues/338 https://github.com/VeriorPies/ParrelSync/issues/61 https://github.com/prusa3d/PrusaSlicer/issues/5751 https://github.com/iterative/dvc/issues/2530 https://github.com/facebook/relay/issues/3647 And I know godmode9 at one point absolutely freaked when navigating into a symlink. It kinda depends on the app and what it's trying to load
-
Keeping React app in sync with backend/database
It does, however, have a steep learning curve and messy documentation, plus needs nontrivial effort to set it up. I recommend deep diving into the example at http://relay.dev and playing with a test project first before you try to integrate it into your main app.
-
Introduction to GraphQL
Despite you may not want to use Relay (or even React) to consume your GraphQL data, their specification is very useful and provides a common ground of what developers should expect from a GraphQL server.
-
Why Would Anyone Need JavaScript Generator Functions?
For a concrete example, Relay uses them to garbage collect data in an asynchronous fashion. If an update is detected during the course of a gc, it is aborted.
https://github.com/facebook/relay/blob/main/packages/relay-r...
redux-saga
- Main-Thread-Scheduling
-
Creating Own Chat GPT
For the backend, we chose Python, Django Rest Framework. On the frontend, React, Redux, Saga, Sass. Let’s start with the backend, which was managed by Yegor. He writes about the server part of the project himself.
-
Internals of Async / Await in JavaScript
The whole article properly the best explanation of generators I have come across. This quote stuck out:
> Generators are a special type of function that can return multiple pieces of data during its execution. Traditional functions can return multiple data by using structures like Arrays and Objects, but Generators return data whenever the caller asks for it, and they pause execution until they are asked to continue to generate and return more data.
Applications of generators? I have only used Redux-Saga[1]. Can't even think of other libraries that use them, but would be interested in learning.
-
Generators in the wild
redux-saga. The most popular effects library in js
-
I don't get why I should use Redux
Redux can be extended with a lot of other packages. For example with a side effect manager, you can separate side effects from your business logic, help with error handling and in the same process make testing of side effects a lot easier.
-
What Is The Best Name for This Synchronous Function?
Consumer vs. Producer: Check out Redux Saga
-
Front-end Guide
Your app will likely have to deal with async calls like making remote API requests. redux-thunk and redux-saga were created to solve those problems. They may take some time to understand as they require understanding of functional programming and generators. Our advice is to deal with it only when you need it.
-
Why Would Anyone Need JavaScript Generator Functions?
Hey thanks for the thoughtful response.
I agree with everything you mentioned here. I'd love to continue to chat with you about how to make testing sagas better.
If you'd like, it would be great if we could move this convo to https://github.com/redux-saga/redux-saga/discussions/2337
Redux-sagas[0] makes great use of generators. I found it a fantastic tool, if you're already in the redux ecosystem, and have an application that sprawls enough to benefit. It's great when you have to manage multiple process lifecycles. A single "saga" can represent the entire lifespan of a session in just a few lines of code, a socket or similar long-lived process, with clear code branches to shorter-lived handlers or other sagas for the details.
The downsides are:
- a quirky syntax that needs learning, and is of the "loose with semantics" style - like Rails-eque REST's play with HTTP methods
- it's hard to test (despite what the documentation claims). It's highly declarative, and such code seems hard to test.
-
What is the best plan to catch data from multiple api calls and display some data
If there are dependent API calls, you can probably look at redux-saga. It’s one of the best libraries out there to manage the data.
What are some alternatives?
redux-toolkit - The official, opinionated, batteries-included toolset for efficient Redux development
react-query - 🤖 Powerful asynchronous state management, server-state utilities and data fetching for TS/JS, React, Solid, Svelte and Vue. [Moved to: https://github.com/TanStack/query]
rtk-query - Data fetching and caching addon for Redux Toolkit
axios - Promise based HTTP client for the browser and node.js
SWR - React Hooks for Data Fetching
apollo-client - :rocket: A fully-featured, production ready caching GraphQL client for every UI framework and GraphQL server.
Immer - Create the next immutable state by mutating the current one
Next.js - The React Framework
urql - The highly customizable and versatile GraphQL client with which you add on features like normalized caching as you grow.