cloudflare/vinext
`useLinkStatus`: pending state sticky after navigation / shallow routing completes
クローズ
#1,527 opened on 2026/05/22
adapter-api-e2ehelp wanted
Repository metrics
- Stars
- (8,625 個のスター)
- PR merge metrics
- (平均マージ 1d 1h) (30d で 462 merged PRs)
説明
This issue was created by an agent analysing CI failures from the Next.js Deploy Suite (vinext
mainvs Next.jsv16.2.6, 2026-05-22).
Problem
useLinkStatus() is expected to return { pending: false } once a navigation has settled (including shallow routes). vinext reports pending: 1 after navigation, and the dev-overlay debug element never appears.
Expected pending: 0, received pending: 1 after navigation settles
Estimated Impact
~3 test failures across the deploy suite.
Affected Test Suites
test/e2e/use-link-status/index.test.ts(3 failures)
Recommendation
-
Reproduce first in vinext's own test suite. Render a component subscribing to
useLinkStatus()and click a<Link>; assert pending flips false after navigation. -
Clear pending on navigation lifecycle end. Wire the link-status subscription to the navigation commit lifecycle. Include shallow routing in the clear path.
Part of #1328.