-
Notifications
You must be signed in to change notification settings - Fork 56
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
No source mapping for async functions #92
Comments
Yes, I'm seeing this occasionally as well. Not sure it has something to do with the async test case. Can you try and run the tests as a website with |
Chrome on OSX
Firefox
Safari
|
try mocha's |
I'm running into this. |
I don't even know if the browser bundle of mocha supports |
I suppose this happens because errors in async functions are caught with the window To anyone who wants to look into this, I'd suggest to check what the raw format of a global error looks like in different browsers / phantom and then fix that RegExp in source-mapper. |
When hitting assertions in asynchronous code, we don't get unhelpful callstacks, instead just getting the line number from bundle.js
Result:
The text was updated successfully, but these errors were encountered: