cloudflare/vinext

App Router: dynamically imported component renders fallback content instead of its actual content

Closed

#1,533 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 dynamically imported component should render its actual content (e.g. submit) but instead renders the loading/fallback text (e.g. Reload). The lazy component never resolves to its target output.

Expected component to render `submit`, rendered `Reload` (loading fallback)

Estimated Impact

~1 test failures across the deploy suite.

Affected Test Suites

  • test/e2e/app-dir/dynamic-import/dynamic-import.test.ts

Recommendation

  1. Reproduce first in vinext's own test suite. Add a next/dynamic import of a server/client component and assert the actual component text renders, not the loading fallback.

  2. Investigate why the lazy import never resolves. Check the dynamic chunk loading path: missing chunk URL, failed module evaluation, or Suspense never resolving.

Part of #1328.

Contributor guide

Research direction
Reproduce the issue locally using vinext's test suite, then trace the dynamic import resolution process in the vite plugin to identify why the fallback persists. Check chunk loading, module evaluation, and Suspense boundaries.
Tech stack
typescript
Domain
frontendbackend
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
GitNode.jsReactNext.js dynamic imports
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70