ssrLoadModule returns an identical module for file urls with hash/search

[hi-ogawa]

Describe the bug

• related (but likely an independent issue) V3 breaks dynamic imports vitest-dev/vitest#7361

import { createServer } from "vite"

const fileUrl = new URL('./hello.js', import.meta.url);
{
  console.log('==== import ====');
  const mod1 = await import(fileUrl.href);
  const mod2 = await import(fileUrl.href + '#bustCache=1');
  const mod3 = await import(fileUrl.href + '?bustCache=1');
  console.log({ mod1, mod2, mod3 });
  console.log('[mod1 === mod2]', mod1 === mod2); // ===> false
  console.log('[mod1 === mod3]', mod1 === mod3); // ===> false
  console.log('[mod2 === mod3]', mod2 === mod3); // ===> false
}
{
  console.log('==== ViteDevServer.ssrLoadModule ====');
  const server = await createServer();
  const mod1 = await server.ssrLoadModule(fileUrl.href);
  const mod2 = await server.ssrLoadModule(fileUrl.href + '#bustCache=1');
  const mod3 = await server.ssrLoadModule(fileUrl.href + '?bustCache=1');
  console.log({ mod1, mod2, mod3 });
  console.log('[mod1 === mod2]', mod1 === mod2); // ===> true
  console.log('[mod1 === mod3]', mod1 === mod3); // ===> true
  console.log('[mod2 === mod3]', mod2 === mod3); // ===> true
  await server.close();
}

On Vite 5, file url was resolution failure. On Vite 6, it resolves but it looks like module identity is not considering hash/search. I only tested with ssrLoadModule entry case, but we should probably check other patterns too (static import, dynamic import, non-analyzable static import).

Reproduction

https://stackblitz.com/edit/vitest-dev-vitest-fchdscfz?file=repro.js

Steps to reproduce

• open a stackblitz link and run node repro.js

System Info

(stackblitz)

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    vite: latest => 6.0.11

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.