Tim van der Lippe
6d109a9d45
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>
Browser-friendly inheritance fully compatible with standard node.js inherits.
This package exports standard inherits from node.js util module in
node environment, but also provides alternative browser-friendly
implementation through browser
field. Alternative
implementation is a literal copy of standard one located in standalone
module to avoid requiring of util. It also has a shim for old
browsers with no Object.create support.
While keeping you sure you are using standard inherits
implementation in node.js environment, it allows bundlers such as
browserify to not
include full util package to your client code if all you need is
just inherits function. It worth, because browser shim for util
package is large and inherits is often the single function you need
from it.
It's recommended to use this package instead of
require('util').inherits for any code that has chances to be used
not only in node.js but in browser too.
usage
var inherits = require('inherits');
// then use exactly as the standard one
note on version ~1.0
Version ~1.0 had completely different motivation and is not compatible
neither with 2.0 nor with standard node.js inherits.
If you are using version ~1.0 and planning to switch to ~2.0, be careful:
- new version uses
super_instead ofsuperfor referencing superclass - new version overwrites current prototype while old one preserves any existing fields on it