sourceMappingURL with non-base64 data URI not supported. about convert-source-map HOT 9 CLOSED

@jdalton I guess you need to find that time to dig in. I'm just the random guy who links to specs.

from convert-source-map.

Ok so it turns out the vscode issue isn't related to convert-source-map though it couldn't hurt to patch this. I haven't forgotten I'm on the hook : )

from convert-source-map.

#48 (comment)

Let’s close this until somebody needs it.

Guess that time is now.

from convert-source-map.

Worth noting devs tools in Electron and at least Chrome 61 with node --inspect
work with these data:application/json style sourceMappingURLs.

from convert-source-map.

Not entirely sure what the fix should be .. hoping someone will provide a PR with a fix that doesn't break any tests to make sure all is still backwards compat.

from convert-source-map.

Easy. Just follow RFC 2397:

The [data] URLs are of the form:

data:[<mediatype>][;base64],<data>

The is an Internet media type specification (with optional parameters.) The appearance of ";base64" means that the data is encoded as base64. Without ";base64", the data (as a sequence of octets) is represented using ASCII encoding for octets inside the range of safe URL characters and using the standard %xx hex encoding of URLs for octets outside that range. If is omitted, it defaults to text/plain;charset=US-ASCII. As a shorthand, "text/plain" can be omitted but the charset parameter supplied.

from convert-source-map.

Easy. Just follow RFC 2397:

Would love a PR @lydell as I'm not gonna be able to address ATM due to time constraints :)

from convert-source-map.

Or maybe @jdalton wants to pick it up since this is affecting VSCode ...
LMK if so, I made you collab in the mean time

from convert-source-map.

Rock 🤘 !

If @lydell wants to lead, I can review. Else I can find some time to dig in.

from convert-source-map.