react-svelte
react-query
react-svelte | react-query | |
---|---|---|
2 | 190 | |
301 | 27,869 | |
- | - | |
0.0 | 9.1 | |
over 1 year ago | almost 2 years ago | |
JavaScript | TypeScript, JS | |
GNU General Public License v3.0 or later | 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.
react-svelte
-
Virtual DOM is pure overhead
Reactās changes over time have always been broadly compatible, and the same under the hood, just presented and manipulated a different way at the surface. Migrating to anything like Svelte would be a radical and extremely incompatible change on multiple fronts. Itās never, ever going to happen; the closest youāll get will be another layer on top of React that embeds something like Svelteāsuch as https://github.com/Rich-Harris/react-svelte.
Svelteās approach requires detailed knowledge of the structure of state, and requires compilation: componentsā blocks are not written in JavaScript, but rather a language with the same general syntax but different semantics, and some places where JavaScript is too flexible to be tractable get replaced with special template syntax (like {#each} instead of for-loops or Array.prototype.map). Svelte cannot be implemented as a JavaScript library (I disqualify eval()). Svelte is also deliberately severely limited in what it can express in various places, whereas React gives you the full power of JavaScript (for better and for worse).<p>You could perhaps implement an optimising compiler for a small subset of React components that avoid problematic patterns and are written in TypeScript with proper specifications of the types of state and props; but if you considered it unacceptable for this compiler to change the componentās semantics, I think youād be surprised at how little serious React code in the wild could actually be supported. Even simple loops <i>might</i> be out of reach. The Svelte approach canāt be a progressive enhancement, itās an all-or-nothing (at the component level).
- I need help with a Svelte/Storybook/React implementation
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?
budibase - Budibase is an open-source low code platform that helps you build internal tools in minutes š
SWR - React Hooks for Data Fetching
uibuilder - Typed HTML templates using TypeScript's TSX files
axios - Promise based HTTP client for the browser and node.js
Tailwind CSS - A utility-first CSS framework for rapid UI development.
redux-saga - An alternative side effect model for Redux apps
htmx - </> htmx - high power tools for HTML
rtk-query - Data fetching and caching addon for Redux Toolkit
zustand - š» Bear necessities for state management in React
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.
urql - The highly customizable and versatile GraphQL client with which you add on features like normalized caching as you grow.
redux-toolkit - The official, opinionated, batteries-included toolset for efficient Redux development