Open rH4rtinger opened 2 months ago
@rH4rtinger Our extension is also using minified js files in the production code for client (extension) and server (language server) par. For getting code coverage performed by vscode-extension-tester, we exclude them and only performed webpack on the js files used in webviews. You may want to see the webpack.conig.ts file that we are using. Could you implement a similar change to your webpack configuration file?
I can not modify my webpack config file in the way you do, because my extension consists from just one entry point. If I remove this entry point, then nothing will build.
I created a example project with the coverage results checked in.
If you check out the extension.js coverage, you can see that the results that I get are not really informative.
Describe the bug
I have a extension that is built via webpack.
When I try to get the coverage, I needed to give the option
-u
, otherwise I would not get any coverage result.The result I got was from my minified file built by webpack. This is not good for getting any coverage result, because you can not read any information from a file, that has just one line.
script in
package.json
:This is the start of my coverage report. Note that there are no more lines.
I tried switching my mode for building to
development
. This produced no coverage.Expected behavior
-u
flag.development
flag from webpack.Steps to reproduce
Logs
Operating System
Windows 10
Visual Studio Code
1.92.0
vscode-extension-tester
8.5.0
NodeJS
22.4.0
npm
10.8.1