@tanstack/react-virtual
- 3.14.20 is the latest, published 15 October 2026.
- No known security advisory.
- 3.x: 87 releases since 1 December 2023, 14 in the last 90 days.
Releases in the last 90 days
Feed of releases and advisoriesEvery stable release, newest first. Notes are quoted as the maintainers published them.
3.14.20
15 October 2026Updated dependencies:
Patch Changes
Updated dependencies:
@tanstack/virtual-core@3.19.5
3.14.19
13 October 2026Updated dependencies:
Patch Changes
Updated dependencies:
@tanstack/virtual-core@3.19.4
3.14.18
13 October 2026Updated dependencies:
Patch Changes
Updated dependencies:
@tanstack/virtual-core@3.19.3
3.14.17
12 October 2026Updated dependencies:
Patch Changes
Updated dependencies:
@tanstack/virtual-core@3.19.2
3.14.16
12 October 2026Updated dependencies:
Patch Changes
Updated dependencies:
@tanstack/virtual-core@3.19.1
3.14.15
11 October 2026Updated dependencies:
Patch Changes
Updated dependencies:
@tanstack/virtual-core@3.19.0
3.14.14
9 October 2026Rows were only positioned by the owner's layout effect or the next onChange. A row mounted by a child that re-renders on its own (local state, context, a resolved Suspense boundary) skipped both when it was fixed-size, and stayed unpositioned until the range changed. Rows are now positioned as they register through measureElement, and containerRef positions the rows that mounted together with the container.
Patch Changes
fix(react-virtual): position
directDomUpdatesrows that mount without the owner re-rendering
Rows were only positioned by the owner's layout effect or the next
onChange. A row mounted by a child that re-renders on its own (local state, context, a resolved Suspense boundary) skipped both when it was fixed-size, and stayed unpositioned until the range changed. Rows are now positioned as they register throughmeasureElement, andcontainerRefpositions the rows that mounted together with the container.Updated dependencies:
@tanstack/virtual-core@3.18.0
3.14.13
14 September 2026Updated dependencies:
Patch Changes
Skip
flushSyncfor the synchronous notify raised frommeasureElement. React callsmeasureElementfrom a ref callback, i.e. while it is committing, andflushSynccannot flush there — it warns in development instead. The commit phase already runs at discrete (sync) priority, so the update lands in the same lane and the same frame withoutflushSync. Notifies from every other path (ResizeObserver re-measures, scroll adjustments) still flush synchronously.
Updated dependencies:
@tanstack/virtual-core@3.17.11
3.14.12
11 September 2026Updated dependencies:
Patch Changes
Updated dependencies:
@tanstack/virtual-core@3.17.10
3.14.11
7 September 2026Updated dependencies:
Patch Changes
Updated dependencies:
@tanstack/virtual-core@3.17.9
Show 4 earlier releases
3.14.10
18 August 2026Updated dependencies:
Patch Changes
Updated dependencies:
@tanstack/virtual-core@3.17.8
3.14.9
28 July 2026Updated dependencies:
Patch Changes
Updated dependencies:
@tanstack/virtual-core@3.17.7
3.14.8
22 July 2026Updated dependencies:
Patch Changes
Fix a gap at the top of the list after an end-anchored prepend in
directDomUpdatesmode. The prepend grows the total size and bumpsscrollOffsetto the new bottom in the same pass, but the size container's height was written after_willUpdatesynced the scroll position — so the browser clamped thescrollTopwrite to the stale (shorter)scrollHeight, leaving whitespace at the top until the next scroll. The container is now grown before the scroll sync. Only affecteddirectDomUpdatesmode (React-rendered sizers receive their height during render).
Updated dependencies:
@tanstack/virtual-core@3.17.6
3.14.7
20 July 2026Updated dependencies:
Patch Changes
Updated dependencies:
@tanstack/virtual-core@3.17.5
Quality and security signals
What npm and deps.dev say about the latest release. Signals, not a verdict.
Reading npm and deps.dev…
Registry facts last checked 15 October 2026. Releases and advisories last read 15 October 2026.
Know when your own dependencies move
Inlinr tracks your coding time automatically. Switch dependency tracking on for a project and it reads that repository's manifest to show what is behind and what has been deprecated — off by default, one project at a time.