-
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:Runtime
is:issue state:open label:Runtime
Search results
allowedDevOrigins causes a hydration mismatch (display:contents metadata boundary) on every full page load
RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.Status: Open.#98604 In vercel/next.js;cachedNavigations session-shell prerender races an async cacheHandlers.default get: E1163 on every dynamic render with deterministic keys
Cache ComponentsRelated to the `cacheComponents`, `useCache`, or `ppr` experimental flags.Related to the `cacheComponents`, `useCache`, or `ppr` experimental flags.RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.Status: Open.#98543 In vercel/next.js;[next-rspack] NextExternalsPlugin wrongly externalizes transpilePackages direct dependencies on Windows + pnpm (dev only, pages router)
RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.Status: Open.#98505 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;NextJS Edge runtime process polyfill for process.getBuiltinModule (an optional API) throws when importing js-bson
RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.Status: Open.cookies() inside after() returns pre-mutation values in a Route Handler
Route HandlersRelated to Route Handlers.Related to Route Handlers.RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.Status: Open.#98222 In vercel/next.js;Dev server retains ~90 MB per edit of a Server Component and consumes memory without bounds
ReactRelated to React.Related to React.RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.Status: Open.#98221 In vercel/next.js;experimental.inlineCss embeds the full stylesheet 3x per page — getGlobalErrorStyles re-inlines it with an empty injectedCSS set
CSSRelated to CSS.Related to CSS.RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.Status: Open.#98110 In vercel/next.js;Turbopack browser runtime: first-wins module registration installs the wrong factory when a module id is emitted with different bodies in different chunks
Pages RouterRelated to Pages Router.Related to Pages Router.RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.Status: Open.#98099 In vercel/next.js;experimental.inlineCss: stylesheet duplicated twice in the flight payload — _full.segment.rsc carries the CSS text 2x (3x total per prerendered page)
CSSRelated to CSS.Related to CSS.RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.Status: Open.#98079 In vercel/next.js;runtimeServerDeploymentId: prerendered flight payloads pin the build-time deployment id — serving a build under a different deployment id causes an infinite MPA reload loop
RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.Status: Open.#98078 In vercel/next.js;Concurrent FileSystemCache writes can corrupt fetch-cache JSON on a shared filesystem
RuntimeRelated to Node.js or Edge Runtime with Next.js.Related to Node.js or Edge Runtime with Next.js.Status: Open.