Open karlhorky opened 2 years ago
Or is the recommendation now to switch to next/image
as mentioned here:
Currently next/image has bugs with:
Possibly changes needed to get next-images to work are not such a large lift (current code is like 20 lines) and probably not much is needed to make it work in later versions of next.
Only problem I've encountered so far with next-images is with dynamicAssetPrefix
(if I turn this off my previous set up does work). So I say we at least dig in to find out what exactly are the problems with next-images that make it not work in version 12/13 (by the way my next-images config works fine in v12.2.x but not 12.3.4) so I doubt that version 11 is actually not working unless for some edge case that I didn't try.
Hi there, thanks for
next-images
! 🙌Now that Next.js 13 is officially released, would you consider supporting this new version?
(maybe also version 11 and 12 as mentioned in the issues below)
87
73