FSA-compliant promise middleware for Redux that dispatches resolved or rejected promise values as actions.
Redux Promise is a middleware for Redux that handles promises and Flux Standard Action-compliant actions with promise payloads. It automatically dispatches the resolved or rejected values of promises as Redux actions, simplifying asynchronous logic in Redux applications. It is designed to work seamlessly with FSA specifications and supports server-side rendering by returning promises to the caller.
Redux developers building applications with asynchronous operations who want a standardized, FSA-compliant way to handle promises without manual dispatch logic.
Developers choose Redux Promise for its simplicity in integrating promise-based async logic with Redux, FSA compliance for consistent action structures, and built-in support for server-side rendering scenarios.
FSA-compliant promise middleware for Redux.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically dispatches resolved or rejected promise values as Redux actions, eliminating manual dispatch boilerplate for async operations, as described in the README.
Adheres to Flux Standard Action specifications, ensuring consistent action structures with payload and error handling, which simplifies integration and reduces inconsistencies.
Returns a promise from the middleware, enabling middleware chains to wait for async operations to complete, crucial for SSR setups where data fetching is required before rendering.
Works well with redux-actions for creating async action creators, reducing boilerplate and streamlining promise-based workflows, as demonstrated in the README examples.
Does not dispatch actions at the start of async operations, making it unsuitable for applications needing immediate UI feedback, a limitation explicitly mentioned in the README.
Focuses solely on promises and lacks support for other async patterns like observables or generators, which are often required for more complex side effects or cancellations.
Tightly coupled with Redux, so it cannot be used in projects with other state management libraries or those transitioning away from Redux, limiting its applicability.