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.
Browsers have supported data: URLs in the fetch API for some time now. node-fetch will support them as well in its upcoming v3. The fetch API is the simplest and most reliable way to extract files from data: URLs.
Adding this support precludes a future "data:" matching prefix. This change should not break any existing HTTP(S) matchers, but since the "data:" scheme was previously stripped from URLs passed to matchers, this change will break any existing matchers for data: URLs that were full-string, "begin:", front-anchored regex/glob, or otherwise assumed that the "data:" scheme would be absent.
I did not include support for blob: URLs since they are opaque, less feasible to meaningfully test, and not supported by node-fetch.