After Vite 4.2 upgrade, the manifest.json file cannot be generated after using sharedwork

[AlexStacker]

Describe the bug

After Vite 4.2 upgrade, the manifest.json file cannot be generated after using sharedwork

Only show so few assets lines:

{
  "sharedwork.js": {
    "file": "assets/sharedwork-9c4decac.js",
    "isEntry": true,
    "src": "sharedwork.js"
  }
}

It seems that Rollup has change the method finalizeAdditionalAsset.
rollup/rollup@75c5113#diff-016e61f8e680c4307db5ae6252b432289d01f2d31802ce47892a9b832cd6abc2R398-R400

Reproduction

https://stackblitz.com/edit/vitejs-vite-jb9po3?file=main.js&terminal=dev

Steps to reproduce

After run build, check the manifest.json file in the dist directory

System Info

System:
    OS: macOS 12.6.3
    CPU: (10) x64 Apple M1 Pro
    Memory: 36.00 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 14.19.3 - ~/.nvm/versions/node/v14.19.3/bin/node
    npm: 6.14.17 - ~/.nvm/versions/node/v14.19.3/bin/npm
  Browsers:
    Chrome: 110.0.5481.177
    Edge: 111.0.1661.54
    Firefox: 111.0.1
    Safari: 16.4
  npmPackages:
    vite: ^4.2.1 => 4.2.1

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.

[stackblitz]

Start a new pull request in StackBlitz Codeflow.

• vitejs-vite-jb9po3 (Open reproduction)

[vinayakkulkarni]

It seems there is an issue with Workers with latest version of vite, reference to another Web Worker issue – #12611 (comment)

[sapphi-red]

Duplicate of #10190

[sun0day]

It seems that this has been fixed in the main.

[sapphi-red]

@sun0day It seems there's a race condition.

[AlexStacker]

It seems that this has been fixed in the main.

Hey @sun0day I tested with the latest 4.3.0-beta.1 still exist. When I was debugging, I found that the emitFile in the manifest.ts is triggered the output of manifest.json twice. Once it output the content of the file we saw below:

{
    "sharedwork.js": {
      "file": "assets/sharedwork-9c4decac.js",
      "isEntry": true,
      "src": "sharedwork.js"
    }
}

and the second time it output the content of assets, but it was not written to the file. So should it output 2 manifest.json files or should it be combined into one file for output.