Issue Station
Sign In
Tools hereToolbox

nextjs - ✅(Solved) Fix turbopack: missing "loader" prop on window using src dir with loaderFile [1 pull requests, 4 comments, 4 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#85726•Fetched 2026-04-08 02:14:10
View on GitHub
Comments
4
Participants
4
Timeline
13
Reactions
0
Author
H01001000H01001000
Participants
github-actions[bot]github-actions[bot]H01001000H01001000kangw3nkangw3nmischnicmischnic
Timeline (top)
commented ×4labeled ×3closed ×1cross-referenced ×1

Fix Action

Fixed

PR fix notes

PR #85765: WIP: test imageLoader on windows

Description (problem / solution / changelog)

Related to #85726

Changed files

  • .github/workflows/build_and_test.yml (modified, +4/-2)

Code Example

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 65447
  Available CPU cores: 32
Binaries:
  Node: 22.13.0
  npm: 9.8.1
  Yarn: 4.4.1
  pnpm: 8.10.5
Relevant Packages:
  next: 16.0.1
  eslint-config-next: 15.1.2
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2
Next.js Config:
  output: standalone
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/H01001000/reproduction-app

To Reproduce

  1. use src dir
  2. Set images, loader: custom and provide loaderFile (as usual) make sure its in src
  3. Use a Next/Image
  4. run next dev or next build

Current vs. Expected behavior

only trigger on using src dir.

On windows pc, using turbopack (default) will cause the bug, switch to webpack the bug gone Also tested on macbook m4 pro, turbopack work as expected

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 65447
  Available CPU cores: 32
Binaries:
  Node: 22.13.0
  npm: 9.8.1
  Yarn: 4.4.1
  pnpm: 8.10.5
Relevant Packages:
  next: 16.0.1
  eslint-config-next: 15.1.2
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2
Next.js Config:
  output: standalone

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

Turbopack

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

next dev (local)

Additional context

Tried on next@16, 16.0.1, 16.0.2-canary.5, all will leads to the bug

extent analysis

TL;DR

Switching to Webpack instead of Turbopack resolves the issue on Windows PCs.

Guidance

  • The issue seems to be specific to Turbopack on Windows, as switching to Webpack resolves the problem.
  • To verify, try running next dev or next build with Webpack instead of Turbopack.
  • The fact that the issue occurs on Windows but not on a MacBook M4 Pro suggests a potential platform-specific bug in Turbopack.
  • Try updating Next.js to a newer version (if available) to see if the issue is resolved, although the user has already tried version 16.0.2-canary.5 without success.

Example

No code snippet is provided as the issue seems to be related to the build tool (Turbopack) rather than the code itself.

Notes

The issue might be specific to the combination of Next.js version 16.0.1, Turbopack, and Windows 10 Pro. Further investigation would be needed to determine the root cause.

Recommendation

Apply workaround: Switch to Webpack instead of Turbopack, as it resolves the issue on Windows PCs. This is a temporary solution until the root cause is identified and fixed in Turbopack.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#integration issue#index setup#retrieval issue#search optimization#API routing

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - ✅(Solved) Fix turbopack: missing "loader" prop on window using src dir with loaderFile [1 pull requests, 4 comments, 4 participants]