[coverage] Fix non source-mapped coverage issue #2383
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The coverage was not correct since there was no source-map between the babel-compiled output and the original source code. This led to incorrect coverage reports (issue first found by @ftoromanoff) since those were based on the babel-compiled output.
This PR fixes on our unit tests:
babel-register-esm
one.--experimental-loader
options, we now usenode:module.register()
(not supported bybabel-register-esm
).[BABEL] Note: The code generator has deoptimised the styling of [...]/node_modules/[...] as it exceeds the max of 500KB.
warnings, since we now ignore compilation of modules innode_modules
(not done bybabel-register-ems
but previously done by@babel/register
).Further info: