@tanstack/react-virtual
Headless UI for virtualizing scrollable elements in React
About
Headless UI for virtualizing scrollable elements in React
What detecting @tanstack/react-virtual tells you about a site
@tanstack/react-virtual is the current TanStack windowing library, so its presence tells you the app renders large collections efficiently by mounting only visible items, and that the team is bought into the TanStack ecosystem and its modern, hooks-first conventions. It is a precise, headless tool, so finding it implies real data scale (long feeds, big tables, virtualised grids) and an engineering team that profiled rendering cost rather than reaching for it casually. It pairs naturally with other TanStack tools.
Why the exact @tanstack/react-virtual version matters
This package carries the TanStack v3-era versioning, where the virtualizer API, measurement model and options were refined across releases, so the version pins which hook shape and which dynamic-measurement capabilities the code uses. It also confirms the project is on the rebranded, maintained line rather than the deprecated react-virtual.
@tanstack/react-virtual in a real-world stack
When you find @tanstack/react-virtual in a bundle, it rarely travels alone. Frequently @tanstack/react-query and @tanstack/react-table in the same TanStack-heavy app.
Quick facts
npm install @tanstack/react-virtualCommon pairings
Packages this one expects to find in the same project. Each is also a Sourcemap Explorer detection target.
What @tanstack/react-virtual pulls in
@tanstack/react-virtual declares 1 direct dependency — each one also rides into any bundle that ships @tanstack/react-virtual, so they are detection targets too. Reading them is a quick way to understand the package's real footprint .
How Sourcemap Explorer detects @tanstack/react-virtual
@tanstack/react-virtual ships as v3.14.9, published 2026-07-28 and carries 1 direct dependency, 2 peer dependencies (react, react-dom), 134 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when @tanstack/react-virtual rides inside a deployed bundle — here is how the detection works.
We catch @tanstack/react-virtual from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/@tanstack/react-virtual/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.
- 1
Confirm the site exposes sourcemaps
In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment — that map is where the `@tanstack/react-virtual` paths live.
- 2
Find the package in the bundle
Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/@tanstack/react-virtual/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/@tanstack/react-virtual/package.json` gives you the exact installed version.
- 3
Read the version directly from package.json
Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/@tanstack/react-virtual/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.
Recent versions
@tanstack/react-virtual README
Live mirror of the GitHub README, for reference. Updated whenever the repo's default branch changes.
TanStack Virtual
A headless, framework‑agnostic virtualization library for rendering massive lists, grids, and tables at 60FPS while giving you full control over markup and styles.
- Framework‑agnostic & headless
- Virtualizes vertical, horizontal & grid layouts with a single hook/function
- Lightweight (10–15kb) yet powerful, with dynamic & measured sizing support
- Smooth 60FPS scrolling with sticky items and window‑scrolling utilities
Read the docs →
Get Involved
- We welcome issues and pull requests!
- Participate in GitHub discussions
- Chat with the community on Discord
- See CONTRIBUTING.md for setup instructions
Partners
|
|
We're looking for TanStack Virtual Partners to join our mission! Partner with us to push the boundaries of TanStack Virtual and build amazing things together.
LET'S CHATExplore the TanStack Ecosystem
- TanStack Config – Tooling for JS/TS packages
- TanStack DB – Reactive sync client store
- TanStack DevTools – Unified devtools panel
- TanStack Form – Type‑safe form state
- TanStack Pacer – Debouncing, throttling, batching
- TanStack Query – Async state & caching
- TanStack Ranger – Range & slider primitives
- TanStack Router – Type‑safe routing, caching & URL state
- TanStack Start – Full‑stack SSR & streaming
- TanStack Store – Reactive data store
- TanStack Table – Headless datagrids
… and more at TanStack.com »
FAQ
What is @tanstack/react-virtual used for?
Headless UI for virtualizing scrollable elements in React
How can I tell if a website is using @tanstack/react-virtual?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `@tanstack/react-virtual` from two complementary signals: `node_modules/@tanstack/react-virtual/` paths inside the JavaScript sourcemap, and the embedded `package.json` we read for exact-version detection. Without the extension you can do the same lookup manually in DevTools — the steps are listed in the "How Sourcemap Explorer detects" section above.
How do I find out which version of @tanstack/react-virtual a website is running?
Read it straight from the site's JavaScript sourcemap. When a build ships source maps, the bundled `@tanstack/react-virtual/package.json` carries the exact `version` string — Sourcemap Explorer extracts it in one click on the Stack tab, and you can do it by hand in DevTools by opening the `.map` file and searching for `node_modules/@tanstack/react-virtual/package.json`. That is far more reliable than inferring the version from an asset-hash or a `?ver=` query string, which is all surface-level detectors have to go on. The current npm release is 3.14.9, but real deployments frequently run an older pinned version — which is exactly why reading the bundled number matters.
What is the latest version of @tanstack/react-virtual?
3.14.9, as published on the npm registry. The "Recent versions" table on this page lists the most recent 8 releases with their release dates. Sourcemap Explorer reports the version actually bundled into a site, which can lag the latest release by months on real-world deployments.
Is @tanstack/react-virtual actively maintained?
Very actively maintained — the last release shipped within the past three months. The last published release was 2026-07-28. Source code: https://github.com/TanStack/virtual.
Where can I read more?
Project homepage: https://tanstack.com/virtual. Source code: https://github.com/TanStack/virtual. Published on npm: https://www.npmjs.com/package/@tanstack/react-virtual. Licensed as MIT.
Keep reading on Sourcemap Explorer
Detection deep dives
Alternative tools
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for @tanstack/react-virtual and report the precise version (the registry's latest is v3.14.9, published 2026-07-28; the bundled copy is often older). Without sourcemaps, an import / require in the page's scripts is enough to flag it.