Turbopack loader ignores resource query on aliased imports

[sam3d]

Link to the code that reproduces this issue

https://github.com/sam3d/turbopack-resource-query-repro

To Reproduce

Start the application usng pnpm dev (turbopack is enabled by default)

Current vs. Expected behavior

I'd expect both a relative and aliased import to behave the same way:

import isHello from "./example.txt?hello";
import shouldBeWorld from "@/app/example.txt?world";

export default async function Page() {
  return (
    <ul>
      <li>isHello: {isHello}</li>
      <li>shouldBeWorld: {shouldBeWorld}</li>
    </ul>
  );
}

However they do not, as the resource query is not passed to the loader when accessing with @/app/...:

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.0.0: Mon Aug 12 20:51:54 PDT 2024; root:xnu-11215.1.10~2/RELEASE_ARM64_T6000
  Available memory (MB): 65536
  Available CPU cores: 10
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 9.12.3
Relevant Packages:
  next: 15.0.4-canary.4 // Latest available version is detected (15.0.4-canary.4).
  eslint-config-next: 15.0.4-canary.4
  react: 19.0.0-rc-66855b96-20241106
  react-dom: 19.0.0-rc-66855b96-20241106
  typescript: 5.6.3
Next.js Config:
  output: N/A

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

Turbopack

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

next dev (local)

Additional context

No response

[JesseKoldewijn]

I believe there's already a couple of issues present regarding the resource imports in TurboPack. So that part of your issue might be a slight duplicate of these existing issues.