next/future/image

[colbyfayock]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
next-cloudinary	✅ Ready (Inspect)	Visit Preview	Oct 27, 2022 at 8:25PM (UTC)

[colbyfayock]

https://github.com/all-contributors please add @colbyfayock for code, doc, example

[colbyfayock]

@all-contributors please add @colbyfayock for code, doc, example

[allcontributors]

@colbyfayock

I've put up a pull request to add @colbyfayock! 🎉

[nucliweb]

What do you think about defining a prop to use next/future/image or next/image.
There are a lot of legacy projects with the next/image still.

[colbyfayock]

so, my thinking here is because of the way i'm wrapping the component, CldImage doesn't necessarily care what version the component is using

i have to test to confirm this, but nothing i'm doing is using anything that's changed, it all gets passed through, and i add stuff on top by making modifications to the src based on additional Cloudinary-related props

[nucliweb]

Yes, but if I want to use CldImage component but I use the Next.js version lower than 12.3 (with support to next/future/image) I will have a crash, right?

[colbyfayock]

i need to test that theory and see (or if you want to help out with that). its my understanding next/future/image will be updated to next/image in the release, it won't maintain /future so it will treat it the same, it will just have a different API

i have Next.js as a peer dependency, so there shoudln't be any version requirements iif im not mistaken

[nucliweb]

@colbyfayock FYI, Next.js 13 will be remove /future from the component name.

[github-actions]

🎉 This PR is included in version 0.4.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀