Skip to content
This repository has been archived by the owner on May 10, 2021. It is now read-only.

Support for Next/Image #70

Closed
lokmanm opened this issue Nov 2, 2020 · 1 comment · Fixed by #138
Closed

Support for Next/Image #70

lokmanm opened this issue Nov 2, 2020 · 1 comment · Fixed by #138

Comments

@lokmanm
Copy link

lokmanm commented Nov 2, 2020

Hello everyone, as you might already know Next now has a new Image Component and I was thinking if its possible to support it on Netlify ?

At our company we are very tight with the whole Netlify ecosystem, we use Netlify CMS and we use Netlify for publishing almost everything that we have & we cant afford to switch to Vercel just for this component.

The new Image component is very good but sadly I found out that they only support that on Vercel hosted sites, We are not very familiar with next-on-netlify thus we can't do a PR, but we are willing to help out during the PR with testing, docs, or whatever is needed.

Thank you

@etrepum
Copy link
Contributor

etrepum commented Nov 10, 2020

The absolute simplest thing you could do today would be to use imgix, akamai, or cloudinary as an image optimizing CDN (these are the ones supported by next/image). Yeah, it's not provided by Netlify, but you also don't have to change how anything is deployed.

The Netlify options don't seem very low friction. There is Netlify Large Media Transformations but it requires that you set up Git LFS for those assets and it would also require a patch to next.js to support that URL scheme.

It would be possible to deploy the new next.js image optimizer (/_next/image) as a Netlify Function, but the performance would not be very good because it uses the local disk to persist the cache so every request would be a cache miss and have to do the optimization each time.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants