[Turbopack] load wrong assetPrefix (it uses http://localhost:3000/http://cdn.com)

[thasuohm]

Link to the code that reproduces this issue

https://github.com/thasuohm/nextjs-reproduce/tree/turbopack/wrong-assetprefix-load

To Reproduce

1. Create a simple next js app
2. add assetPrefix in next.config.js
3. run in dev mode with --turbo

Current vs. Expected behavior

AS: It loads assetPrefix with localhost as a prefix

EXPECTED: it loads correctly assetPrefix when run with --turbo

Verify canary release

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

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
Binaries:
  Node: 20.10.0
  npm: N/A
  Yarn: N/A
  pnpm: 7.25.0
Relevant Packages:
  next: 14.1.1-canary.1
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A

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

App Router, Turbopack (--turbo)

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

next dev (local)

Additional context

This has happened Since version 14.0.3

_PACK-2282

[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.