Range mappings: encoding/decoding support#45
Merged
jridgewell merged 6 commits intojridgewell:mainfrom Feb 28, 2026
Merged
Conversation
jridgewell
force-pushed
the
range-mappings-decode
branch
from
f7c49f2 to
01a4f69
Compare
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.
I'm currently looking into adding range mappings support for these packages. This is an initial PR that just adds encoding/decoding handling. Similar to the scopes code, I've added additional range mappings functions in a separate file rather than in the core code.
The first commit adds code for unsigned VLQ. I think this is needed for updated scopes support anyway so maybe you've written a version of this already, in which case I'd be happy to adapt the PR to that.
I'm also working on support in trace-mapping, etc. that will build on this PR.