Reactive Data Client

dataclient.io/docs/concepts/… normalized data brings up to 93x performance over react fetch frameworks like react query

TypeScript 6.0 is now available! This release brings better type-checking for methods, new standard library features, new module features for Node.js, and more! But most important, this release brings us one step closer to the upcoming native-speed 7.0! devblogs.microsoft.com/typescript/ann…

dataclient.io/blog/2026/01/0… Vue 3 support!

Check out what react 19 + data client can do for your user experience

Handle errors and loading fallbacks with one AyncBoundary dataclient.io/docs/api/Async…. Compatible with all #ReactJS data libraries including #NextJS.

NextJS Client components enable the best of both worlds. Server rendering means fast initial load. Client hydration means immediate interactivity and improved usages performance over SSG. #nextjs" target="_blank" rel="nofollow noopener">dataclient.io/docs/guides/ss…

Building a #ReactJS application with a #Django backend is easy when you have good inheritance paradigms dataclient.io/rest/guides/dj…

dataclient.io/rest/api/schema JSX for data management. Turns out writing 0 state management code can also give you the best performance in React.

Introducing Codemod2.0! 🎉 Combining deterministic engines for scalable detection with LLM for intelligent transformation. Use your own model with a familiar command: npx codemod --OPENAI_API_KEY=xxx Learn more → go.codemod.com/codemod2

In React 18, two components that are siblings to each other can suspend together within the same Suspense Boundary because React keeps (pre-)rendering siblings even if one component suspends. So this works: Both components have a suspending fetch inside, both will fetch in parallel and will be "revealed" together because they are in the same boundary. In React 19, this will be a request waterfall: When the first component suspends, the second one never gets to render, so the fetch inside of it won't be able to start. The argument is that rendering the second component is not necessary because it will be replaced with the fallback anyway, and with this, they can render the fallback "faster" (I guess we are talking fractions of ms here for most apps. Rendering is supposed to be fast, right?). So if the second component were to trigger a fetch well then bad luck, better move your fetches to start higher up the tree, in a route loader, or in a server component.

dataclient.io/blog/2024/04/0… Full safe store access using schemas 🔥

React Native 0.73.0 is out! This release brings Debugging Improvements, Stable Symlink Support, Android 14 Support, and more ⬇️ reactnative.dev/blog/2023/12/0…

Today we released TypeScript 5.3! Now bringing: - new narrowing improvements - more correctness checks - import attributes - handy new editor features - lots of optimizations and lots more! So try it today! devblogs.microsoft.com/typescript/ann…

Lots of narrowing improvements mean improved safety without 0 developer work!

const getTodo = new RestEndpoint({ path: '/todos/:id', }); #TypeScript async functions using path templates dataclient.io/rest/api/RestE…