Support charset in decode_data_url
#137
Merged
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.
rolldown's sourcemap implementation outputs inline source maps that start withdata:application/json;charset=utf-8;base64,, which would currently fail with the implementation ofdecode_data_url. Obviously, this seems like a slippery slope to implementing the entirety of the mime type spec, but hopefully this is about the extent of the variance in most common sourcemap generators.Github code search for
data:application/json;charset=utf-8Github code search for
data:application/json;charset=utf8