o functions deployed
This deploy did not include any functions. Learn more about Netlify Functions.
and, as you can see in the link, gatsbyImage() images give 404 (please do mind that not all images on this page are newer style gatsbyImage(), only vehicle images are. Content images are the old syntax gatsbyImageData() and will and show always build in buildtime ignoring imageCDN)
When i revert my project back to Gatsby 5.11 with gatsby-plugin-netlify and running the same GATSBY_CLOUD_IMAGE_CDN=true, this results in:
1 function deployed
We have deployed 1 function. Visit your Functions for more information.
As it turns out, Netlify has no “image CDN”, so you should not configure that to true in later versions (I suppose in earlier versions, it happens automatically), but the example you quote of it working is us dynamically transforming images with a lambda function instead.
I don’t know if I understand your awnser.
yes, Gatsby 5.11 with gatsby-plugin-netlify and GATSBY_CLOUD_IMAGE_CDN=true skips buildtime image creation, creates a lambda function to transform images on the edge, thats what is called ImageCDN.
example: https://64fb601ec5082e000883ccce--sweet-cupcake-d43613.netlify.app/
1 function deployed
We have deployed 1 function. Visit your Functions for more information.
Gatsby 5.12 dropped gatsby-plugin-netlify in favor of gatsby-adapter-netlify, GATSBY_CLOUD_IMAGE_CDN=true skips buildtime image creation, does not create the lambda function and therefor; the images return a 404.
example: https://64fb252be454280db8b2bbc2--sweet-cupcake-d43613.netlify.app/
o functions deployed
This deploy did not include any functions. Learn more about Netlify Functions.
