cloudflare/vinext

App Router: middleware-rewritten shallow link breaks history traversal

Closed

#1,540 opened on May 22, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)TypeScript (371 forks)github user discovery
adapter-api-e2ehelp wanted

Repository metrics

Stars
 (8,563 stars)
PR merge metrics
 (Avg merge 1d 1h) (462 merged PRs in 30d)

Description

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.

Contributor guide

Research direction
Reproduce the failure in vinext's own test suite using the middleware shallow link fixture. Then investigate the navigation commit path to ensure the canonical URL is set in the history entry and the page finishes rendering after a middleware rewrite.
Tech stack
typescriptnextjsreactvite
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65