cloudflare/vinext

App Router: static-sibling info not included in server response

Closed

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

Next.js includes static sibling route names in the SSR response (e.g. "sale", "featured", "settings", "electronics") so the client router can prefetch sibling routes. vinext does not include this metadata, so all four static-siblings tests fail on substring assertions against the HTML.

Expected substring: "\"sale\"" — static sibling names missing from SSR response

Estimated Impact

~4 test failures across the deploy suite.

Affected Test Suites

  • test/e2e/app-dir/static-siblings/static-siblings.test.ts (4 failures)

Recommendation

  1. Reproduce first in vinext's own test suite. Add a route group with multiple sibling pages and assert the SSR response embeds the sibling route names.

  2. Emit static-sibling info in the RSC payload. When rendering a route, include the names of its sibling routes (from the route table) in the serialised payload so the client router can prefetch them.

Part of #1328.

Contributor guide

Research direction
Reproduce the issue by adding sibling routes to the test suite and inspect the RSC payload to find where static sibling names should be emitted. Then modify the route rendering logic to include sibling route names in the serialized output.
Tech stack
typescriptreact
Domain
backendfull stack
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.
Half day
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.
Clear
Prerequisites
ReactNext.js routing concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60