feat!: split scopes and ranges in SourceMapJson and remove EMPTY tag - #19
Merged
Merged
Conversation
szuend
added this pull request to stack #20
September 28, 2026 09:25
Base automatically changed from
pr-2-range-definition-source-scope-idx
to
main
September 28, 2026 09:35
Per tc39/ecma426#266 and tc39/ecma426#274, original scopes and generated ranges are now stored in separate 'scopes' ((string | null)[]) and 'ranges' (string) fields in the source map JSON rather than a single combined string. Each source's scopes entry is decoded with a fresh ScopeState, root scopes within the same source keep relative line/column offsets instead of resetting to 0, and missing scope information is represented by 'null' in the 'scopes' array instead of Tag.EMPTY ('A').
szuend
force-pushed
the
pr-3-split-scopes-and-ranges
branch
from
September 28, 2026 09:35
c3e6b3c to
b3142d0
Compare
OrKoN
approved these changes
Sep 28, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Per tc39/ecma426#266 and tc39/ecma426#274, original scopes and generated ranges are now stored in separate 'scopes' ((string | null)[]) and 'ranges' (string) fields in the source map JSON rather than a single combined string. Each source's scopes entry is decoded with a fresh ScopeState, root scopes within the same source keep relative line/column offsets instead of resetting to 0, and missing scope information is represented by 'null' in the 'scopes' array instead of Tag.EMPTY ('A').