cloudflare/vinext

Pages Router prerender: pages under `/api-...` and lazy catchall pages never finish loading

Closed

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

Pages whose path begins with /api-docs/... (an apparent false positive of API-route detection) and lazy fallback catch-all pages (fallback: true) hang waiting for the rendered content. The fallback boundary stays on fallback text and never resolves to the page contents.

page.waitForSelector('#api-docs') timeout

TIMED OUT: /Hi.*?delayby3s/

Estimated Impact

~3 test failures across the deploy suite.

Affected Test Suites

  • test/e2e/prerender.test.ts (3 failures)

Recommendation

  1. Reproduce first in vinext's own test suite. Add a Pages Router page at pages/api-docs/index.tsx and a [...slug] lazy catchall. Verify each finishes loading.

  2. Tighten API-route detection. Match only pages/api/... (with the slash), not the substring api-. Otherwise pages whose path starts with api- are treated as API routes and never render.

  3. Resolve the fallback for lazy catchall. Make sure the prerender fallback resolves to the rendered content once getStaticProps completes.

Part of #1328.

Contributor guide

Research direction
Examine the vinext prerender implementation to identify why pages under `/api ` are incorrectly treated as API routes and why lazy catchall pages never resolve. Fix the API route detection to match only `pages/api/` and ensure fallback resolves after `getStaticProps`.
Tech stack
typescriptvitenextjs
Domain
backend
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.
Clear
Prerequisites
Next.jsVitePages Router
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50