`@sveltejs/enhanced-img` 0.9.0 causes build to slow down 10x

[ahkelly]

Describe the bug

Upgrading from @sveltejs/enhanced-img@0.8.5 to @sveltejs/enhanced-img@0.9.2 causes the build process to progress extremely slowly (literally from around 1 minute to 14 minutes) on a site that has hundreds of images all using <enhanced:img>. The build process especially hangs at node_modules/svelte/src/internal/client/warnings.js for several minutes.

I have tried several times now with recent sveltekit updates and have to always roll back to 0.8.5

Reproduction

Really wish I knew how to setup a repo for this, how do I install enhanced-img in sveltelab or other place with hundreds of jpg's. I expect this issue to get closed as a result but not sure how else to highlight that there is a bug in the latest update.

Logs

System Info

Ubuntu 22, Node 24, npm 11
svelte@5.45.5
@sveltejs/kit@2.49.1
@sveltejs/adapter-node@5.4.0

Severity

blocking an upgrade

Additional Information

No response

[beeb]

Confirmed here as well, from 25s to 8 minutes. The problem appeared in 0.9.0.

[elliott-with-the-longest-name-on-github]

@beeb How sure are you that it happened precisely in 0.9.0 (as opposed to .1 or .2)? I only ask because the only change in that version was upgrading the vite-imagetools version we're using from 8.x to 9.x, which would suggest an upstream issue.

[beeb]

@beeb How sure are you that it happened precisely in 0.9.0 (as opposed to .1 or .2)? I only ask because the only change in that version was upgrading the vite-imagetools version we're using from 8.x to 9.x, which would suggest an upstream issue.

I tested it locally by pinning the dependency to 0.9.0 and building my project. I tested with 0.8.5 and didn't observe the slowdown.

[elliott-with-the-longest-name-on-github]

Perfect, thank you!

[ahkelly]

I can confirm it was 0.9.0 series as I tested that version in addition to 0.9.2.

[benmccann]

darn. I'm guessing JonasKruckenberg/imagetools#841 is the culprit

I changed where the .clone() was happening so that it happens more often now. I'm not sure if that's an expensive operation, but it could be the culprit. It was wrong before and not safe (see JonasKruckenberg/imagetools#723), so I don't think we can simply change it back, but that could be one thing to investigate. It's probably either that or somehow the way I stopped two transform jobs from running in parallel has held things up

[benmccann]

Can you test if 0.10.2 fixes this issue? It fixes some issues with caching, but I don't have a way to reproduce this issue to see if it's been solved

[ajdexter]

Just tested.. My build times at 0.8.0 are around ~1minute, ~33m on 0.9.0-0.10.0.

Wahoo! Looks like 0.10.2 is coming it at the ~1 minute mark as well. Thanks @benmccann

[elliott-with-the-longest-name-on-github]

Awesome, thank you! Thanks @benmccann too!