crank
react-query
crank | react-query | |
---|---|---|
13 | 190 | |
2,673 | 27,869 | |
0.1% | - | |
8.1 | 9.1 | |
8 days ago | almost 2 years ago | |
TypeScript | TypeScript, JS | |
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.
crank
-
Coroutines in JavaScript for Web Components
If you enjoy this approach, you might enjoy the Crank JS framework. https://crank.js.org/
> Crank uses generator functions to define stateful components. You store state in local variables, and `yield` rather than `return` to keep it around.
- Crank.js, the Just JavaScript Framework
-
A Proposal for an asynchronous Rust GUI framework
I'm very interested in seeing if using the commonly implemented forms of compiler support for async programming can also be well used for GUI programming. One wishawa[0] is also perusing this approach in Rust but I first came upon this idea from the crank-js[1] authors. It wasn't clear to me why that one never went anywhere. Was it failure with the approach or was React just a good solution in the space? I can say this though, there's something strikingly elegant about those initial samples of using JavaScript generators for components.
[0]: https://github.com/wishawa/async_ui
[1]: https://github.com/bikeshaving/crank
Take a look at crank.js, a JavaScript framework where components can be written as async functions or as generators. It seems similar to what you're trying to do :)
- UnsuckJS: Progressively enhance HTML with lightweight JavaScript libraries
-
Algebraic Effects – You Can Touch This (2019)
Well there's https://crank.js.org that uses native js generators where you would you normally put hooks in. Never used it but looked like a very neat idea.
-
What happens if you mix React, Mobx and generators*? Ok, let's do it!
Reminds me of https://github.com/bikeshaving/crank, which was rather fun for a PoC I made a while back.
-
Are my components supposed to render multiple times?
Strictly speaking, the framework hides this complexity away, but it still exists and it is the framework that's now paying the extra cost. Of course a framework is allowed, and should, when possible, hide away these things. For example Crank.js uses generators to allow for async Components as first class citizens, https://github.com/bikeshaving/crank, but they're still having to deal with the pitfalls of asynchronous work.
-
React State Museum - Examples to help portray the how, why, which, pros, and cons of various state management systems in the React ecosystem
To give the author of https://crank.js.org/ due credit, after reading through the descriptive posts I was impressed by the amount of thought and design that went into it.
-
What's New in React 18?
> What do you propose as an alternative?
There are lots of alternatives, but perhaps the simplest would have been to use async generators. This is how Crank[0] (mentioned elsewhere in this thread) works, and it allows you to do anything (AFAIK) that's possible with hooks with a much simpler and more testable API.
> So, sure, there are limitations and rules you have to pay attention to with hooks... but that's just programming.
No, it's not. The biggest problem with React hooks is that they are not composed of transferable knowledge, meaning memorizing these rules and patterns does not transfer outside of React; likewise, I can't use much of the knowledge I have already built up over many years of my career when using hooks. It's the same argument that's made against Rails, where you have to learn tons of Rails-specific idioms (on top of having to understand general concepts like relational database access patterns) instead of just writing code in a way that's more direct and intuitive for anyone.
My brain has limited RAM. The more things I have to keep in my head when developing against an API, the more likely I am to make a mistake. With every release of React, I seem to have to keep more and more of these details in my brain as I work. Contrast this with something like Svelte, where you really only need to fully grok about two concepts to use it effectively. I understand that this is the tradeoff the React team made, but I'm not convinced it's worth it.
[0]: https://crank.js.org/ and https://crank.js.org/blog/introducing-crank
react-query
-
20 Essential Parts Of Any Large Scale React App
react-query
-
Some Very Cool (Underrated maybe) React Libraries
React Query: This library makes it easy to manage data in your React applications, from fetching to caching and updating data. It offers a simple, powerful, and flexible API for handling data and keeping your UI in sync with your data. https://github.com/tannerlinsley/react-query
-
Do I need a fetching library in React?
useQuery (react-query) (+) all from above (+) even more features (-) more complex, even the examples are complex, has more aggressive defaults (re-fetching every 2s)
-
Is there any redux-saga equivalent for zustand?
see here Overview
-
React Query Codegen from OpenAPI
Rapini is a new tool that can generate custom React Query hooks using OpenAPI (Swagger) files.
-
React hooks for 28 RxJS operators
React Query is the gold standard for using async data declaratively with hooks. I ended up needing to modify even my simple useTimer hook to work more like useQuery to take multiple keys in order to work as an inner observable for other operators.
-
Goodbye, useEffect - Reactathon 2022
For most situations, I would recommend using a library like React Query. It handles a lot of common data-fetching boiler plate and already accounts for this useEffect() issue. Also, it supports Suspense if you want to use that.
-
Managing application cache with react-query, and code generation.
At this point, I want to move on to the react-query cache management library. Give a brief overview and see how you can improve your developer experience with cache using this library.
-
When to use a hook, and when to use a service?
There isn't the "service" concept in React. If you need to send off data you can just do so with fetch. If you need to load data and cache it so it can be used across components and unmounts, then something like react-query is what I'd recommend. But it's basically a combination of React Context, useEffect, and useState to manage the cache and lifecycle of a request.
-
What would you consider to be a must for a modern 2022 dev stack?
react-query is pretty neat too. I default to that for most projects unless it's something unusual
What are some alternatives?
js-framework-benchmark - A comparison of the performance of a few popular javascript frameworks
SWR - React Hooks for Data Fetching
React - The library for web and native user interfaces.
axios - Promise based HTTP client for the browser and node.js
async_ui - Lifetime-Friendly, Component-Based, Retained-Mode UI Powered by Async Rust
redux-saga - An alternative side effect model for Redux apps
ava - Node.js test runner that lets you develop with confidence 🚀
rtk-query - Data fetching and caching addon for Redux Toolkit
sucrase - Super-fast alternative to Babel for when you can target modern JS runtimes
zustand - 🐻 Bear necessities for state management in React
solid - A declarative, efficient, and flexible JavaScript library for building user interfaces.
Recoil - Recoil is an experimental state management library for React apps. It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.