Fix bug when invalid JSON passed as source map#1195
Merged
jakubpawlowicz merged 2 commits intoJan 25, 2022
Conversation
Collaborator
|
Thanks @shpingalet007 for fixing this issue, let me merge it and release as a bugfix later today. |
jakubpawlowicz
pushed a commit
that referenced
this pull request
Jan 26, 2022
* Handling empty source-maps * Test files created
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.
Fix the #1194 issue when the source map file for some reason can be empty. In this case handle this situation to avoid
JSON.parse()an empty string.