-
Notifications
You must be signed in to change notification settings - Fork 32.4k
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
React Compiler + Turbopack: lazy useState initializer throws TDZ when helper function declarations appear later in the same hook
SWCRelated to minification/transpilation in Next.js.Related to minification/transpilation in Next.js.TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.Status: Open.#98820 In vercel/next.js;Turbopack: nested next/dynamic gets no SSR stylesheet link, causing FOUC and layout shift (App Router)
CSSRelated to CSS.Related to CSS.Lazy LoadingRelated to Next.js Lazy Loading (e.g., next/dynamic or React.lazy).Related to Next.js Lazy Loading (e.g., next/dynamic or React.lazy).Module ResolutionModule resolution (CJS / ESM, module resolving).Module resolution (CJS / ESM, module resolving).TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.Status: Open.#98804 In vercel/next.js;Turbopack traces a pnpm hoisted-store alias without its target files, producing a dangling symlink that fails Vercel deploys with ENOENT
Module ResolutionModule resolution (CJS / ESM, module resolving).Module resolution (CJS / ESM, module resolving).OutputRelated to the the output configuration option.Related to the the output configuration option.TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.Status: Open.#98791 In vercel/next.js;[App Router] Critical layout CSS lacks preload link hints in document head
PerformanceAnything with regards to Next.js performance.Anything with regards to Next.js performance.Status: Open.#98756 In vercel/next.js;- Status: Open.#98750 In vercel/next.js;
[App Router] AI search crawlers and TelegramBot miss streaming metadata in Edge SSR
RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.Status: Open.#98748 In vercel/next.js;Partial Prefetching: generated routes return HTTP 500 on a cold custom-cache miss
Dynamic RoutesRelated to dynamic routes.Related to dynamic routes.RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.Status: Open.Searchparams not working when
cacheComponentsanddraftModeare enabledDraft ModeRelated to Draft Mode.Related to Draft Mode.Status: Open.#98720 In vercel/next.js;Instant-navigation validation reports a deliberate
redirect()from a layout as a validation failureError OverlayRelated to Next.js's error overlay.Related to Next.js's error overlay.RedirectsRelated to redirecting.Related to redirecting.Status: Open.#98711 In vercel/next.js;Turbopack dev: a route handler compiled after N pages costs ~16 MB × N (50 pages + 34 handlers → 29 GB); regressed in 16.3.0-canary.101
PerformanceAnything with regards to Next.js performance.Anything with regards to Next.js performance.Route HandlersRelated to Route Handlers.Related to Route Handlers.TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.Status: Open.#98707 In vercel/next.js;Turbopack: HMR stops updating after client navigation
Linking and NavigatingRelated to Next.js linking (e.g., <Link>) and navigation.Related to Next.js linking (e.g., <Link>) and navigation.TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.Status: Open.App Router: a <Link> clicked while its prefetch is in flight commits with no <title> (and can commit an empty segment) — Pending segment-cache entry is handed to React as a plain promise
Linking and NavigatingRelated to Next.js linking (e.g., <Link>) and navigation.Related to Next.js linking (e.g., <Link>) and navigation.Loading UI and StreamingRelated to loading UI (loading.tsx) and streaming.Related to loading UI (loading.tsx) and streaming.MetadataRelated to Next.js' Metadata API.Related to Next.js' Metadata API.Status: Open.#98684 In vercel/next.js;