Repository navigation
fix(deps): update dependency @tanstack/virtual-core to ^3.18.0 - #79
Open
renovate-ce-paramount-engineering[bot] wants to merge 1 commit into
Open
renovate-ce-paramount-engineering[bot] wants to merge 1 commit into
renovate-ce-paramount-engineering[bot] wants to merge 1 commit into
Conversation
renovate-ce-paramount-engineering
Bot
force-pushed
the
renovate/tanstack-virtual-monorepo
branch
from
October 12, 2026 15:01
718fbe6 to
bb9916c
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^3.17.8→^3.18.0Release Notes
TanStack/virtual (@tanstack/virtual-core)
v3.18.0Compare Source
Minor Changes
43675bc- feat(virtual-core): addcancelScroll()to stop an in-flightscrollToIndex/scrollToOffset/scrollBy/scrollToEndfrom correcting toward its target, so a user gesture can take over the viewport (#1285)Patch Changes
#1276
9df47a3- FixscrollToIndex(last, { align: 'end' })overshooting the last item bypaddingEnd; it now respectsscrollPaddingEndlike other end-aligned items. To scroll to the very bottom includingpaddingEnd, usescrollToEnd().#1293
c644f10- fix(virtual-core): don't cache a 0 size whenmeasureElementreceives a node that isn't attached to the document yet#1294
2a631f4- Keep scrollToIndex reconciliation active until pending ResizeObserver measurements can update its target, including when useAnimationFrameWithResizeObserver is enabled. Respect an external scroll away from a reached target during this settling period.v3.17.11Compare Source
Patch Changes
#1284
06d1b6b- Read the current scroll offset when the debounced scroll-end fallback fires so measurement adjustments made since the last browser scroll event are not overwritten by stale state.#1248
2c0a0ea- Keep a travelling smoothscrollToIndexalive when content is prepended. WithanchorTo: 'end', the prepend anchor sync wrotescrollTopinstantly, which cancelled the browser's smooth animation and left the scroll stranded partway; Chromium drops a smooth request re-issued right after such a cancel, so it could not be resumed. The sync is now skipped while a smooth programmatic scroll is still in flight, and the animation continues to its recomputed target. A smooth scroll that has already landed still receives the anchor sync.v3.17.10Compare Source
Patch Changes
#1272
ab3278c- Keep an end-pinned virtualizer following appended items when older items are trimmed in the same update and the item count does not increase. Recognize ordered, overlapping windows while preserving reading anchors for users who have scrolled away from the end.Preserve item keys in the lazy measurement cache so a stable
getItemKeycallback reading mutable data cannot change the identity of previously measured rows.v3.17.9Compare Source
Patch Changes
4a0adf3- Recover the bottom pin when the browser clamps an end-anchored scroll compensation write.resizeItemcompensates a size change by writingscrollTopbefore the consumer has committed the new total size, so when the grown item does not itself extend the scroll range the browser clamps the write to the old maximum and the viewport is left short of the end with no scroll event to correct it. Two cases hit this:paddingEnd > 0with a growing last item, where the overflowing item only extendsscrollHeightto its own end and the clamp lands exactlypaddingEndshort (#1258); and a row above the last one growing while the last row keeps its size, underdirectDomUpdates(#1266). A compensation write whose target exceeds the scroll maximum at write time is now recorded as clamped and re-issued once the sizer has grown — right afternotifyfor consumers that size the container synchronously inonChange, and from_willUpdatefor consumers that size it during a render. The clamped read-back keeps the retry pending; any other scroll event cancels it, so a user reading history is never yanked.Configuration
📅 Schedule: (in timezone America/Los_Angeles)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate CE.