-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does this support next/future/image? #24
Comments
Hi @robert-sperse, the new image api from Next.js is not yet supported. I will have a look at it |
This comment was marked as off-topic.
This comment was marked as off-topic.
Looks like |
Hi @elliott-w, Thanks for bringing awareness to their progress with the new Image component. Once they announce their next major version and more implementation details, I will reflect the changes here so that the syntax matches closely. |
Forgive my ignorance, but I can't see what further implementation details you'd need than those specified in the api reference here? |
Would be really nice if the future image is supported since it's a lot less 'hacky' than the old component with spans e.t.c. |
Hey, definitely, the new implementation is a lot simpler. I am on it to support the future image as well. |
Changing is fairly easy If you can't wait you could use my fork :)
|
I just published v0.17.0, which supports the next/future/image component. Please let me know whether it works as expected, as I had to implement the blurry placeholder image using an SVG filter since the wrapper that had overflow:hidden set (which limits the blur to not extend over the image borders) is gone in the next/future/image component. |
If not, can you add support for it. https://nextjs.org/docs/api-reference/next/future/image
The text was updated successfully, but these errors were encountered: