cloudflare/vinext

App Router: `proxy-nfc-traced` route redirect produces empty content

Closed

#1,546 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

A page that should be reachable via a proxy/redirect ends up rendering empty content. Root cause is unclear from the error alone (Expected: "hello world" / Received: ""); likely related to middleware proxy rewrite or NFT-traced module loading not finding the target page module after the redirect.

Expected: "hello world" Received: ""

Estimated Impact

~1 test failures across the deploy suite.

Affected Test Suites

  • test/e2e/app-dir/proxy-nfc-traced/proxy-nfc-traced.test.ts

Recommendation

  1. Reproduce first in vinext's own test suite. Run the proxy-nfc-traced fixture and capture the underlying error or empty response.

  2. Investigate NFT module tracing and proxy rewrites. The empty content likely means the production server cannot resolve the target page module after the rewrite. Add logging in the route dispatcher.

Part of #1328.

Contributor guide

Research direction
Inspect the failing test `proxy nfc traced.test.ts` and trace the route handler path to identify where the empty content is generated. Investigate middleware proxy rewrite and NFT traced module loading.
Tech stack
typescriptnextjs
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
Needs investigation
Prerequisites
TypeScriptNext.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20