Using getImage in content collection loader throwing error on build in Astro v5

[An0nymusA]

Astro Info

Astro                    v5.1.8
Node                     v20.9.0
System                   Windows (x64)
Package Manager          npm
Output                   static
Adapter                  @astrojs/cloudflare
Integrations             copyStyles
                         generate-sitemap
                         generate-redirects
                         generate-favicons
                         copy-files
                         @astrojs/tailwind
                         @astrojs/preact
                         @playform/inline
                         @inox-tools/runtime-logger

If this issue only occurs in one browser, which browser is a problem?

No response

Describe the Bug

I have a getImage function inside my content collection loader to optimize images found in the collection. It worked in v4, but after upgrading to v5 it stopped working and throws this errror when building. (For context when used outside the content config it works)

InvalidImageService: There was an error loading the configured image service. Please see the stack trace for more information.
    at eval (E:/Documents/LocalGarbage/bartender-headless/node_modules/astro/dist/assets/internal.js:24:21)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async getConfiguredImageService (E:/Documents/LocalGarbage/bartender-headless/node_modules/astro/dist/assets/internal.js:20:34)
    at async getImage (E:/Documents/LocalGarbage/bartender-headless/node_modules/astro/dist/assets/internal.js:54:19)
    at async getImage (astro:assets:27:42) {
  loc: undefined,
  title: 'Error while loading image service.',
  hint: undefined,
  frame: undefined,
  type: 'AstroError',
  cause: Error: Vite module runner has been closed.
      at SSRCompatModuleRunner.getModuleInformation (file:///E:/Documents/LocalGarbage/bartender-headless/node_modules/astro/node_modules/vite/dist/node/module-runner.js:1188:13)
      at SSRCompatModuleRunner.cachedModule (file:///E:/Documents/LocalGarbage/bartender-headless/node_modules/astro/node_modules/vite/dist/node/module-runner.js:1178:21)
      at request (file:///E:/Documents/LocalGarbage/bartender-headless/node_modules/astro/node_modules/vite/dist/node/module-runner.js:1214:99)
      at dynamicRequest (file:///E:/Documents/LocalGarbage/bartender-headless/node_modules/astro/node_modules/vite/dist/node/module-runner.js:1216:124)
      at getConfiguredImageService (E:/Documents/LocalGarbage/bartender-headless/node_modules/astro/dist/assets/internal.js:20:40)
      at getImage (E:/Documents/LocalGarbage/bartender-headless/node_modules/astro/dist/assets/internal.js:54:25)
      at getImage (astro:assets:27:82)
      at loader (E:/Documents/LocalGarbage/bartender-headless/src/content.config.ts:67:39)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async simpleLoader (file:///E:/Documents/LocalGarbage/bartender-headless/node_modules/astro/dist/content/content-layer.js:268:16)
      at async Promise.all (index 3)
      at async #doSync (file:///E:/Documents/LocalGarbage/bartender-headless/node_modules/astro/dist/content/content-layer.js:175:5)
      at async file:///E:/Documents/LocalGarbage/bartender-headless/node_modules/p-queue/dist/index.js:230:36
}

Example: https://stackblitz.com/edit/github-n5ufjfep?file=src%2Fcontent.config.ts

What's the expected result?

To get an optimized image

Link to Minimal Reproducible Example

https://stackblitz.com/edit/github-n5ufjfep

Participation

• I am willing to submit a pull request for this issue.

[ascorbic]

I'm honestly a little surprised this ever worked! getImage was never expected to work in loaders, but it seems it does accidentally work in some scenarios. It's not that it was meant to be forbidden - it's not what it was designed for, and so is likely to cause problems even if it did work. Your best bet is to use getImage when you query the collection instead.