Severity
Reports at this severity, newest stored first.
In Next.js dev mode with output: export, dynamic routes with parameters requiring URL encoding (e.g., spaces) intermittently fail with a missing param error, while production builds work correctly. The bug depends on navigation order and is caused by inconsistent handling of encoded vs. decoded parameters.
Next.js does not pass identifierPrefix to React Flight renderer, causing useId() counters to reset per request and collide across client-side navigations when shared layouts persist.
router.refresh() unexpectedly scrolls the page to the top after a history.replaceState call changes the search params. The root cause is a hard-coded ScrollBehavior.Default in the tree-mismatch retry path (serverPatchReducer) and in the non-redirect server action path (serverActionReducer), which overrides the NoScroll intent of the original refresh.
When a LangGraph interrupt occurs in an MCP tool call that returns InputRequiredResult, resuming the graph causes MCPAdapter to issue a fresh initial tool call without the original request_state. If the server generates a new input-request key for each initial call, the adapter validates the saved answer against the new key and raises ValueError before sending the answer to the server.
In LangChain's retry middleware, calculate_delay applies the max_delay cap before adding ±25% jitter, allowing the final delay to reach up to max_delay * 1.25. This causes unexpected longer waits than configured.
When ripgrep is not installed, FilesystemFileSearchMiddleware falls back to in-process Python regex search on model-controlled patterns, leading to catastrophic backtracking and denial of service.
When env is not provided to ShellToolMiddleware, _create_resources coerces None to an empty dict, causing host and Codex shell sessions to lose parent environment variables such as PATH, proxy settings, and credentials.
When partial prerendering (PPR) is enabled, runtime-rendered pages with no postponed state are written to the file-system cache without an .rsc file, but the read path requires .rsc for such entries, leading to cache MISS on every request after eviction from memory.
In Next.js production builds, when a Server Action writes a cookie and calls revalidatePath, and the page segment has an async layout and a loading.js boundary, the resulting transition can get stuck with suspendedLanes=512 and pingedLanes=0, causing the UI to never update. This is a stochastic bug affecting versions 16.2.x and 16.3.x.
ChatDeepSeek's message serialization omits `reasoning_content` from AIMessage.additional_kwargs, causing DeepSeek API 400 errors in multi-turn tool-calling conversations when the model requires the previous reasoning content to be passed back.
The ChatGPT device login helper in langchain-openai sends form-encoded data to an endpoint that expects JSON, causing HTTP 400. Additionally, the polling and token exchange steps do not match OpenAI's current device authorization flow, making the feature completely inoperative.
Next.js build with Turbopack fails when encountering a named @container rule (e.g., @container scroll-content) that does not include a condition, because the bundled lightningcss version lacks support for named container queries (scroll-state). This causes 'Unexpected end of input' errors during CSS parsing, breaking builds for projects that rely on such CSS (e.g., nhsuk-frontend).
When using next/image with a relative src that returns a 302 redirect to an external image, the built-in image optimizer does not follow the redirect and returns a 500 Internal Server Error, while a native <img> displays correctly.
The Edge Runtime process polyfill in Next.js defines process.getBuiltinModule as a throwing stub, violating Node's optional API contract. Packages such as js-bson that use feature detection (e.g., `if (globalThis.process?.getBuiltinModule)`) call the stub and trigger a runtime error, causing 500 errors in edge routes.
In Route Handlers, calling cookies() inside after() returns the inbound cookie snapshot instead of the mutated values because the mutable cookie jar is not synchronized before after() switches the work unit phase.
Next.js dev server retains ~90 MB per edit of a Server Component due to unbounded growth of Node's generatedSourceMapCache and React's fakeFunctionCache. Inline data URL source maps and line/column-dependent keys cause permanent cache entries, leading to OOM crashes.
Next.js dev server using rspack panics and aborts when error overlay or browser log forwarding requests original stack frames during a rebuild, due to stale compilation handle aliasing the in-progress compilation.
In Next.js dev, when a prerendered page is activated while the HMR WebSocket is still in CONNECTING state, the client enters an infinite reconnect loop. This prevents page hydration and floods the server with repeated /_next/hmr upgrade requests.
In Next.js Pages Router, during a shallow navigation, Router.getRouteInfo() may return a cached { __appRouter: true } prefetch marker instead of actual route info, leading to undefined Component and pageProps, crashing _app and preventing navigation.
Client-side navigation through a proxy that responds with a 308 redirect preserves the previous page's scroll position, leaving the new page scrolled down instead of at the top.
A before_model middleware hook configured with can_jump_to=["model"] that returns {"jump_to":"model"} crashes create_agent at runtime with KeyError because the conditional edge path map omits the hook's own node name, even though the router resolves "model" to it.
When middleware.ts exists, Next.js normalizes _next/data URLs before config redirects run, causing redirects to match internal data requests and return props from the wrong page. This breaks client-side navigation, while the absence of middleware avoids the issue.
Clicking Pricing in the nav from the homepage causes a full app crash (black page) because of a ChunkLoadError. The root cause is two Next.js apps (www and docs) sharing the same origin but having different deployment IDs, causing prefetched docs chunks to be requested from the wrong asset prefix. Webpack caches the chunk rejection, and when the Pricing route later requests the same shared chunk ID, the cached failure is replayed, leading to an uncaught error. The global-error chunk also 404s, preventing any error UI.
The `_generate` method uses `self.pipeline.task in "translation"` instead of an equality or prefix check, causing valid transformers translation tasks like `translation_en_to_fr` to raise ValueError. It also incorrectly matches empty string.
split_module mixes group indices and compacted module positions; empty groups cause off-by-one leading to out-of-bounds panic in module_fragments/graph.rs:746.
Next.js 16.3.x treats dynamic metadata routes with `generateStaticParams` as static metadata files, collapsing `app/[lang]/sitemap.ts` to `/-/sitemap.xml` and dropping per-locale sitemaps.
Reading `AIMessage.content_blocks` for a message with a non-standard Anthropic content block containing an `index` key silently deletes that key from the original `message.content` because the fallback branch pops `index` from the same dict object stored in the message. This also affects `model_provider="bedrock"` via bedrock.py importing the same function.
MarkdownHeaderTextSplitter corrupts chunk content by applying line.strip() and str.isprintable() filtering, which removes tabs, NBSP, and leading whitespace inside fenced code blocks, causing silent data loss during text splitting.
Passing an empty array to an 'in' filter in the PostgREST query builder produces invalid SQL (`in ()`), causing syntax errors. This affects vault helpers in Supabase Studio.
When using a Git worktree with node_modules symlinked to the primary checkout, running `next dev` with Turbopack triggers an internal panic: "Symlink node_modules could not be resolved: the symlink target leaves the filesystem root or its parent directory could not be resolved". The development server exits before serving the application. This affects parallel AI-assisted coding sessions that share dependencies across worktrees.