Fix inline source-map support with charset in the data url #65
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.
Inline source map prefix should contain an charset:
data:application/json;charset:utf-8;base64,
This is the case with the last releases of browserify for instance.
This fix make inline source map detection more flexible to support
this kind of data url (not only with charset) and use a regexp instead
of a static string:
/^data:application\/json[^,]+base64,/
(I didn’t push the generated
browser-source-map-support.js
with thisPR, do you want me to ?)