cloudflare/vinext

Build: `require.context` returns empty result (Webpack-only API)

Closed

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

require.context('./parent', true, /\.js$/) should expose the matched file list at runtime; vinext returns an empty string. The Webpack-only require.context API is not transformed by the Vite/Rolldown build into a directory-import equivalent.

require.context() returns empty string at runtime

Estimated Impact

~1 test failures across the deploy suite.

Affected Test Suites

  • test/e2e/app-dir/require-context/require-context.test.ts

Recommendation

  1. Reproduce first in vinext's own test suite. Add a require.context() call in a Pages Router page and assert it returns the expected file list.

  2. Add a transform. Implement a Vite plugin that rewrites require.context(...) into Vite's import.meta.glob(...) so the matched file list is available at runtime.

Contributor guide

Research direction
Implement a Vite plugin that transforms `require.context('./parent', true, /\.js$/)` into Vite's `import.meta.glob` equivalent, ensuring the matched file list is available at runtime. Test the plugin with a basic Pages Router page.
Tech stack
javascripttypescriptvitenodejs
Domain
build systemdeveloper experiencetooling
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
Node.jsViteJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70