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

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.