You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am getting a coverage report using PTI. However I am running into many issues which I am failing to find decent answers for.
I am only going to pick one issue for now.
I am getting a coverage report and can render it using nyc. It also appears to be taking the source map into account. However the resulting report is rendering files names incorrectly.
The file names are close but incorrect. The report is showing the file extension as jsx.js/tsx.js/ts.js instead of just jsx/tsx/ts.
Would anyone have any idea on what could be going on here? I am using Webpack and can provide the config for that if that might help.
However, I am assuming, Puppeteer utilizes the source map and the file name ends with its original extension after the coverage data is retrieved. This could obviously be anything before a transpiler is ran.
I'm not sure what the exact purpose of this method is other than remapping the path to another. But it seems to me that expecting the extension to always be ".js" is not entirely correct.
Unless some other part of the code requires ".js", I think the easiest thing would be to just remove the ".js" strings from the following lines 60, 63, 69, 72.
I am getting a coverage report using PTI. However I am running into many issues which I am failing to find decent answers for.
I am only going to pick one issue for now.
I am getting a coverage report and can render it using nyc. It also appears to be taking the source map into account. However the resulting report is rendering files names incorrectly.
The file names are close but incorrect. The report is showing the file extension as jsx.js/tsx.js/ts.js instead of just jsx/tsx/ts.
Would anyone have any idea on what could be going on here? I am using Webpack and can provide the config for that if that might help.
Here is a snippet of the report from the console.
The text was updated successfully, but these errors were encountered: