In the relentless pursuit of Core Web Vitals and instant UI responsiveness, frontend engineers inevitably hit the "runtime tax." Even gzipped, the classic react and react-dom pair weighs around 45–50 KB. On mobile networks and budget smartphones, downloading and parsing those scripts steals precious fractions of a second before the first interactive screen appears (Time to Interactive).
Historically, teams solved this by switching to Preact, though compatibility with modern ecosystems like React 19 and meta-frameworks occasionally broke down. TanStack Query creator Tanner Linsley has unveiled a radical experiment—an ultra-lightweight client-side replacement called TanStack Redact, covered in detail in the TanStack Redact documentation.
Anatomy of Redact: Dropping Fiber for Weight Savings
Redact's core idea is an uncompromising reduction in client bundle size (saving 20% to 70% compared to the original). The library is designed as a drop-in replacement: you don't rewrite a single line of your components, and simply redirect aliases in your bundler:
// vite.config.ts: swapping standard React for the ultra-lightweight Redact runtime
import { defineConfig } from 'vite';
import react from '@vitejs/plugin-react';
export default defineConfig({
plugins: [react()],
resolve: {
alias: {
'react': '@tanstack/redact',
'react-dom': '@tanstack/redact/dom',
'react-dom/client': '@tanstack/redact/dom/client',
'react/jsx-runtime': '@tanstack/redact/jsx-runtime',
},
},
});
Redact emulates almost all key hooks (useState, useEffect, useMemo, useCallback, useTransition), supports portals, and includes basic Suspense. Yet this tiny footprint is achieved by removing the core architectural pillar of React 18/19—the Fiber scheduler and Time Slicing.
The Cost of Synchronicity: CPU Load
In React 19, rendering is concurrent: if a user clicks a button during a heavy update, the browser interrupts rendering and prioritizes input. In TanStack Redact, rendering is strictly synchronous: any state change immediately and continuously recalculates the DOM subtree from top to bottom:
import React, { useState, useEffect } from 'react';
export function RealtimeFilter() {
const [query, setQuery] = useState('');
// In Redact, every keystroke triggers an immediate synchronous render cycle
useEffect(() => {
console.log('Synchronous effect fired right after the DOM update');
}, [query]);
return (
<div className="filter-box">
<input
value={query}
onChange={(e) => setQuery(e.target.value)}
placeholder="Search table..."
/>
</div>
);
}
Independent benchmarks on real-world apps reveal the harsh truth: under frequent cascading updates (dynamic filters, active animations, continuous typing), Redact consumes twice as much CPU time as standard React. The lack of smart batching loads up the Main Thread, hurting the Interaction to Next Paint (INP) metric.
Paired with the modern TanStack Start framework, Redact is a great fit for content landing pages and dashboards with infrequent updates where every kilobyte at startup matters. For heavy web apps packed with interactivity, however, the original React Fiber remains the unmatched standard.

![Node.JS [ru]](/api/digests/it_development/daily/20261101/assets/sources/we-use-js.jpg?v=afa57dd22899de281ce8acde5ab09ad661ce4a0bf3c6c59b7ff06ca9aae95f23)