Updated next version from 12.3.1 to 14.2.3
The react and react-dom were updated to their corresponding compatible versions as well.
Changes
Starting with Next.js 13, <Link> renders as <a>, so attempting to use <a> as a child is invalid. The new-link codemod automatically upgraded previous version of Next.js to the new <Link> usage. All link elements of the form <Link><a id="link">Home</a></Link> were changed to <Link id="link">Home</Link>. [Reference Link]
Starting in Next.js 13, the next/image component has undergone some major changes. These include removing the layout prop in favor of style or className to add support for canonical style prop. The next-image-to-legacy-image codemod automatically changed next/image imports to next/legacy/image. [Reference Link]
images.domains was deprecated and replaced by images.remotePatterns in next.config.js.
Possible Changes
next/legacy/image can be upgraded to the new next/image once a stable version of the codemod for it has been developed.
Overview
Updated
nextversion from12.3.1to14.2.3Thereactandreact-domwere updated to their corresponding compatible versions as well.Changes
<Link>renders as<a>, so attempting to use<a>as a child is invalid. Thenew-linkcodemod automatically upgraded previous version of Next.js to the new<Link>usage. All link elements of the form<Link><a id="link">Home</a></Link>were changed to<Link id="link">Home</Link>. [Reference Link]next/imagecomponent has undergone some major changes. These include removing thelayoutprop in favor ofstyleorclassNameto add support for canonicalstyleprop. The next-image-to-legacy-image codemod automatically changednext/imageimports tonext/legacy/image. [Reference Link]images.domainswas deprecated and replaced byimages.remotePatternsinnext.config.js.Possible Changes
next/legacy/imagecan be upgraded to the newnext/imageonce a stable version of the codemod for it has been developed.