redux-saga

Create the middleware with createSagaMiddleware, mount it via applyMiddleware when creating the Redux store, then call sagaMiddleware.run(rootSaga). Calling run before the middleware is mounted on the store is invalid and a common setup mistake.

fork creates an attached task: the parent waits for it, child errors bubble up, and cancellation propagates downward. spawn creates a detached task that shares none of the parent's completion, error, or cancellation flow, so use it only for intentional top-level work.

Yes, takeEvery, takeLatest, takeLeading, throttle, and debounce all accept a Channel in place of a pattern natively. Avoid building wrapper utilities around these helpers unless they add cleanup, typing, or domain-specific value.

take auto-terminates the saga when it receives END from a closed channel, while takeMaybe returns the END object so the saga can handle closure itself. Close channels you own in a finally block and use flush to recover buffered messages during cleanup.

Use cloneableGenerator from @redux-saga/testing-utils to create cloneable generator instances for branch testing, and createMockTask to mock Task objects for fork, join, and cancel flows. Prefer effect-level assertions for small generators.

Use runSaga to execute a saga outside Redux middleware by providing a channel for take, a dispatch function for put, and getState for select. It returns the same Task interface as middleware.run, suiting standalone or non-Redux execution.