128 issues found — filter by difficulty, status, or repo
Handling OPTIONS requests incorrectly leads to 500 errors.
Safari-specific image handling regression in Next.js 16.2
The issue involves a regression in build ID generation affecting caching behavior.
Complex interaction between caching, metadata boundaries, and dynamic APIs causes server-side errors.
The issue involves runtime-specific behavior with cached functions in proxy.ts.
The warning logic inconsistently handles default exports in TypeScript components.
HMR breaks in Next.js 16.2 when using `manifest.ts`, but reports vary on root cause.
Mobile Safari event handling issue in Next.js 16.2.1 with unclear reproducibility.
The issue involves adding charset=utf-8 encoding to the Content-Type header for server actions.
Jest tests fail when using a custom image loader in Next.js 16.2.
The issue involves CSS `:target` selector behavior with Next.js `<Link>` component.
Next.js incorrectly handles runtime data in `generateMetadata` with `cacheComponents` enabled.