development mode and build mode instrument result is different in SSR project

[sunnywanggit]

Describe the bug

development mode and build mode instrument result is different in SSR project

development mode：

build mode：

Reproduction

https://github.com/sunnywanggit/coverage

Steps to reproduce

No response

System Info

System:
    OS: Windows 10 10.0.22000
    CPU: (16) x64 AMD Ryzen 7 5800H with Radeon Graphics         
    Memory: 1.17 GB / 15.86 GB
  Binaries:
    Node: 16.14.0 - D:\dachui\install\node\node.EXE
    Yarn: 1.22.15 - D:\dachui\install\node\yarn.CMD
    npm: 8.3.1 - D:\dachui\install\node\npm.CMD
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (108.0.1462.76)
    Internet Explorer: 11.0.22000.120

Used Package Manager

yarn

Logs

No response

Validations

• Read the Contributing Guidelines.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a vite-plugin-istanbul 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.
• The provided reproduction is a minimal reproducible example of the bug.

[iFaxity]

Hi @sunnywanggit,

I'll look at this and see if i can find a cause.

Might be an error when the instrumenter gets the ID for the file as the filenames are different in build and in serve mode.

[sunnywanggit]

@iFaxity Thanks a lot

[iFaxity]

After looking into this there could be a fix to manipulate the module ID to remove the query parameters after the file path. However not sure what consequence this can have on other setups.

I will try this approach as there seem to not be a fix using Vite/Rollups own API. as getFileName is not valid for the modules and getModuleInfo does not yield anything interesting. The query parameters is only there for the Vue plugin to know how to parse the file, nothing else it seems.

[iFaxity]

@sunnywanggit Please try the solution release in the version v4.0.0-rc.2.

If it is ok i will publish it along a release in the future, but for now it is in a release candidate to try out the feature

[vduggen]

@sunnywanggit Please try the solution release in the version v4.0.0-rc.2.

If it is ok i will publish it along a release in the future, but for now it is in a release candidate to try out the feature

I tested it on version v4.0.0-rc.2 and it's working fine, I was scared because in the beginning it was the cache hahaha, thanks a lot for the project it helped a lot! I felt some difficulties because it doesn't have much content, but I want to see if I contribute to the community.

PS: I'm Brazilian and I'm using google translator, sorry if the translation is bad

[iFaxity]

@vduggen No worries I understand you just fine 😊.

Great that the solution worked, I will publish it in a stable release very soon.

Thanks for contributing 👍.

[github-actions]

🎉 This issue has been resolved in version 4.0.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀