CAF VS posterus

Consumer vs. Producer - "Redux Saga is said to be about managing side effects..." I'm not sure this description is a million miles from what you're trying to achieve (although I'm struggling a little to comprehend) Redux Saga is essentially a set of APIs around yield that goes quite far in doing what you describe: Making the consumer of a chain of a/synchronous tasks more in control of the flow. Also worth your consideration might be Cancelable Async Flows.

The absolute best use case for generator functions is for making cancellable async flows: https://github.com/getify/CAF

Here is link number 1 - Previous text "CAF"

To that end, CAF tries to create a more ergonomic/idiomatic way of doing this "threading" of cancelation semantics through your async tasks. Perhaps it's worth a glance: https://github.com/getify/CAF

there are some libs offering something similar: https://github.com/getify/CAF

May I suggest looking at CAF?

Check out these; - https://github.com/mitranim/posterus - https://github.com/timgit/pg-boss - https://github.com/FirebaseExtended/firebase-queue - https://www.npmjs.com/package/rabbit-queue

Async/Await covers the 80% of use cases for async logic in JS. Most people aren't really using promises as multicast references. They don't call `then` in one place, hang on to the promise reference, then call `then` again somewhere else (perhaps to represent a cached value); they call `then` once on the reference because it's just a moment in a composite operation.

It's for this reason that I think this library[0] is the more appropriate abstraction for that same 80% of use-cases, as its more memory efficient since you can represent the same composite operation that generates multiple promise references with a single object (a unicast reference instead). I haven't learned Rust but apparently the author bases this on Rust's ownership principle.

[0]https://github.com/mitranim/posterus

https://github.com/mitranim/posterus#taskdeinit