Prototype implementation of Source Maps v4 #1
Conversation
This file contains 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
Source Maps v4 standard proposal is an addendum to source maps to improve post-hoc debugging and analysis of call stacks. This proposal is being put forward in [https://github.com/MicrosoftEdge/MSEdgeExplainers/pull/538](Microsoft Edge) and is designed to enable an analysis of stack traces to reconstruct an unminified stack trace. To do so, two additional fields are added to the source maps output: - `scopeNames` - `scopes` The latter field behaves similarly to the existing `mappings` field. The former list are names that should be displayed for a given function once it is determined to be responsible. The format of the `scopes` field is a Base64 VLQ with 6 fields, which are, in order: - Source file index - Source line (relative offset) - Source character (relative offset) - End line (relative offset, should always be positive) - End character (relative offset) - Index into `scopeNames` (This first commit does not implement the VLQ encoding; rather, all number values are directly passed in and are neither relative nor are they encoded as VLQs).
- Method declarations - Constructor - Class property accessors - Improved arrow scope - Arrow scope call expressions - Lambda class property - Base64 VLQ encoding of `scopes` property Fixed a bug that allowed some code to execute in v3 passes.
Several tests related to tsc --init / tsc watch were breaking as a result of the new option. These tests have been rebaselined or adjusted as needed to accommodate the new `sourceMapVersion` setting.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request is for me to do a self-code-review.
Source Maps v4 standard proposal is an addendum to source maps to
improve post-hoc debugging and analysis of call stacks. This proposal is
being put forward in
[https://github.com/MicrosoftEdge/MSEdgeExplainers/pull/538](Microsoft Edge)
and is designed to enable an analysis of stack traces to reconstruct an
unminified stack trace.
To do so, two additional fields are added to the source maps output:
scopeNamesscopesThe latter field behaves similarly to the existing
mappingsfield. Theformer list are names that should be displayed for a given function once
it is determined to be responsible. The format of the
scopesfield isa Base64 VLQ with 6 fields, which are, in order:
scopeNames(This first commit does not implement the VLQ encoding; rather, all
number values are directly passed in and are neither relative nor are
they encoded as VLQs).
Fixes #