We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
14.2.1
https://github.com/scry/VueCoverage
clone the repo, yarn install, karma start.
Karma will break because of these lines in remap-istanbul.
remap-istanbul expects sourcemaps to have the "file" property, but vue-loader isn't setting it.
parser.js should be passing the file option to SourceMapGenerator, as per SourceMapGenerator docs.
Link to line in vue-loader.
parser.js skips the file property, which results in a map being exported without file specified.
This causes an issue specifically with remap-istanbul. I thought the bug was theirs for a while but it looks like it's a saner fix in vue-loader.
The text was updated successfully, but these errors were encountered:
I added a pull for reference. #1190 It's almost a one-liner.
Sorry, something went wrong.
Thanks for the PR!
No branches or pull requests
Uh oh!
There was an error while loading. Please reload this page.
Version
14.2.1
Reproduction link
https://github.com/scry/VueCoverage
Steps to reproduce
clone the repo, yarn install, karma start.
Karma will break because of these lines in remap-istanbul.
remap-istanbul expects sourcemaps to have the "file" property, but vue-loader isn't setting it.
What is expected?
parser.js should be passing the file option to SourceMapGenerator, as per SourceMapGenerator docs.
Link to line in vue-loader.
What is actually happening?
parser.js skips the file property, which results in a map being exported without file specified.
This causes an issue specifically with remap-istanbul. I thought the bug was theirs for a while but it looks like it's a saner fix in vue-loader.
The text was updated successfully, but these errors were encountered: