next-image-to-legacy-image: This codemod will safely and automatically rename next/image imports to next/legacy/image to maintain the same behavior as Next.js 12.There are two codemods to help you migrate to the new Image Component: Starting in Next.js 13, this new behavior is now the default for next/image. These improvements included less client-side JavaScript, easier ways to extend and style images, better accessibility, and native browser lazy loading. Next.js 12 introduced many improvements to the Image Component with a temporary import: next/future/image. You can continue using pages with new features that work in both directories, such as the updated Image component, Link component, Script component, and Font optimization. However, upgrading to Next.js 13 does not require using the new app directory. Next.js 13 introduces a new app directory with new features and conventions. The target configuration property has been removed and superseded by Output File Tracing.
A codemod is available to automatically upgrade your code. Add the legacyBehavior prop to use the legacy behavior or remove the to upgrade. A codemod is available to safely and automatically rename your imports. The next/future/image import was renamed to next/image. The next/image import was renamed to next/legacy/image.The swcMinify configuration property was changed from false to true.The minimum React version has been bumped from 17.0.2 to 18.2.0.The minimum Node.js version has been bumped from 12.22.0 to 14.18.0, since 12.x has reached end-of-life.The Supported Browsers have been changed to drop Internet Explorer and target modern browsers.To update to Next.js version 13, run the following command using your preferred package manager: npm i or yarn add or pnpm up next react react-dom eslint-config-next -latest
0 kommentar(er)
