Great.
I also agree that if this was automatic, it would have been great, but there are pros/cons there. Some frameworks like Next.js don't *yet* have a clear adapter interface, so we detect it automatically. Having to configure things gives you much more explicit control but is more manual.
I love netlify have been using netlify to host my blog since most of its life and this wasn’t a netlify issue, this was my dissatisfaction with Astro not netlify, but I’m so glad you decided to help anyway, thanks
We're also good friends with the Astro team, so I'd try to get to the bottom of it when I can :-)
Also noting to @mk.gg - the CPU usage for image optimization (without the adapter) is pretty intense on my local machine, perhaps there's a way to throttle that.
My issue wasn’t exactly the fact that I had to add an adapter manually, the issue is that I have to use 3rd party(netlify’s) image optimizations when it’s supposed to be done by the SSG(like gatsby-plugin-image does) without running out of memory
Comments
I also agree that if this was automatic, it would have been great, but there are pros/cons there. Some frameworks like Next.js don't *yet* have a clear adapter interface, so we detect it automatically. Having to configure things gives you much more explicit control but is more manual.
Also noting to @mk.gg - the CPU usage for image optimization (without the adapter) is pretty intense on my local machine, perhaps there's a way to throttle that.