cloudflare/vinext

App Router: middleware-rewritten shallow link breaks history traversal

クローズ

#1,540 opened on 2026/05/22

 (0 件のコメント) (0 件のリアクション) (0 人の担当者)TypeScript (383 件のフォーク)github user discovery
adapter-api-e2ehelp wanted

Repository metrics

Stars
 (8,624 個のスター)
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 main vs Next.js v16.2.6, 2026-05-22).

Problem

After a middleware-rewritten navigation, the back button ([data-go-back]) never becomes visible, indicating the rewritten page never finishes rendering or history state isn't wired up. May relate to the canonical-URL handling from #1348.

[data-go-back] never visible after middleware-rewritten navigation

Estimated Impact

~1 test failures across the deploy suite.

Affected Test Suites

  • test/e2e/middleware-shallow-link/index.test.ts

Recommendation

  1. Reproduce first in vinext's own test suite. Use the middleware-shallow-link fixture and assert the back button appears after the rewrite.

  2. Investigate the navigation commit path. After a middleware rewrite, the canonical URL must be set in the history entry and the page must finish rendering.


Part of #1328.

コントリビューターガイド