- Explain how defaults work and what the default values are.
- Mention quality on the basic page

This records new configs being leveraged

This does two things:

- Rename `iconSizes` to `imageSizes`.
- Give priority to `imageSizes` regardless of `deviceSizes` as a means to opt-out of the srcset behavior.

Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

Co-authored-by: NTim Neutkens <timneutkens@me.com>

Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
Co-authored-by: NJoe Haddad <joe.haddad@zeit.co>

This is a follow-up to https://github.com/vercel/next.js/pull/18067 adding an example for i18n routing

x-ref: https://github.com/vercel/next.js/pull/17370

Might be easier for some users to see a whole app set up with it

Follow-up to https://github.com/vercel/next.js/pull/18067 this adds the manifest item for the new docs

This is a follow-up to https://github.com/vercel/next.js/pull/17755 which adds support for returning `notFound` to `getServerSideProps` also

* Fix test without expect for redirects from getStaticProps/getServerSideProps

* Fix browser back issue of redirects from getServerSideProps / getStaticProps

This removes the `unstable_` prefix to prepare for stabilizing the feature

This separates the `next.config.js` property `images.sizes` into to properties: `images.deviceSizes` and `images.iconSizes`.

The purpose is for images that are not intended to take up the majority of the viewport.


Related to #18122 

Add missing links in the documentation

This adds checks to ensure that less than 50 domain and size items are configured and no sizes are less than 0 or greater than 10,000 

x-ref: https://github.com/vercel/next.js/issues/18122Co-authored-by: NSteven <steven@ceriously.com>

There was a bug when the user defines a width on the Image component, but a larger size image is requested.

This is because the browser uses the `srcset` to decide which image size to request and we had the srcset basically hardcoded.

This PR fixes the behavior so that the `srcset` will never be larger than the `width` defined on the component.

It also fixes a bug where the preload srcset did not match the img srcset.

- Related to #18147 
- Related to #18122

* Add next/image default loader errors

* Add domains check

* Apply suggestions from PR

* Update test

We currently always accept requests to the new `/_next/image` endpoint, even when it should not be used.

Instead, we should check to see if the default loader is used as a signal to enable this API.

Other loaders (such as cloudinary) will not go through the Next.js API so there is no need to expose this, instead we 404.

- Analogous to https://github.com/vercel/vercel/pull/5321
- Related to #18122

This ensures a custom `/404` page with `getStaticProps` works correctly when leveraging the new `unstable_notFound` support in `getStaticProps`

Closes: https://github.com/vercel/next.js/issues/18196
x-ref: https://github.com/vercel/next.js/pull/17755

* Adds React 17 as a peer dependency

Solves on of the issues in https://github.com/vercel/next.js/issues/18122

Co-authored-by: NLee Robinson <me@leerob.io>
Co-authored-by: NTim Neutkens <timneutkens@me.com>

For many users refactoring from `<img>` to `<Image>`, we can often support their properties as-is.
The exception was width/height.

This PR allows the `<Image>` component to accept strings for `width` and `height` just like `<img>`.

Related to #18122