5e112c062e
Changes ESLint warning message to still encourage usage of `next/image` for the best experience, but also denoting that optimization could come with incurred costs. ## Feature - [x] Documentation added - [x] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) ## Documentation / Examples - [x] Make sure the linting passes by running `pnpm build && pnpm lint` - [x] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) --------- Co-authored-by: Steven Tey <stevensteel97@gmail.com> Co-authored-by: Steven <steven@ceriously.com> |
||
---|---|---|
.. | ||
base-directories | ||
config-core-web-vitals | ||
config-in-package-json | ||
custom-config | ||
custom-directories | ||
empty-directory | ||
eslint-cache | ||
eslint-cache-custom-dir | ||
eslint-ignore | ||
file-linting | ||
first-time-setup | ||
ignore-during-builds | ||
invalid-eslint-version | ||
max-warnings | ||
mjs-cjs-linting | ||
no-config/pages | ||
no-eslint-plugin | ||
plugin-core-web-vitals-config | ||
plugin-recommended-config | ||
test | ||
with-typescript |