Share chunks between multiple ESM Workers

Describe the bug

When bundling WebWorkers in the es format, all the modules imported by the worker are inlined inside the worker chunk and no import syntax is used.

In the following reproduction, there's the following setup:

2 script outputs: main and seconday
One module validation that is imported by main.ts and secondary.ts

By analyzing the build output, 3 chunks are emitted:

validation-[hash].js, which includes the code shared between both main and secondary outputs.
main-[hash].js, the code for the main output.
secondary-[hash].js, the code for the secondary output.

For WebWorkers in ESM format, the same behaviour is expected: instead of inlining the imported modules in the worker's chunk, the worker should import from another common chunk.

Specifically, in the reproduction, I expect the shared chunk to contain the contents of isBool (from validation.ts) and comlink's expose and that both are imported by the workers (FancyWorker1 just needs to import expose).

To better see the problem, minification is already disabled.

Reproduction

https://stackblitz.com/edit/vue3-vite-typescript-starter-rayp8m

Steps to reproduce

Run npm ci && npm run build in the StackBlitz project
Go to the dist folder and observe the output of the main thread's chunks (remember, called main and secondary)
Observe the emitted chunks for the worker and how both have Comlink's expose inlined (with FancyWorker1 inlining isBool too!)

System Info

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:
    @vitejs/plugin-vue: 5.1.3 => 5.1.3 
    vite: 5.4.3 => 5.4.3

Used Package Manager

npm

Logs

No response

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] 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.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

vitejs / vite