a2b781fafe
### What? In #57062, a deprecation warning was added for usage of `nextConfig.images.domains`. This warning was erroneously showing up for users that had an `assetPrefix` configured. ### Why? When an `assetPrefix` specified, during assignment for `nextConfig` default values, we push to `nextConfig.images.domains` so that the user doesn't receive errors about hostnames not being configured ([Original PR](https://github.com/vercel/next.js/pull/29307)). This means people are indirectly being opted into a deprecated config, and receiving a warning because of it. ### How? We no longer push any defaults to the deprecated config option. Additionally, this applies the same defaults handling to `remotePatterns,` as otherwise people using this new config will run into the same issue as this block was originally intended to fix. Fixes #58074 |
||
---|---|---|
.. | ||
app-dir | ||
asset-prefix | ||
base-path | ||
both-basepath-trailingslash | ||
default | ||
export-config | ||
image-from-node-modules | ||
invalid-image-import | ||
loader-config | ||
loader-config-default-loader-with-file | ||
loader-config-edge-runtime | ||
middleware | ||
react-virtualized | ||
svgo-webpack | ||
trailing-slash | ||
typescript | ||
unicode | ||
unoptimized |