Stack traces for input source maps #273
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Compute correct stack traces if the test file itself was already compiled before ava was run, provided it contains a source map pragma.
source-map-support works fine if the map is already an object.
Member
| Looks good to me. @jamestalmage ? |
Contributor
| 👍
Bah! I meant to fix that. Thanks @novemberborn. |
jamestalmage added a commit that referenced this pull request Nov 26, 2015
…cemaps Stack traces for input source maps
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
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.
Follow-up to #262, as requested by @jamestalmage:
Note the second commit which is unrelated to input source map support but removes an unnecessary stringification of the transpiled source map.