Affected version
Reports that share this version, grouped in one feed.
Next.js provides a TypeScript language-service plugin that reports framework-specific diagnostics in the editor, but these diagnostics are not available when running `tsc` or any Next.js CLI command. This means CI type checking can miss Next.js-specific type errors (e.g., invalid metadata export types), leading to false confidence. A framework-aware CLI type check command (e.g., `next check`) should be added.
In Next.js 16.3.0, when a page contains links with different route shapes and a middleware rewrite maps some URLs to a different locale prefix, the client-side segment prefetch scheduler reuses the segment path from a previously processed link (e.g., the home route) for later links that are starved by the 4-request network cap. This results in 404 responses for the affected prefetch _rsc requests. Navigation still works due to fallback, but browser consoles are polluted with errors and E2E tests fail.
LangChain, LlamaIndex, and Pydantic
Pinecone, Chroma, Weaviate, Qdrant, and neighboring stores
Next.js, Supabase, and the surrounding app stack