next-config
6 traces
- Next.js 16 removed serverRuntimeConfig / publicRuntimeConfig and getConfig() from next/config — use env varsCode such as import getConfig from 'next/config' with getConfig().publicRuntimeConfig.apiUrl, or serverRuntimeConfig/publicRuntimeConfig keys in next.config, stops working after upgrading to Next.js 16. Fix: To read a…
- `experimental.ppr` has been merged into `experimental.cacheComponents`: Next.js 16 removed ppr/dynamicIO/useCache flagsA next.config copied from Next.js 15 tutorials (experimental: { ppr: 'incremental' }, experimental: { dynamicIO: true }, experimental: { useCache: true }) or a route that exports export const experimentalppr = true…
- Next.js 16: local next/image src with a query string (/logo.png?v=2) is rejected unless images.localPatterns allows itAfter upgrading to Next.js 16, cache-busted local images such as <Image src="/assets/photo.png?v=1" /> or /api/images/123?t=... Fix: After, allowing any query string under a path (omit search): Or allow exactly one…
- Next.js 16: next/image quality={90} silently becomes 75 — images.qualities now defaults to [75]After upgrading to Next.js 16, <Image quality={90} /> (or 50, 100…) looks the same as the default quality. Fix: List every quality you use: Then <Image quality={90} ...
- ERROR: This build is using Turbopack, with a `webpack` config and no `turbopack` config. (Next.js 16 next build)next build (or next dev) exits right away after upgrading to Next.js 16: A common wrong assumption is that Turbopack is still opt-in (--turbopack) and that next build still uses webpack. Fix: Pick one option: 1.
- Next.js 16: next/image returns 400 for images on private/local IPs — set images.dangerouslyAllowLocalIPA self-hosted Next.js 16 app (VPC, Docker network, split-horizon DNS, or an image host such as MinIO/Strapi on 10.x/192.168.x/localhost) gets 400 Bad Request from /next/image for remote images that worked on 15, even…