This also adds Python-2.0 to the list of accepted licenses. Lastly, it fixes a bug where the package.json files were incorrectly reordered. For the `exports` of a particular package, the order that the entrypoints are defined in is crucial. Therefore, we should not alter the order of entrypoints and instead maintain the originally defined ordering. We can use an `OrderedDict` to ensure that Python always loads the JSON files in the same order. DISABLE_THIRD_PARTY_CHECK=NPM update R=jacktfranklin@chromium.org Bug: none Change-Id: I5a309782de6015edea6ba3b502aa0db1f008d973 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2692909 Auto-Submit: Tim van der Lippe <tvanderlippe@chromium.org> Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org>
content-type
Create and parse HTTP Content-Type header according to RFC 7231
Installation
$ npm install content-type
API
var contentType = require('content-type')
contentType.parse(string)
var obj = contentType.parse('image/svg+xml; charset=utf-8')
Parse a content type string. This will return an object with the following
properties (examples are shown for the string 'image/svg+xml; charset=utf-8'):
-
type: The media type (the type and subtype, always lower case). Example:'image/svg+xml' -
parameters: An object of the parameters in the media type (name of parameter always lower case). Example:{charset: 'utf-8'}
Throws a TypeError if the string is missing or invalid.
contentType.parse(req)
var obj = contentType.parse(req)
Parse the content-type header from the given req. Short-cut for
contentType.parse(req.headers['content-type']).
Throws a TypeError if the Content-Type header is missing or invalid.
contentType.parse(res)
var obj = contentType.parse(res)
Parse the content-type header set on the given res. Short-cut for
contentType.parse(res.getHeader('content-type')).
Throws a TypeError if the Content-Type header is missing or invalid.
contentType.format(obj)
var str = contentType.format({type: 'image/svg+xml'})
Format an object into a content type string. This will return a string of the
content type for the given object with the following properties (examples are
shown that produce the string 'image/svg+xml; charset=utf-8'):
-
type: The media type (will be lower-cased). Example:'image/svg+xml' -
parameters: An object of the parameters in the media type (name of the parameter will be lower-cased). Example:{charset: 'utf-8'}
Throws a TypeError if the object contains an invalid type or parameter names.