-
Notifications
You must be signed in to change notification settings - Fork 93
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
Issue with NextJS 10 #219
Comments
Hello there! First, thank's you for the work made here. I hope to add more context to this issue. The problemI am trying to bump my project to nextJS 10.
Indeed, in I think I ran into this because nextJS 10 bring SolutionsFix on the version 2This was my chosen solution. I opened a pull request for it. It is minimal, and all checks are OK. Upgrade to the version 3 canaryI tried this but ran into #195 |
Thanks 😅 |
Is this still useful with the new version? |
With the alpha 3 version, I encounter #195. Version 3 will be a good solution when stable 😃 |
@SalahAdDin It is, to import from modules |
@ScreamZ I mean, is this page still relevant with the new NextJS image api? |
Yeah, because NextJS don't do the same things exactly, they are optimizing other things |
is there any tutorial about that? |
As said in the NextJS documentation
For my personal use case, I need to build time URL generation at least to fill product metadata. @ScreamZ , from my point of view, NextJS Image component and this library do the same things, but not at the same time. This still has drawbacks. EDIT: It also works with a custom server as specified on the loaders page section. |
@guillaumeLamanda I'm not sure to understand, we must use vercel to work with the new image component of next.js ? When i read the next.js documentation and when i saw this library, I was thinking about wich solution is better for my current project. So, if you can help me to take the good decision i will be very happy 😄 |
I do not think so, the documentation states the built-in optimization is used by default. |
@durchanek thank's I missed the So @JbPons, the |
Thanks for the clarification |
I first implemented the workaround proposed here before realizing there is a better way recommended to fix this using the 'responsive' property in next.config.js. Reference: #206 |
Have a look at this thread vercel/next.js#18946
The text was updated successfully, but these errors were encountered: