128 issues found — filter by difficulty, status, or repo
Cache component feature breaks Clerk sign-in route with unclear Suspense boundary requirements.
The issue involves runtime-specific behavior in a monorepo setup with unclear root causes.
Server code leaks to browser due to re-exporting pages.
CSS minification issue in an outdated Next.js version with unclear reproduction steps.
Metadata alternates URL generation appears incorrect but root cause is unclear.
Intermittent failure with large request bodies in middleware requires deep understanding of Next.js internals.
Browser-specific hydration failure due to turbopack runtime assumptions.
The issue involves understanding Next.js metadata and shared fetch behavior.
Cache poisoning issue during rapid test execution requires careful investigation of Next.js caching behavior.
CSS `:has()` rules are incorrectly applied due to `display: none` behavior.
The issue clearly identifies a bug in HMR handling of interception routes with a proposed fix.
Middleware tracing produces duplicate traces requiring careful instrumentation changes