-
-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
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
Unable to lookup source #837
Comments
Such local fix can help: in method NYC.prototype.instrumentAllFiles replace
with
|
JaKXz
added
help wanted
Great First Contribution
needs-investigation
and removed
wontfix
labels
Mar 7, 2019
Hi @golonikum sorry for the late reply! Would you like to submit a PR with your change? otherwise I will try to make some time for it but we welcome contributions :) It would be interesting to see if we can reproduce this in a failing test |
golonikum
pushed a commit
to golonikum/nyc
that referenced
this issue
Mar 7, 2019
golonikum
pushed a commit
to golonikum/nyc
that referenced
this issue
Mar 7, 2019
@golonikum I've merged your fix, thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
Content of the source files must be in the coverage report.
Observed Behavior
All report files contain the same excepion log:
Unable to lookup source: ...(ENOENT: no such file or directory, open '...')
Bonus Points! Code (or Repository) that Reproduces Issue
https://github.com/golonikum/testNycIssue
Open coverage/index.html and click on source.js link.
Forensic Information
Operating System: Microsoft Windows 10 Enterprise.
Environment Information: https://gist.github.com/golonikum/70385ce51a8bfe1b91947058d9f39197
The text was updated successfully, but these errors were encountered: