next/image failed to use the custom loader when using next dev --turbo

[mhughdo]

Link to the code that reproduces this issue

https://github.com/mhughdo/nextjs-bug-reproduction-app

To Reproduce

Run pnpm dev

Current vs. Expected behavior

Current:

• Next is showing the missing loader prop error when using the custom loader

Expected behavior: - The image could be loaded properly

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
 Arch: arm64
 Platform: darwin
 Version: Darwin Kernel Version 23.0.0
Binaries:
 node: v20.8.0
 pnpm: 8.13.1
Packages
 next: Next.js 14.0.5-canary.34 (turbo)
 react: 18.2.0
 react-dom: 18.2.0

Which area(s) are affected? (Select all that apply)

Image optimization (next/image, next/legacy/image), Turbopack (--turbo)

Additional context

No response

_PACK-2190

[Bahlaouane-Hamza]

I can confirm, i think this is related to 946c9c5

This introduce

// @ts-ignore - This is replaced by webpack alias
import defaultLoader from 'next/dist/shared/lib/image-loader'

Which is supposed to replaced by Webpack here
https://github.com/vercel/next.js/blob/canary/packages/next/src/build/create-compiler-aliases.ts#L114

I believe the equivalent webpack aliasing mecanic for Turbo is here https://github.com/vercel/next.js/blob/canary/packages/next-swc/crates/next-core/src/next_import_map.rs, but this does not contain any ref to image-loader

You can manage the aliasing yourself in the meantime using experimental.turbo.resolveAlias like so:

diff --git a/next.config.js b/next.config.js
index 897e72e..63c4d84 100644
--- a/next.config.js
+++ b/next.config.js
@@ -14,6 +14,13 @@ const nextConfig = {
     path: 'https://hughdo-dev.imgix.net/',
     loaderFile: './loader/index.ts',
   },
+  experimental: {
+    turbo: {
+      resolveAlias: {
+        "next/dist/shared/lib/image-loader": './loader/index.ts',
+      },
+    },
+  },
 }

 module.exports = nextConfig

@styfle any guidance on this please ?

[mhughdo]

@Bahlaouane-Hamza

Thank you for your solution. I can confirm that it fixed the problem for now.

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.