You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encountered an issue regarding the Strapi Starter Next Blog, but is most likely relevant to all Strapi starters and templates.
When the blur placeholder prop is added to the Next Image component in frontend\components\image.js, the optimizations that Next does relating to the image get nullified. This is the case, because the optimized and unoptimized version of the image are then both fetched. This can be witnessed in the Network tab of the developer tools.
For clarification, if these two lines of code are added the raw and optimized version of the Strapi image are requested:
I encountered an issue regarding the Strapi Starter Next Blog, but is most likely relevant to all Strapi starters and templates.
When the blur placeholder prop is added to the Next Image component in
frontend\components\image.js
, the optimizations that Next does relating to the image get nullified. This is the case, because the optimized and unoptimized version of the image are then both fetched. This can be witnessed in the Network tab of the developer tools.For clarification, if these two lines of code are added the raw and optimized version of the Strapi image are requested:
Full code of
frontend\components\image.js
:The text was updated successfully, but these errors were encountered: