App Router: misc navigation regressions (unicode params, useParams identity, push pending)
#1 555 ouverte le 22 mai 2026
Métriques du dépôt
- Stars
- (8 625 étoiles)
- Métriques de merge PR
- (Merge moyen 1j 1h) (462 PRs mergées en 30 j)
Description
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
A handful of app-router navigation regressions: (1) unicode search params not surfaced in the RSC ok-response stream; (2) useParams returns 0 items (no identity stability) when rendered under pages; (3) external router.push() reports lastIsPending: false instead of true. These do not cleanly fit any single existing issue.
unicode search params: expected pathname "/" with content-type text/x-component
useParams identity: Expected length 2, Received length 0
Estimated Impact
~4 test failures across the deploy suite.
Affected Test Suites
test/e2e/app-dir/navigation/navigation.test.ts(3 failures)test/e2e/app-dir/search-params-react-key/layout-params.test.ts
Recommendation
-
Reproduce first in vinext's own test suite. Cover each regression independently: unicode search params in RSC stream,
useParamsidentity stability, externalrouter.pushpending status. -
Address each root cause. Unicode: ensure search params are decoded/encoded consistently on the SSR path. useParams: stabilise the identity across renders. External push: thread the pending status back to the consumer.
Part of #1328.