Affected version
Reports that share this version, grouped in one feed.
import.meta.glob with `../` patterns matches nothing in server components and app routes under Turbopack in Next.js 16.3 canary, while `./` patterns work. This breaks Vite-compatible path semantics for parent traversal.
When pageExtensions is configured as a single-element array (e.g., ['tsx']), Next.js webpack build fails with resolution errors for app dir routes. The issue is caused by the loader receiving pageExtensions as a plain string due to query string serialization, and the string branch in next-app-loader missing the leading dot for extensions.
With experimental.turbopackRustReactCompiler enabled, a shadowed local variable named like an HTML intrinsic (e.g., `table`) that is passed as a JSX prop causes the compiler to rename the lowercase `<table>` tag to `<table_0>`, leading to unrecognized element and hydration mismatch. The bug requires a specific combination: a `const table = useReactTable(...)`, a nested shadowing `const table`, passing the outer `table` as a prop, and an early return causing server/client structural difference.