effection
redux-saga
Our great sponsors
effection | redux-saga | |
---|---|---|
5 | 42 | |
485 | 22,501 | |
7.4% | 0.0% | |
9.3 | 4.0 | |
about 2 months ago | 18 days ago | |
TypeScript | 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.
effection
-
Bun, JavaScript, and TCO
While working on effection (https://github.com/thefrontside/effection) we spent a bunch of time ensuring that our delimited continuations could handle deep recursive call stacks in Deno.
PR: https://github.com/thefrontside/continuation/pull/11
TCO would have definitely simplified this issue.
What’s worse is hitting maximum memory callstack exception is very tricky to catch and is not reliable across runtimes. So when a user hits it it can be tricky to track down.
-
Effection 3.0 – Structured Concurrency and Effects for JavaScript
`redux-saga` maintainer here.
I've been using `effection` to build a replacement for `redux-saga` over at https://github.com/neurosnap/starfx
Effection has demonstrated to me how truly powerful delimited continuations are and why structured concurrency is an incredible asset for anything that requires async flow control -- basically everything in TS/JS.
I know sometimes it's hard to imagine why someone would need structured concurrency or care about delimited continuations for a front-end application, but this is a game changer in terms of expressing async flow control.
Some things to note about Effection:
- API surface area is small https://github.com/thefrontside/effection/issues/851
- It tries to stay as close to JS constructs as possible so it will feel very familiar
- Resource cleanup is automatic (when a function passes out of scope all descendent tasks are shut down automatically)
- End-user doesn't need to think about delimited continuations
The only leap users need to "deal with" coming from async/await is the syntax.
import { main, call } from "effection";
-
Internals of Async / Await in JavaScript
- https://github.com/thefrontside/continuation
- https://github.com/thefrontside/effection/tree/v3
- https://github.com/neurosnap/starfx
The last one intends to replace redux-saga using DCs.
Here’s a presentation I gave recently talking about DCs in typescript: https://youtu.be/uRbqLGj_6mI?si=XI0JNMKMoO2VHMvM
-
Philosophy of Coroutines
https://github.com/thefrontside/effection/tree/v3
- Effection: Structured concurrency and effects framework for JavaScript
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.
[1]: https://redux-saga.js.org/
-
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
-
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.
-
[AskJS] Where will I need to write generator functions?
redux-saga makes use of them in really nice way. https://redux-saga.js.org/ That’s where I’ve used them the most.
What are some alternatives?
myproxy - MySQL proxy
redux-toolkit - The official, opinionated, batteries-included toolset for efficient Redux development
starfx - A modern approach to side-effect and state management for web apps.
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]
kal - A powerful, easy-to-use, and easy-to-read programming language for the future.
rtk-query - Data fetching and caching addon for Redux Toolkit
assembly - assembly projects
axios - Promise based HTTP client for the browser and node.js
libcommon - Library of reusable C++ code
SWR - React Hooks for Data Fetching
Async Ruby - An awesome asynchronous event-driven reactor for Ruby.
Immer - Create the next immutable state by mutating the current one