boxed
redux-saga
boxed | redux-saga | |
---|---|---|
6 | 42 | |
613 | 22,504 | |
2.3% | -0.0% | |
8.4 | 4.0 | |
5 days ago | 25 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.
boxed
- Boxed: Functional Types and Utilities for TypeScript
-
The gotcha of unhandled promise rejections
I was happy when Promise became available, but in retrospect I'd wish we would have skipped ahead and gotten Observable (e.g: https://rxjs.dev/) instead to enable more powerful functionality and composition etc.
In Typescript dealing with rejection is also painful since rejection reasons can't be guaranteed to be Error even when you always take care of that. And it can't help you guarantee that you're handling all types of errors thrown. For that purpose I'm thinking of using https://github.com/supermacro/neverthrow#readme or https://swan-io.github.io/boxed.
- Boxed: Functional utility types and functions for TypeScript
-
I Avoid Async/Await
Agree that try/catch is verbose and not terribly ergonomic, but my solution has been to treat errors as values rather than exceptions, by default. It's much less painful to achieve this if you use a library with an implementation of a Result type, which I admin is a bit of a painful workaround, but worth it. I've recently been using: https://github.com/swan-io/boxed.
By far the greatest benefit is being able to sanely implement a type-safe API. To me, it is utter madness throwing custom extensions of the Error class arbitrarily deep in the call-stack, and then having a catch handler somewhere up the top hoping that each error case is matched and correctly translated to the intended http response (at least this seems to be a common alternative).
- Boxed: Utility Types for Functional TypeScript
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?
async - Easily run code asynchronously
redux-toolkit - The official, opinionated, batteries-included toolset for efficient Redux development
neverthrow - Type-Safe Errors for JS & TypeScript
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]
cofx - A node and javascript library that helps developers describe side-effects as data in a declarative, flexible API.
rtk-query - Data fetching and caching addon for Redux Toolkit
rescript-compiler - The compiler for ReScript.
axios - Promise based HTTP client for the browser and node.js
variant - Variant types in TypeScript
SWR - React Hooks for Data Fetching
async - Async utilities for node and the browser
Immer - Create the next immutable state by mutating the current one