Add section about migrating from next/image to next/future/image
#39270
Conversation
| ```css | ||
| max-width: 100%; | ||
| height: auto; | ||
| **intrinsic: next/image** |
There was a problem hiding this comment.
Should we use a table to organize the legacy/future comparison a bit more together similar to our page config allowed/not allowed table? https://github.com/vercel/next.js/blob/canary/errors/invalid-page-config.md
There was a problem hiding this comment.
Tables don't render nicely right now. For example https://nextjs.org/docs/api-reference/next/image#layout
| <td> | ||
|
|
||
| ```jsx | ||
| import Image from 'next/image' |
There was a problem hiding this comment.
This looks a bit strange when live.
Thoughts on just doing section headers to for each and just including the after code snippet with a comment in there?
// Replaces default usage of `next/image`
import Image from 'next/future/image'
import img from '../img.png'
const css = { maxWidth: '100%', height: 'auto' }
export default function Page() {
return <Image src={img} style={css} />
}
There was a problem hiding this comment.
Thoughts on just doing section headers to for each and just including the after code snippet with a comment in there?
Sounds good to me, would be curious if tables would render better if we hid the sidebar 🤔
This expands on the previous PR #38978 with a section on migrating