`useLinkStatus`: pending state sticky after navigation / shallow routing completes
#1,527 创建于 2026年5月22日
仓库指标
- 星标
- (8,563 个星标)
- PR 合并指标
- (平均合并 1天 1小时) (30 天内合并 462 个 PR)
描述
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.