-
Notifications
You must be signed in to change notification settings - Fork 31.9k
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open label:Performance
is:issue state:open label:Performance
Search results
after(): a task that never settles retains the request's async context for the life of the server
AfterRelated to the after() function.Related to the after() function.PerformanceAnything with regards to Next.js performance.Anything with regards to Next.js performance.Route HandlersRelated to Route Handlers.Related to Route Handlers.Status: Open.#98561 In vercel/next.js;next dev overrides container-aware V8 heap limit using host memory
PerformanceAnything with regards to Next.js performance.Anything with regards to Next.js performance.RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.Status: Open.#98381 In vercel/next.js;Turbopack panics in ModuleGraphImportTracer: 'entered unreachable code: there must be a path to a root' (module_graph/mod.rs:750)
CSSRelated to CSS.Related to CSS.PerformanceAnything with regards to Next.js performance.Anything with regards to Next.js performance.TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.Status: Open.#98205 In vercel/next.js;resolveMetadata loses AsyncLocalStorage context across async boundary during cold static prerendering (InvariantError E1068)
MetadataRelated to Next.js' Metadata API.Related to Next.js' Metadata API.PerformanceAnything with regards to Next.js performance.Anything with regards to Next.js performance.TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.Status: Open.#98200 In vercel/next.js;Turbopack build saturates 4 GB and stalls or OOMs
PerformanceAnything with regards to Next.js performance.Anything with regards to Next.js performance.TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.Status: Open.#97802 In vercel/next.js;Turbopack:
productionBrowserSourceMaps: truedisables dead-import elimination forcompiler.define-foldedtypeofguardsPerformanceAnything with regards to Next.js performance.Anything with regards to Next.js performance.TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.Status: Open.#97791 In vercel/next.js;Turbopack: next build deadlocks at 0% CPU — content-hashed chunk paths + mutually-referencing async chunks form an await cycle
PerformanceAnything with regards to Next.js performance.Anything with regards to Next.js performance.TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.Status: Open.#97399 In vercel/next.js;Next 16.3 regression: htmlLimitedBots matching browser UAs makes cacheable PPR pages private/no-store
Dynamic RoutesRelated to dynamic routes.Related to dynamic routes.MetadataRelated to Next.js' Metadata API.Related to Next.js' Metadata API.PerformanceAnything with regards to Next.js performance.Anything with regards to Next.js performance.RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.Status: Open.#96594 In vercel/next.js;next build can wait far beyond the built-in telemetry timeout when a caller signal is provided
PerformanceAnything with regards to Next.js performance.Anything with regards to Next.js performance.RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.Status: Open.#96291 In vercel/next.js;App Router: chunk <script> tags get no fetchpriority and Chrome's LowPriorityAsyncScriptExecution delays their evaluation — hydration render storm (~30k commits) on cross-site assetPrefix CDNs
PerformanceAnything with regards to Next.js performance.Anything with regards to Next.js performance.RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.Status: Open.#96202 In vercel/next.js;experimental.webVitalsAttribution has no effect on useReportWebVitals
PerformanceAnything with regards to Next.js performance.Anything with regards to Next.js performance.Status: Open.next build workers strip --max-old-space-size (isolatedMemory) and expose no memory control — page-data collection OOMs, bundler-independent
PerformanceAnything with regards to Next.js performance.Anything with regards to Next.js performance.TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.WebpackRelated to Webpack with Next.js.Related to Webpack with Next.js.Status: Open.#95745 In vercel/next.js;