react-virtual
Hooks for virtualizing scrollable elements in React
About
Hooks for virtualizing scrollable elements in React
What detecting react-virtual tells you about a site
react-virtual is the legacy, pre-TanStack name of what is now @tanstack/react-virtual, so seeing this older package name is itself a dating signal: the code predates Tanner Linsley's TanStack rebrand and has not been migrated. Functionally it means the app virtualises long lists or grids, rendering only visible rows, which tells you it handles large datasets (feeds, tables, logs) and that performance under volume mattered enough to reach for windowing. The unmigrated name hints at a codebase that has not been heavily touched recently.
Why the exact react-virtual version matters
Because react-virtual was superseded by the renamed @tanstack/react-virtual, any version here is by definition on the deprecated line; the exact version mainly tells you how far back the project froze and that it never adopted the TanStack-era hook API. It is most useful as an age and maintenance indicator.
react-virtual in a real-world stack
When you find react-virtual in a bundle, it rarely travels alone. React, typically with a table or list-heavy UI; the modern replacement is @tanstack/react-virtual.
Quick facts
npm install react-virtualCommon pairings
Packages this one expects to find in the same project. Each is also a Sourcemap Explorer detection target.
What react-virtual pulls in
react-virtual declares 1 direct dependency — each one also rides into any bundle that ships 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 react-virtual
react-virtual ships as v2.10.4, published 2022-01-21 and carries 1 direct dependency, 1 peer dependency (react), 44 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when react-virtual rides inside a deployed bundle — here is how the detection works.
We catch 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/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 `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/react-virtual/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/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/react-virtual/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.
Major releases of react-virtual
When each major version first landed. Major bumps are where breaking changes live, so this timeline is the fastest way to date the react-virtual version a site actually ships against the ecosystem.
Recent versions
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 react-virtual used for?
Hooks for virtualizing scrollable elements in React
How can I tell if a website is using react-virtual?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `react-virtual` from two complementary signals: `node_modules/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 react-virtual a website is running?
Read it straight from the site's JavaScript sourcemap. When a build ships source maps, the bundled `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/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 2.10.4, but real deployments frequently run an older pinned version — which is exactly why reading the bundled number matters.
What is the latest version of react-virtual?
2.10.4, 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 react-virtual actively maintained?
Quiet at the moment — no new release in over two years. Worth checking the repository for an active fork before adopting on a new project. The last published release was 2022-01-21. Source code: https://github.com/tannerlinsley/react-virtual.
Where can I read more?
Project homepage: https://github.com/tannerlinsley/react-virtual#readme. Source code: https://github.com/tannerlinsley/react-virtual. Published on npm: https://www.npmjs.com/package/react-virtual. Licensed as MIT.
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for react-virtual and report the precise version (the registry's latest is v2.10.4, published 2022-01-21; the bundled copy is often older). Without sourcemaps, an import / require in the page's scripts is enough to flag it.