mrs-toolbox-cli 10.0.10 → 10.0.12-489672f

package/npm-cache/_cacache/content-v2/sha512/{a8/07/ddabf33f1ebdc69bd953d88c3f1316f82ac73b0dbf7f7d45e302f079ec92b6e14292cf4cc92fc4ee1e8cf0211ca746117f1fd15431b9102615be868475be → 6a/09/6dd5bf2f22d8d1df7d0c7363c43e87342f9932f2182d9cec4e4c0dd10f0d7fdadfb5ec061ec849681a4482cb21390dba8f68652ee0759a6ef25a692019c4}

@@ -24415,7 +24415,7 @@
     "latest": "3.19.3",
     "backports": "2.8.29"
   },
-  "_rev": "924-bc28aa5a2d03bcdc",
+  "_rev": "931-cabc4f62821c2a24",
   "_id": "uglify-js",
   "readme": "UglifyJS 3\n==========\n\nUglifyJS is a JavaScript parser, minifier, compressor and beautifier toolkit.\n\n#### Note:\n- `uglify-js` supports JavaScript and most language features in ECMAScript.\n- For more exotic parts of ECMAScript, process your source file with transpilers\n  like [Babel](https://babeljs.io/) before passing onto `uglify-js`.\n- `uglify-js@3` has a simplified [API](#api-reference) and [CLI](#command-line-usage)\n  that is not backwards compatible with [`uglify-js@2`](https://github.com/mishoo/UglifyJS/tree/v2.x).\n\nInstall\n-------\n\nFirst make sure you have installed the latest version of [node.js](http://nodejs.org/)\n(You may need to restart your computer after this step).\n\nFrom NPM for use as a command line app:\n\n    npm install uglify-js -g\n\nFrom NPM for programmatic use:\n\n    npm install uglify-js\n\n# Command line usage\n\n    uglifyjs [input files] [options]\n\nUglifyJS can take multiple input files.  It's recommended that you pass the\ninput files first, then pass the options.  UglifyJS will parse input files\nin sequence and apply any compression options.  The files are parsed in the\nsame global scope, that is, a reference from a file to some\nvariable/function declared in another file will be matched properly.\n\nIf no input file is specified, UglifyJS will read from STDIN.\n\nIf you wish to pass your options before the input files, separate the two with\na double dash to prevent input files being used as option arguments:\n\n    uglifyjs --compress --mangle -- input.js\n\n### Command line options\n\n```\n    -h, --help                  Print usage information.\n                                `--help options` for details on available options.\n    -V, --version               Print version number.\n    -p, --parse <options>       Specify parser options:\n                                `acorn`  Use Acorn for parsing.\n                                `bare_returns`  Allow return outside of functions.\n                                                Useful when minifying CommonJS\n                                                modules and Userscripts that may\n                                                be anonymous function wrapped (IIFE)\n                                                by the .user.js engine `caller`.\n                                `spidermonkey`  Assume input files are SpiderMonkey\n                                                AST format (as JSON).\n    -c, --compress [options]    Enable compressor/specify compressor options:\n                                `pure_funcs`  List of functions that can be safely\n                                              removed when their return values are\n                                              not used.\n    -m, --mangle [options]      Mangle names/specify mangler options:\n                                `reserved`  List of names that should not be mangled.\n    --mangle-props [options]    Mangle properties/specify mangler options:\n                                `builtins`  Mangle property names that overlaps\n                                            with standard JavaScript globals.\n                                `debug`  Add debug prefix and suffix.\n                                `domprops`  Mangle property names that overlaps\n                                            with DOM properties.\n                                `keep_quoted`  Only mangle unquoted properties.\n                                `regex`  Only mangle matched property names.\n                                `reserved`  List of names that should not be mangled.\n    -b, --beautify [options]    Beautify output/specify output options:\n                                `beautify`  Enabled with `--beautify` by default.\n                                `preamble`  Preamble to prepend to the output. You\n                                            can use this to insert a comment, for\n                                            example for licensing information.\n                                            This will not be parsed, but the source\n                                            map will adjust for its presence.\n                                `quote_style`  Quote style:\n                                               0 - auto\n                                               1 - single\n                                               2 - double\n                                               3 - original\n                                `wrap_iife`  Wrap IIFEs in parentheses. Note: you may\n                                             want to disable `negate_iife` under\n                                             compressor options.\n    -O, --output-opts [options] Specify output options (`beautify` disabled by default).\n    -o, --output <file>         Output file path (default STDOUT). Specify `ast` or\n                                `spidermonkey` to write UglifyJS or SpiderMonkey AST\n                                as JSON to STDOUT respectively.\n    --annotations               Process and preserve comment annotations.\n                                (`/*@__PURE__*/` or `/*#__PURE__*/`)\n    --no-annotations            Ignore and discard comment annotations.\n    --comments [filter]         Preserve copyright comments in the output. By\n                                default this works like Google Closure, keeping\n                                JSDoc-style comments that contain \"@license\" or\n                                \"@preserve\". You can optionally pass one of the\n                                following arguments to this flag:\n                                - \"all\" to keep all comments\n                                - a valid JS RegExp like `/foo/` or `/^!/` to\n                                keep only matching comments.\n                                Note that currently not *all* comments can be\n                                kept when compression is on, because of dead\n                                code removal or cascading statements into\n                                sequences.\n    --config-file <file>        Read `minify()` options from JSON file.\n    -d, --define <expr>[=value] Global definitions.\n    -e, --enclose [arg[:value]] Embed everything in a big function, with configurable\n                                argument(s) & value(s).\n    --expression                Parse a single expression, rather than a program\n                                (for parsing JSON).\n    --ie                        Support non-standard Internet Explorer.\n                                Equivalent to setting `ie: true` in `minify()`\n                                for `compress`, `mangle` and `output` options.\n                                By default UglifyJS will not try to be IE-proof.\n    --keep-fargs                Do not mangle/drop function arguments.\n    --keep-fnames               Do not mangle/drop function names.  Useful for\n                                code relying on Function.prototype.name.\n    --module                    Process input as ES module (implies --toplevel)\n    --no-module                 Avoid optimizations which may alter runtime behavior\n                                under prior versions of JavaScript.\n    --name-cache <file>         File to hold mangled name mappings.\n    --self                      Build UglifyJS as a library (implies --wrap UglifyJS)\n    --source-map [options]      Enable source map/specify source map options:\n                                `base`  Path to compute relative paths from input files.\n                                `content`  Input source map, useful if you're compressing\n                                           JS that was generated from some other original\n                                           code. Specify \"inline\" if the source map is\n                                           included within the sources.\n                                `filename`  Filename and/or location of the output source\n                                            (sets `file` attribute in source map).\n                                `includeSources`  Pass this flag if you want to include\n                                                  the content of source files in the\n                                                  source map as sourcesContent property.\n                                `names` Include symbol names in the source map.\n                                `root`  Path to the original source to be included in\n                                        the source map.\n                                `url`  If specified, path to the source map to append in\n                                       `//# sourceMappingURL`.\n    --timings                   Display operations run time on STDERR.\n    --toplevel                  Compress and/or mangle variables in top level scope.\n    --v8                        Support non-standard Chrome & Node.js\n                                Equivalent to setting `v8: true` in `minify()`\n                                for `mangle` and `output` options.\n                                By default UglifyJS will not try to be v8-proof.\n    --verbose                   Print diagnostic messages.\n    --warn                      Print warning messages.\n    --webkit                    Support non-standard Safari/Webkit.\n                                Equivalent to setting `webkit: true` in `minify()`\n                                for `compress`, `mangle` and `output` options.\n                                By default UglifyJS will not try to be Safari-proof.\n    --wrap <name>               Embed everything in a big function, making the\n                                “exports” and “global” variables available. You\n                                need to pass an argument to this option to\n                                specify the name that your module will take\n                                when included in, say, a browser.\n```\n\nSpecify `--output` (`-o`) to declare the output file.  Otherwise the output\ngoes to STDOUT.\n\n## CLI source map options\n\nUglifyJS can generate a source map file, which is highly useful for\ndebugging your compressed JavaScript.  To get a source map, pass\n`--source-map --output output.js` (source map will be written out to\n`output.js.map`).\n\nAdditional options:\n\n- `--source-map \"filename='<NAME>'\"` to specify the name of the source map. The value of\n  `filename` is only used to set `file` attribute (see [the spec][sm-spec])\n  in source map file.\n\n- `--source-map \"root='<URL>'\"` to pass the URL where the original files can be found.\n\n- `--source-map \"names=false\"` to omit symbol names if you want to reduce size\n  of the source map file.\n\n- `--source-map \"url='<URL>'\"` to specify the URL where the source map can be found.\n  Otherwise UglifyJS assumes HTTP `X-SourceMap` is being used and will omit the\n  `//# sourceMappingURL=` directive.\n\nFor example:\n\n    uglifyjs js/file1.js js/file2.js \\\n             -o foo.min.js -c -m \\\n             --source-map \"root='http://foo.com/src',url='foo.min.js.map'\"\n\nThe above will compress and mangle `file1.js` and `file2.js`, will drop the\noutput in `foo.min.js` and the source map in `foo.min.js.map`.  The source\nmapping will refer to `http://foo.com/src/js/file1.js` and\n`http://foo.com/src/js/file2.js` (in fact it will list `http://foo.com/src`\nas the source map root, and the original files as `js/file1.js` and\n`js/file2.js`).\n\n### Composed source map\n\nWhen you're compressing JS code that was output by a compiler such as\nCoffeeScript, mapping to the JS code won't be too helpful.  Instead, you'd\nlike to map back to the original code (i.e. CoffeeScript).  UglifyJS has an\noption to take an input source map.  Assuming you have a mapping from\nCoffeeScript → compiled JS, UglifyJS can generate a map from CoffeeScript →\ncompressed JS by mapping every token in the compiled JS to its original\nlocation.\n\nTo use this feature pass `--source-map \"content='/path/to/input/source.map'\"`\nor `--source-map \"content=inline\"` if the source map is included inline with\nthe sources.\n\n## CLI compress options\n\nYou need to pass `--compress` (`-c`) to enable the compressor.  Optionally\nyou can pass a comma-separated list of [compress options](#compress-options).\n\nOptions are in the form `foo=bar`, or just `foo` (the latter implies\na boolean option that you want to set `true`; it's effectively a\nshortcut for `foo=true`).\n\nExample:\n\n    uglifyjs file.js -c toplevel,sequences=false\n\n## CLI mangle options\n\nTo enable the mangler you need to pass `--mangle` (`-m`).  The following\n(comma-separated) options are supported:\n\n- `eval` (default: `false`) — mangle names visible in scopes where `eval` or\n  `with` are used.\n\n- `reserved` (default: `[]`) — when mangling is enabled but you want to\n  prevent certain names from being mangled, you can declare those names with\n  `--mangle reserved` — pass a comma-separated list of names.  For example:\n\n      uglifyjs ... -m reserved=['$','require','exports']\n\n  to prevent the `require`, `exports` and `$` names from being changed.\n\n### CLI mangling property names (`--mangle-props`)\n\n**Note:** THIS WILL PROBABLY BREAK YOUR CODE.  Mangling property names\nis a separate step, different from variable name mangling.  Pass\n`--mangle-props` to enable it.  It will mangle all properties in the\ninput code with the exception of built in DOM properties and properties\nin core JavaScript classes.  For example:\n\n```javascript\n// example.js\nvar x = {\n    baz_: 0,\n    foo_: 1,\n    calc: function() {\n        return this.foo_ + this.baz_;\n    }\n};\nx.bar_ = 2;\nx[\"baz_\"] = 3;\nconsole.log(x.calc());\n```\nMangle all properties (except for JavaScript `builtins`):\n```bash\n$ uglifyjs example.js -c -m --mangle-props\n```\n```javascript\nvar x={o:0,_:1,l:function(){return this._+this.o}};x.t=2,x.o=3,console.log(x.l());\n```\nMangle all properties except for `reserved` properties:\n```bash\n$ uglifyjs example.js -c -m --mangle-props reserved=[foo_,bar_]\n```\n```javascript\nvar x={o:0,foo_:1,_:function(){return this.foo_+this.o}};x.bar_=2,x.o=3,console.log(x._());\n```\nMangle all properties matching a `regex`:\n```bash\n$ uglifyjs example.js -c -m --mangle-props regex=/_$/\n```\n```javascript\nvar x={o:0,_:1,calc:function(){return this._+this.o}};x.l=2,x.o=3,console.log(x.calc());\n```\n\nCombining mangle properties options:\n```bash\n$ uglifyjs example.js -c -m --mangle-props regex=/_$/,reserved=[bar_]\n```\n```javascript\nvar x={o:0,_:1,calc:function(){return this._+this.o}};x.bar_=2,x.o=3,console.log(x.calc());\n```\n\nIn order for this to be of any use, we avoid mangling standard JS names by\ndefault (`--mangle-props builtins` to override).\n\nA default exclusion file is provided in `tools/domprops.json` which should\ncover most standard JS and DOM properties defined in various browsers.  Pass\n`--mangle-props domprops` to disable this feature.\n\nA regular expression can be used to define which property names should be\nmangled.  For example, `--mangle-props regex=/^_/` will only mangle property\nnames that start with an underscore.\n\nWhen you compress multiple files using this option, in order for them to\nwork together in the end we need to ensure somehow that one property gets\nmangled to the same name in all of them.  For this, pass `--name-cache filename.json`\nand UglifyJS will maintain these mappings in a file which can then be reused.\nIt should be initially empty.  Example:\n\n```bash\n$ rm -f /tmp/cache.json  # start fresh\n$ uglifyjs file1.js file2.js --mangle-props --name-cache /tmp/cache.json -o part1.js\n$ uglifyjs file3.js file4.js --mangle-props --name-cache /tmp/cache.json -o part2.js\n```\n\nNow, `part1.js` and `part2.js` will be consistent with each other in terms\nof mangled property names.\n\nUsing the name cache is not necessary if you compress all your files in a\nsingle call to UglifyJS.\n\n### Mangling unquoted names (`--mangle-props keep_quoted`)\n\nUsing quoted property name (`o[\"foo\"]`) reserves the property name (`foo`)\nso that it is not mangled throughout the entire script even when used in an\nunquoted style (`o.foo`). Example:\n\n```javascript\n// stuff.js\nvar o = {\n    \"foo\": 1,\n    bar: 3,\n};\no.foo += o.bar;\nconsole.log(o.foo);\n```\n```bash\n$ uglifyjs stuff.js --mangle-props keep_quoted -c -m\n```\n```javascript\nvar o={foo:1,o:3};o.foo+=o.o,console.log(o.foo);\n```\n\nIf the minified output will be processed again by UglifyJS, consider specifying\n`keep_quoted_props` so the same property names are preserved:\n\n```bash\n$ uglifyjs stuff.js --mangle-props keep_quoted -c -m -O keep_quoted_props\n```\n```javascript\nvar o={\"foo\":1,o:3};o.foo+=o.o,console.log(o.foo);\n```\n\n### Debugging property name mangling\n\nYou can also pass `--mangle-props debug` in order to mangle property names\nwithout completely obscuring them. For example the property `o.foo`\nwould mangle to `o._$foo$_` with this option. This allows property mangling\nof a large codebase while still being able to debug the code and identify\nwhere mangling is breaking things.\n\n```bash\n$ uglifyjs stuff.js --mangle-props debug -c -m\n```\n```javascript\nvar o={_$foo$_:1,_$bar$_:3};o._$foo$_+=o._$bar$_,console.log(o._$foo$_);\n```\n\nYou can also pass a custom suffix using `--mangle-props debug=XYZ`. This would then\nmangle `o.foo` to `o._$foo$XYZ_`. You can change this each time you compile a\nscript to identify how a property got mangled. One technique is to pass a\nrandom number on every compile to simulate mangling changing with different\ninputs (e.g. as you update the input script with new properties), and to help\nidentify mistakes like writing mangled keys to storage.\n\n\n# API Reference\n\nAssuming installation via NPM, you can load UglifyJS in your application\nlike this:\n```javascript\nvar UglifyJS = require(\"uglify-js\");\n```\n\nThere is a single high level function, **`minify(code, options)`**,\nwhich will perform all minification [phases](#minify-options) in a configurable\nmanner. By default `minify()` will enable the options [`compress`](#compress-options)\nand [`mangle`](#mangle-options). Example:\n```javascript\nvar code = \"function add(first, second) { return first + second; }\";\nvar result = UglifyJS.minify(code);\nconsole.log(result.error); // runtime error, or `undefined` if no error\nconsole.log(result.code);  // minified output: function add(n,d){return n+d}\n```\n\nYou can `minify` more than one JavaScript file at a time by using an object\nfor the first argument where the keys are file names and the values are source\ncode:\n```javascript\nvar code = {\n    \"file1.js\": \"function add(first, second) { return first + second; }\",\n    \"file2.js\": \"console.log(add(1 + 2, 3 + 4));\"\n};\nvar result = UglifyJS.minify(code);\nconsole.log(result.code);\n// function add(d,n){return d+n}console.log(add(3,7));\n```\n\nThe `toplevel` option:\n```javascript\nvar code = {\n    \"file1.js\": \"function add(first, second) { return first + second; }\",\n    \"file2.js\": \"console.log(add(1 + 2, 3 + 4));\"\n};\nvar options = { toplevel: true };\nvar result = UglifyJS.minify(code, options);\nconsole.log(result.code);\n// console.log(3+7);\n```\n\nThe `nameCache` option:\n```javascript\nvar options = {\n    mangle: {\n        toplevel: true,\n    },\n    nameCache: {}\n};\nvar result1 = UglifyJS.minify({\n    \"file1.js\": \"function add(first, second) { return first + second; }\"\n}, options);\nvar result2 = UglifyJS.minify({\n    \"file2.js\": \"console.log(add(1 + 2, 3 + 4));\"\n}, options);\nconsole.log(result1.code);\n// function n(n,r){return n+r}\nconsole.log(result2.code);\n// console.log(n(3,7));\n```\n\nYou may persist the name cache to the file system in the following way:\n```javascript\nvar cacheFileName = \"/tmp/cache.json\";\nvar options = {\n    mangle: {\n        properties: true,\n    },\n    nameCache: JSON.parse(fs.readFileSync(cacheFileName, \"utf8\"))\n};\nfs.writeFileSync(\"part1.js\", UglifyJS.minify({\n    \"file1.js\": fs.readFileSync(\"file1.js\", \"utf8\"),\n    \"file2.js\": fs.readFileSync(\"file2.js\", \"utf8\")\n}, options).code, \"utf8\");\nfs.writeFileSync(\"part2.js\", UglifyJS.minify({\n    \"file3.js\": fs.readFileSync(\"file3.js\", \"utf8\"),\n    \"file4.js\": fs.readFileSync(\"file4.js\", \"utf8\")\n}, options).code, \"utf8\");\nfs.writeFileSync(cacheFileName, JSON.stringify(options.nameCache), \"utf8\");\n```\n\nAn example of a combination of `minify()` options:\n```javascript\nvar code = {\n    \"file1.js\": \"function add(first, second) { return first + second; }\",\n    \"file2.js\": \"console.log(add(1 + 2, 3 + 4));\"\n};\nvar options = {\n    toplevel: true,\n    compress: {\n        global_defs: {\n            \"@console.log\": \"alert\"\n        },\n        passes: 2\n    },\n    output: {\n        beautify: false,\n        preamble: \"/* uglified */\"\n    }\n};\nvar result = UglifyJS.minify(code, options);\nconsole.log(result.code);\n// /* uglified */\n// alert(10);\"\n```\n\nTo produce warnings:\n```javascript\nvar code = \"function f(){ var u; return 2 + 3; }\";\nvar options = { warnings: true };\nvar result = UglifyJS.minify(code, options);\nconsole.log(result.error);    // runtime error, `undefined` in this case\nconsole.log(result.warnings); // [ 'Dropping unused variable u [0:1,18]' ]\nconsole.log(result.code);     // function f(){return 5}\n```\n\nAn error example:\n```javascript\nvar result = UglifyJS.minify({\"foo.js\" : \"if (0) else console.log(1);\"});\nconsole.log(JSON.stringify(result.error));\n// {\"message\":\"Unexpected token: keyword (else)\",\"filename\":\"foo.js\",\"line\":1,\"col\":7,\"pos\":7}\n```\nNote: unlike `uglify-js@2.x`, the `3.x` API does not throw errors. To\nachieve a similar effect one could do the following:\n```javascript\nvar result = UglifyJS.minify(code, options);\nif (result.error) throw result.error;\n```\n\n## Minify options\n\n- `annotations` — pass `false` to ignore all comment annotations and elide them\n  from output. Useful when, for instance, external tools incorrectly applied\n  `/*@__PURE__*/` or `/*#__PURE__*/`. Pass `true` to both compress and retain\n  comment annotations in output to allow for further processing downstream.\n\n- `compress` (default: `{}`) — pass `false` to skip compressing entirely.\n  Pass an object to specify custom [compress options](#compress-options).\n\n- `expression` (default: `false`) — parse as a single expression, e.g. JSON.\n\n- `ie` (default: `false`) — enable workarounds for Internet Explorer bugs.\n\n- `keep_fargs` (default: `false`) — pass `true` to prevent discarding or mangling\n  of function arguments.\n\n- `keep_fnames` (default: `false`) — pass `true` to prevent discarding or mangling\n  of function names.  Useful for code relying on `Function.prototype.name`.\n\n- `mangle` (default: `true`) — pass `false` to skip mangling names, or pass\n  an object to specify [mangle options](#mangle-options) (see below).\n\n  - `mangle.properties` (default: `false`) — a subcategory of the mangle option.\n    Pass an object to specify custom [mangle property options](#mangle-properties-options).\n\n- `module` (default: `true`) — process input as ES module, i.e. implicit\n  `\"use strict\";` and support for top-level `await`. When explicitly specified,\n  also enables `toplevel`.\n\n- `nameCache` (default: `null`) — pass an empty object `{}` or a previously\n  used `nameCache` object if you wish to cache mangled variable and\n  property names across multiple invocations of `minify()`. Note: this is\n  a read/write property. `minify()` will read the name cache state of this\n  object and update it during minification so that it may be\n  reused or externally persisted by the user.\n\n- `output` (default: `null`) — pass an object if you wish to specify\n  additional [output options](#output-options).  The defaults are optimized\n  for best compression.\n\n- `parse` (default: `{}`) — pass an object if you wish to specify some\n  additional [parse options](#parse-options).\n\n- `sourceMap` (default: `false`) — pass an object if you wish to specify\n  [source map options](#source-map-options).\n\n- `toplevel` (default: `false`) — set to `true` if you wish to enable top level\n  variable and function name mangling and to drop unused variables and functions.\n\n- `v8` (default: `false`) — enable workarounds for Chrome & Node.js bugs.\n\n- `warnings` (default: `false`) — pass `true` to return compressor warnings\n  in `result.warnings`. Use the value `\"verbose\"` for more detailed warnings.\n\n- `webkit` (default: `false`) — enable workarounds for Safari/WebKit bugs.\n  PhantomJS users should set this option to `true`.\n\n## Minify options structure\n\n```javascript\n{\n    parse: {\n        // parse options\n    },\n    compress: {\n        // compress options\n    },\n    mangle: {\n        // mangle options\n\n        properties: {\n            // mangle property options\n        }\n    },\n    output: {\n        // output options\n    },\n    sourceMap: {\n        // source map options\n    },\n    nameCache: null, // or specify a name cache object\n    toplevel: false,\n    warnings: false,\n}\n```\n\n### Source map options\n\nTo generate a source map:\n```javascript\nvar result = UglifyJS.minify({\"file1.js\": \"var a = function() {};\"}, {\n    sourceMap: {\n        filename: \"out.js\",\n        url: \"out.js.map\"\n    }\n});\nconsole.log(result.code); // minified output\nconsole.log(result.map);  // source map\n```\n\nNote that the source map is not saved in a file, it's just returned in\n`result.map`.  The value passed for `sourceMap.url` is only used to set\n`//# sourceMappingURL=out.js.map` in `result.code`. The value of\n`filename` is only used to set `file` attribute (see [the spec][sm-spec])\nin source map file.\n\nYou can set option `sourceMap.url` to be `\"inline\"` and source map will\nbe appended to code.\n\nYou can also specify sourceRoot property to be included in source map:\n```javascript\nvar result = UglifyJS.minify({\"file1.js\": \"var a = function() {};\"}, {\n    sourceMap: {\n        root: \"http://example.com/src\",\n        url: \"out.js.map\"\n    }\n});\n```\n\nIf you're compressing compiled JavaScript and have a source map for it, you\ncan use `sourceMap.content`:\n```javascript\nvar result = UglifyJS.minify({\"compiled.js\": \"compiled code\"}, {\n    sourceMap: {\n        content: \"content from compiled.js.map\",\n        url: \"minified.js.map\"\n    }\n});\n// same as before, it returns `code` and `map`\n```\n\nIf you're using the `X-SourceMap` header instead, you can just omit `sourceMap.url`.\n\nIf you wish to reduce file size of the source map, set option `sourceMap.names`\nto be `false` and all symbol names will be omitted.\n\n## Parse options\n\n- `bare_returns` (default: `false`) — support top level `return` statements\n\n- `html5_comments` (default: `true`) — process HTML comment as workaround for\n  browsers which do not recognize `<script>` tags\n\n- `module` (default: `false`) — set to `true` if you wish to process input as\n  ES module, i.e. implicit `\"use strict\";` and support for top-level `await`.\n\n- `shebang` (default: `true`) — support `#!command` as the first line\n\n## Compress options\n\n- `annotations` (default: `true`) — Pass `false` to disable potentially dropping\n  functions marked as \"pure\".  A function call is marked as \"pure\" if a comment\n  annotation `/*@__PURE__*/` or `/*#__PURE__*/` immediately precedes the call. For\n  example: `/*@__PURE__*/foo();`\n\n- `arguments` (default: `true`) — replace `arguments[index]` with function\n  parameter name whenever possible.\n\n- `arrows` (default: `true`) — apply optimizations to arrow functions\n\n- `assignments` (default: `true`) — apply optimizations to assignment expressions\n\n- `awaits` (default: `true`) — apply optimizations to `await` expressions\n\n- `booleans` (default: `true`) — various optimizations for boolean context,\n  for example `!!a ? b : c → a ? b : c`\n\n- `collapse_vars` (default: `true`) — Collapse single-use non-constant variables,\n  side effects permitting.\n\n- `comparisons` (default: `true`) — apply certain optimizations to binary nodes,\n  e.g. `!(a <= b) → a > b`, attempts to negate binary nodes, e.g.\n  `a = !b && !c && !d && !e → a=!(b||c||d||e)` etc.\n\n- `conditionals` (default: `true`) — apply optimizations for `if`-s and conditional\n  expressions\n\n- `dead_code` (default: `true`) — remove unreachable code\n\n- `default_values` (default: `true`) — drop overshadowed default values\n\n- `directives` (default: `true`) — remove redundant or non-standard directives\n\n- `drop_console` (default: `false`) — Pass `true` to discard calls to\n  `console.*` functions. If you wish to drop a specific function call\n  such as `console.info` and/or retain side effects from function arguments\n  after dropping the function call then use `pure_funcs` instead.\n\n- `drop_debugger` (default: `true`) — remove `debugger;` statements\n\n- `evaluate` (default: `true`) — Evaluate expression for shorter constant\n  representation. Pass `\"eager\"` to always replace function calls whenever\n  possible, or a positive integer to specify an upper bound for each individual\n  evaluation in number of characters.\n\n- `expression` (default: `false`) — Pass `true` to preserve completion values\n  from terminal statements without `return`, e.g. in bookmarklets.\n\n- `functions` (default: `true`) — convert declarations from `var` to `function`\n  whenever possible.\n\n- `global_defs` (default: `{}`) — see [conditional compilation](#conditional-compilation)\n\n- `hoist_exports` (default: `true`) — hoist `export` statements to facilitate\n  various `compress` and `mangle` optimizations.\n\n- `hoist_funs` (default: `false`) — hoist function declarations\n\n- `hoist_props` (default: `true`) — hoist properties from constant object and\n  array literals into regular variables subject to a set of constraints. For example:\n  `var o={p:1, q:2}; f(o.p, o.q);` is converted to `f(1, 2);`. Note: `hoist_props`\n  works best with `toplevel` and `mangle` enabled, alongside with `compress` option\n  `passes` set to `2` or higher.\n\n- `hoist_vars` (default: `false`) — hoist `var` declarations (this is `false`\n  by default because it seems to increase the size of the output in general)\n\n- `if_return` (default: `true`) — optimizations for if/return and if/continue\n\n- `imports` (default: `true`) — drop unreferenced import symbols when used with `unused`\n\n- `inline` (default: `true`) — inline calls to function with simple/`return` statement:\n  - `false` — same as `0`\n  - `0` — disabled inlining\n  - `1` — inline simple functions\n  - `2` — inline functions with arguments\n  - `3` — inline functions with arguments and variables\n  - `4` — inline functions with arguments, variables and statements\n  - `true` — same as `4`\n\n- `join_vars` (default: `true`) — join consecutive `var` statements\n\n- `keep_fargs` (default: `false`) — discard unused function arguments except\n  when unsafe to do so, e.g. code which relies on `Function.prototype.length`.\n  Pass `true` to always retain function arguments.\n\n- `keep_infinity` (default: `false`) — Pass `true` to prevent `Infinity` from\n  being compressed into `1/0`, which may cause performance issues on Chrome.\n\n- `loops` (default: `true`) — optimizations for `do`, `while` and `for` loops\n  when we can statically determine the condition.\n\n- `merge_vars` (default: `true`) — combine and reuse variables.\n\n- `module` (default: `false`) — set to `true` if you wish to process input as\n  ES module, i.e. implicit `\"use strict\";`.\n\n- `negate_iife` (default: `true`) — negate \"Immediately-Called Function Expressions\"\n  where the return value is discarded, to avoid the parentheses that the\n  code generator would insert.\n\n- `objects` (default: `true`) — compact duplicate keys in object literals.\n\n- `passes` (default: `1`) — The maximum number of times to run compress.\n  In some cases more than one pass leads to further compressed code.  Keep in\n  mind more passes will take more time.\n\n- `properties` (default: `true`) — rewrite property access using the dot notation, for\n  example `foo[\"bar\"] → foo.bar`\n\n- `pure_funcs` (default: `null`) — You can pass an array of names and\n  UglifyJS will assume that those functions do not produce side\n  effects.  DANGER: will not check if the name is redefined in scope.\n  An example case here, for instance `var q = Math.floor(a/b)`.  If\n  variable `q` is not used elsewhere, UglifyJS will drop it, but will\n  still keep the `Math.floor(a/b)`, not knowing what it does.  You can\n  pass `pure_funcs: [ 'Math.floor' ]` to let it know that this\n  function won't produce any side effect, in which case the whole\n  statement would get discarded.  The current implementation adds some\n  overhead (compression will be slower). Make sure symbols under `pure_funcs`\n  are also under `mangle.reserved` to avoid mangling.\n\n- `pure_getters` (default: `\"strict\"`) — Pass `true` for UglifyJS to assume that\n  object property access (e.g. `foo.bar` or `a[42]`) does not throw exception or\n  alter program states via getter function. Pass `\"strict\"` to allow dropping or\n  reordering `foo.bar` only if `foo` is not `null` or `undefined` and is safe to\n  access as a variable. Pass `false` to retain all property accesses.\n\n- `reduce_funcs` (default: `true`) — Allows single-use functions to be\n  inlined as function expressions when permissible allowing further\n  optimization.  Enabled by default.  Option depends on `reduce_vars`\n  being enabled.  Some code runs faster in the Chrome V8 engine if this\n  option is disabled.  Does not negatively impact other major browsers.\n\n- `reduce_vars` (default: `true`) — Improve optimization on variables assigned with and\n  used as constant values.\n\n- `rests` (default: `true`) — apply optimizations to rest parameters\n\n- `sequences` (default: `true`) — join consecutive simple statements using the\n  comma operator.  May be set to a positive integer to specify the maximum number\n  of consecutive comma sequences that will be generated. If this option is set to\n  `true` then the default `sequences` limit is `200`. Set option to `false` or `0`\n  to disable. The smallest `sequences` length is `2`. A `sequences` value of `1`\n  is grandfathered to be equivalent to `true` and as such means `200`. On rare\n  occasions the default sequences limit leads to very slow compress times in which\n  case a value of `20` or less is recommended.\n\n- `side_effects` (default: `true`) — drop extraneous code which does not affect\n  outcome of runtime execution.\n\n- `spreads` (default: `true`) — flatten spread expressions.\n\n- `strings` (default: `true`) — compact string concatenations.\n\n- `switches` (default: `true`) — de-duplicate and remove unreachable `switch` branches\n\n- `templates` (default: `true`) — compact template literals by embedding expressions\n  and/or converting to string literals, e.g. `` `foo ${42}` → \"foo 42\"``\n\n- `top_retain` (default: `null`) — prevent specific toplevel functions and\n  variables from `unused` removal (can be array, comma-separated, RegExp or\n  function. Implies `toplevel`)\n\n- `toplevel` (default: `false`) — drop unreferenced functions (`\"funcs\"`) and/or\n  variables (`\"vars\"`) in the top level scope (`false` by default, `true` to drop\n  both unreferenced functions and variables)\n\n- `typeofs` (default: `true`) — compress `typeof` expressions, e.g.\n  `typeof foo == \"undefined\" → void 0 === foo`\n\n- `unsafe` (default: `false`) — apply \"unsafe\" transformations (discussion below)\n\n- `unsafe_comps` (default: `false`) — assume operands cannot be (coerced to) `NaN`\n  in numeric comparisons, e.g. `a <= b`. In addition, expressions involving `in`\n  or `instanceof` would never throw.\n\n- `unsafe_Function` (default: `false`) — compress and mangle `Function(args, code)`\n  when both `args` and `code` are string literals.\n\n- `unsafe_math` (default: `false`) — optimize numerical expressions like\n  `2 * x * 3` into `6 * x`, which may give imprecise floating point results.\n\n- `unsafe_proto` (default: `false`) — optimize expressions like\n  `Array.prototype.slice.call(a)` into `[].slice.call(a)`\n\n- `unsafe_regexp` (default: `false`) — enable substitutions of variables with\n  `RegExp` values the same way as if they are constants.\n\n- `unsafe_undefined` (default: `false`) — substitute `void 0` if there is a\n  variable named `undefined` in scope (variable name will be mangled, typically\n  reduced to a single character)\n\n- `unused` (default: `true`) — drop unreferenced functions and variables (simple\n  direct variable assignments do not count as references unless set to `\"keep_assign\"`)\n\n- `varify` (default: `true`) — convert block-scoped declarations into `var`\n  whenever safe to do so\n\n- `yields` (default: `true`) — apply optimizations to `yield` expressions\n\n## Mangle options\n\n- `eval` (default: `false`) — Pass `true` to mangle names visible in scopes\n  where `eval` or `with` are used.\n\n- `reserved` (default: `[]`) — Pass an array of identifiers that should be\n  excluded from mangling. Example: `[\"foo\", \"bar\"]`.\n\n- `toplevel` (default: `false`) — Pass `true` to mangle names declared in the\n  top level scope.\n\nExamples:\n\n```javascript\n// test.js\nvar globalVar;\nfunction funcName(firstLongName, anotherLongName) {\n    var myVariable = firstLongName +  anotherLongName;\n}\n```\n```javascript\nvar code = fs.readFileSync(\"test.js\", \"utf8\");\n\nUglifyJS.minify(code).code;\n// 'function funcName(a,n){}var globalVar;'\n\nUglifyJS.minify(code, { mangle: { reserved: ['firstLongName'] } }).code;\n// 'function funcName(firstLongName,a){}var globalVar;'\n\nUglifyJS.minify(code, { mangle: { toplevel: true } }).code;\n// 'function n(n,a){}var a;'\n```\n\n### Mangle properties options\n\n- `builtins` (default: `false`) — Use `true` to allow the mangling of built-in\n  properties of JavaScript API. Not recommended to override this setting.\n\n- `debug` (default: `false`) — Mangle names with the original name still present.\n  Pass an empty string `\"\"` to enable, or a non-empty string to set the debug suffix.\n\n- `domprops` (default: `false`) — Use `true` to allow the mangling of properties\n  commonly found in Document Object Model. Not recommended to override this setting.\n\n- `keep_fargs` (default: `false`) — Use `true` to prevent mangling of function\n  arguments.\n\n- `keep_quoted` (default: `false`) — Only mangle unquoted property names.\n\n- `regex` (default: `null`) — Pass a RegExp literal to only mangle property\n  names matching the regular expression.\n\n- `reserved` (default: `[]`) — Do not mangle property names listed in the\n  `reserved` array.\n\n## Output options\n\nThe code generator tries to output shortest code possible by default.  In\ncase you want beautified output, pass `--beautify` (`-b`).  Optionally you\ncan pass additional arguments that control the code output:\n\n- `annotations` (default: `false`) — pass `true` to retain comment annotations\n  `/*@__PURE__*/` or `/*#__PURE__*/`, otherwise they will be discarded even if\n  `comments` is set.\n\n- `ascii_only` (default: `false`) — escape Unicode characters in strings and\n  regexps (affects directives with non-ascii characters becoming invalid)\n\n- `beautify` (default: `true`) — whether to actually beautify the output.\n  Passing `-b` will set this to true. Use `-O` if you want to generate minified\n  code and specify additional arguments.\n\n- `braces` (default: `false`) — always insert braces in `if`, `for`,\n  `do`, `while` or `with` statements, even if their body is a single\n  statement.\n\n- `comments` (default: `false`) — pass `true` or `\"all\"` to preserve all\n  comments, `\"some\"` to preserve multi-line comments that contain `@cc_on`,\n  `@license`, or `@preserve` (case-insensitive), a regular expression string\n  (e.g. `/^!/`), or a function which returns `boolean`, e.g.\n  ```javascript\n  function(node, comment) {\n      return comment.value.indexOf(\"@type \" + node.TYPE) >= 0;\n  }\n  ```\n\n- `extendscript` (default: `false`) — enable workarounds for Adobe ExtendScript\n  bugs\n\n- `galio` (default: `false`) — enable workarounds for ANT Galio bugs\n\n- `indent_level` (default: `4`) — indent by specified number of spaces or the\n  exact whitespace sequence supplied, e.g. `\"\\t\"`.\n\n- `indent_start` (default: `0`) — prefix all lines by whitespace sequence\n  specified in the same format as `indent_level`.\n\n- `inline_script` (default: `true`) — escape HTML comments and the slash in\n  occurrences of `</script>` in strings\n\n- `keep_quoted_props` (default: `false`) — when turned on, prevents stripping\n  quotes from property names in object literals.\n\n- `max_line_len` (default: `false`) — maximum line length (for uglified code)\n\n- `preamble` (default: `null`) — when passed it must be a string and\n  it will be prepended to the output literally.  The source map will\n  adjust for this text.  Can be used to insert a comment containing\n  licensing information, for example.\n\n- `preserve_line` (default: `false`) — pass `true` to retain line numbering on\n  a best effort basis.\n\n- `quote_keys` (default: `false`) — pass `true` to quote all keys in literal\n  objects\n\n- `quote_style` (default: `0`) — preferred quote style for strings (affects\n  quoted property names and directives as well):\n  - `0` — prefers double quotes, switches to single quotes when there are\n    more double quotes in the string itself. `0` is best for gzip size.\n  - `1` — always use single quotes\n  - `2` — always use double quotes\n  - `3` — always use the original quotes\n\n- `semicolons` (default: `true`) — separate statements with semicolons.  If\n  you pass `false` then whenever possible we will use a newline instead of a\n  semicolon, leading to more readable output of uglified code (size before\n  gzip could be smaller; size after gzip insignificantly larger).\n\n- `shebang` (default: `true`) — preserve shebang `#!` in preamble (bash scripts)\n\n- `width` (default: `80`) — only takes effect when beautification is on, this\n  specifies an (orientative) line width that the beautifier will try to\n  obey.  It refers to the width of the line text (excluding indentation).\n  It doesn't work very well currently, but it does make the code generated\n  by UglifyJS more readable.\n\n- `wrap_iife` (default: `false`) — pass `true` to wrap immediately invoked\n  function expressions. See\n  [#640](https://github.com/mishoo/UglifyJS/issues/640) for more details.\n\n# Miscellaneous\n\n### Keeping copyright notices or other comments\n\nYou can pass `--comments` to retain certain comments in the output.  By\ndefault it will keep JSDoc-style comments that contain \"@preserve\",\n\"@license\" or \"@cc_on\" (conditional compilation for IE).  You can pass\n`--comments all` to keep all the comments, or a valid JavaScript regexp to\nkeep only comments that match this regexp.  For example `--comments /^!/`\nwill keep comments like `/*! Copyright Notice */`.\n\nNote, however, that there might be situations where comments are lost.  For\nexample:\n```javascript\nfunction f() {\n    /** @preserve Foo Bar */\n    function g() {\n        // this function is never called\n    }\n    return something();\n}\n```\n\nEven though it has \"@preserve\", the comment will be lost because the inner\nfunction `g` (which is the AST node to which the comment is attached to) is\ndiscarded by the compressor as not referenced.\n\nThe safest comments where to place copyright information (or other info that\nneeds to be kept in the output) are comments attached to toplevel nodes.\n\n### The `unsafe` `compress` option\n\nIt enables some transformations that *might* break code logic in certain\ncontrived cases, but should be fine for most code.  You might want to try it\non your own code, it should reduce the minified size.  Here's what happens\nwhen this flag is on:\n\n- `new Array(1, 2, 3)` or `Array(1, 2, 3)` → `[ 1, 2, 3 ]`\n- `new Object()` → `{}`\n- `String(exp)` or `exp.toString()` → `\"\" + exp`\n- `new Object/RegExp/Function/Error/Array (...)` → we discard the `new`\n\n### Conditional compilation\n\nYou can use the `--define` (`-d`) switch in order to declare global\nvariables that UglifyJS will assume to be constants (unless defined in\nscope).  For example if you pass `--define DEBUG=false` then, coupled with\ndead code removal UglifyJS will discard the following from the output:\n```javascript\nif (DEBUG) {\n    console.log(\"debug stuff\");\n}\n```\n\nYou can specify nested constants in the form of `--define env.DEBUG=false`.\n\nUglifyJS will warn about the condition being always false and about dropping\nunreachable code; for now there is no option to turn off only this specific\nwarning, you can pass `warnings=false` to turn off *all* warnings.\n\nAnother way of doing that is to declare your globals as constants in a\nseparate file and include it into the build.  For example you can have a\n`build/defines.js` file with the following:\n```javascript\nvar DEBUG = false;\nvar PRODUCTION = true;\n// etc.\n```\n\nand build your code like this:\n\n    uglifyjs build/defines.js js/foo.js js/bar.js... -c\n\nUglifyJS will notice the constants and, since they cannot be altered, it\nwill evaluate references to them to the value itself and drop unreachable\ncode as usual.  The build will contain the `const` declarations if you use\nthem. If you are targeting < ES6 environments which does not support `const`,\nusing `var` with `reduce_vars` (enabled by default) should suffice.\n\n### Conditional compilation API\n\nYou can also use conditional compilation via the programmatic API. With the difference that the\nproperty name is `global_defs` and is a compressor property:\n\n```javascript\nvar result = UglifyJS.minify(fs.readFileSync(\"input.js\", \"utf8\"), {\n    compress: {\n        dead_code: true,\n        global_defs: {\n            DEBUG: false\n        }\n    }\n});\n```\n\nTo replace an identifier with an arbitrary non-constant expression it is\nnecessary to prefix the `global_defs` key with `\"@\"` to instruct UglifyJS\nto parse the value as an expression:\n```javascript\nUglifyJS.minify(\"alert('hello');\", {\n    compress: {\n        global_defs: {\n            \"@alert\": \"console.log\"\n        }\n    }\n}).code;\n// returns: 'console.log(\"hello\");'\n```\n\nOtherwise it would be replaced as string literal:\n```javascript\nUglifyJS.minify(\"alert('hello');\", {\n    compress: {\n        global_defs: {\n            \"alert\": \"console.log\"\n        }\n    }\n}).code;\n// returns: '\"console.log\"(\"hello\");'\n```\n\n### Using native Uglify AST with `minify()`\n```javascript\n// example: parse only, produce native Uglify AST\n\nvar result = UglifyJS.minify(code, {\n    parse: {},\n    compress: false,\n    mangle: false,\n    output: {\n        ast: true,\n        code: false  // optional - faster if false\n    }\n});\n\n// result.ast contains native Uglify AST\n```\n```javascript\n// example: accept native Uglify AST input and then compress and mangle\n//          to produce both code and native AST.\n\nvar result = UglifyJS.minify(ast, {\n    compress: {},\n    mangle: {},\n    output: {\n        ast: true,\n        code: true  // optional - faster if false\n    }\n});\n\n// result.ast contains native Uglify AST\n// result.code contains the minified code in string form.\n```\n\n### Working with Uglify AST\n\nTransversal and transformation of the native AST can be performed through\n[`TreeWalker`](https://github.com/mishoo/UglifyJS/blob/master/lib/ast.js) and\n[`TreeTransformer`](https://github.com/mishoo/UglifyJS/blob/master/lib/transform.js)\nrespectively.\n\n### ESTree / SpiderMonkey AST\n\nUglifyJS has its own abstract syntax tree format; for\n[practical reasons](http://lisperator.net/blog/uglifyjs-why-not-switching-to-spidermonkey-ast/)\nwe can't easily change to using the SpiderMonkey AST internally.  However,\nUglifyJS now has a converter which can import a SpiderMonkey AST.\n\nFor example [Acorn][acorn] is a super-fast parser that produces a\nSpiderMonkey AST.  It has a small CLI utility that parses one file and dumps\nthe AST in JSON on the standard output.  To use UglifyJS to mangle and\ncompress that:\n\n    acorn file.js | uglifyjs -p spidermonkey -m -c\n\nThe `-p spidermonkey` option tells UglifyJS that all input files are not\nJavaScript, but JS code described in SpiderMonkey AST in JSON.  Therefore we\ndon't use our own parser in this case, but just transform that AST into our\ninternal AST.\n\n### Use Acorn for parsing\n\nMore for fun, I added the `-p acorn` option which will use Acorn to do all\nthe parsing.  If you pass this option, UglifyJS will `require(\"acorn\")`.\n\nAcorn is really fast (e.g. 250ms instead of 380ms on some 650K code), but\nconverting the SpiderMonkey tree that Acorn produces takes another 150ms so\nin total it's a bit more than just using UglifyJS's own parser.\n\n[acorn]: https://github.com/ternjs/acorn\n[sm-spec]: https://docs.google.com/document/d/1U1RGAehQwRypUTovF1KRlpiOFze0b-_2gc6fAH0KY0k\n\n### Uglify Fast Minify Mode\n\nIt's not well known, but whitespace removal and symbol mangling accounts\nfor 95% of the size reduction in minified code for most JavaScript - not\nelaborate code transforms. One can simply disable `compress` to speed up\nUglify builds by 3 to 5 times.\n\n| d3.js | minify size | gzip size | minify time (seconds) |\n| --- | ---: | ---: | ---: |\n| original | 511,371 | 119,932 | - |\n| uglify-js@3.13.0 mangle=false, compress=false | 363,988 | 95,695 | 0.56 |\n| uglify-js@3.13.0 mangle=true, compress=false | 253,305 | 81,281 | 0.99 |\n| uglify-js@3.13.0 mangle=true, compress=true | 244,436 | 79,854 | 5.30 |\n\nTo enable fast minify mode from the CLI use:\n```\nuglifyjs file.js -m\n```\nTo enable fast minify mode with the API use:\n```javascript\nUglifyJS.minify(code, { compress: false, mangle: true });\n```\n\n### Source maps and debugging\n\nVarious `compress` transforms that simplify, rearrange, inline and remove code\nare known to have an adverse effect on debugging with source maps. This is\nexpected as code is optimized and mappings are often simply not possible as\nsome code no longer exists. For highest fidelity in source map debugging\ndisable the Uglify `compress` option and just use `mangle`.\n\n### Compiler assumptions\n\nTo allow for better optimizations, the compiler makes various assumptions:\n\n- The code does not rely on preserving its runtime performance characteristics.\n  Typically uglified code will run faster due to less instructions and easier\n  inlining, but may be slower on rare occasions for a specific platform, e.g.\n  see [`reduce_funcs`](#compress-options).\n- `.toString()` and `.valueOf()` don't have side effects, and for built-in\n  objects they have not been overridden.\n- `undefined`, `NaN` and `Infinity` have not been externally redefined.\n- `arguments.callee`, `arguments.caller` and `Function.prototype.caller` are not used.\n- The code doesn't expect the contents of `Function.prototype.toString()` or\n  `Error.prototype.stack` to be anything in particular.\n- Getting and setting properties on a plain object does not cause other side effects\n  (using `.watch()` or `Proxy`).\n- Object properties can be added, removed and modified (not prevented with\n  `Object.defineProperty()`, `Object.defineProperties()`, `Object.freeze()`,\n  `Object.preventExtensions()` or `Object.seal()`).\n- If array destructuring is present, index-like properties in `Array.prototype`\n  have not been overridden:\n  ```javascript\n  Object.prototype[0] = 42;\n  var [ a ] = [];\n  var { 0: b } = {};\n  // 42 undefined\n  console.log([][0], a);\n  // 42 42\n  console.log({}[0], b);\n  ```\n- Earlier versions of JavaScript will throw `SyntaxError` with the following:\n  ```javascript\n  ({\n      p: 42,\n      get p() {},\n  });\n  // SyntaxError: Object literal may not have data and accessor property with\n  //              the same name\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.\n- Iteration order of keys over an object which contains spread syntax in later\n  versions of Chrome and Node.js may be altered.\n- When `toplevel` is enabled, UglifyJS effectively assumes input code is wrapped\n  within `function(){ ... }`, thus forbids aliasing of declared global variables:\n  ```javascript\n  A = \"FAIL\";\n  var B = \"FAIL\";\n  // can be `global`, `self`, `window` etc.\n  var top = function() {\n      return this;\n  }();\n  // \"PASS\"\n  top.A = \"PASS\";\n  console.log(A);\n  // \"FAIL\" after compress and/or mangle\n  top.B = \"PASS\";\n  console.log(B);\n  ```\n- Use of `arguments` alongside destructuring as function parameters, e.g.\n  `function({}, arguments) {}` will result in `SyntaxError` in earlier versions\n  of Chrome and Node.js - UglifyJS may modify the input which in turn may\n  suppress those errors.\n- Earlier versions of Chrome and Node.js will throw `ReferenceError` with the\n  following:\n  ```javascript\n  var a;\n  try {\n      throw 42;\n  } catch ({\n      [a]: b,\n      // ReferenceError: a is not defined\n  }) {\n      let a;\n  }\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.\n- Later versions of JavaScript will throw `SyntaxError` with the following:\n  ```javascript\n  a => {\n      let a;\n  };\n  // SyntaxError: Identifier 'a' has already been declared\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.\n- Later versions of JavaScript will throw `SyntaxError` with the following:\n  ```javascript\n  try {\n      // ...\n  } catch ({ message: a }) {\n      var a;\n  }\n  // SyntaxError: Identifier 'a' has already been declared\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.\n- Some versions of Chrome and Node.js will throw `ReferenceError` with the\n  following:\n  ```javascript\n  console.log(((a, b = function() {\n      return a;\n      // ReferenceError: a is not defined\n  }()) => b)());\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.\n- Some arithmetic operations with `BigInt` may throw `TypeError`:\n  ```javascript\n  1n + 1;\n  // TypeError: can't convert BigInt to number\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.\n- Some versions of JavaScript will throw `SyntaxError` with the\n  following:\n  ```javascript\n  console.log(String.raw`\\uFo`);\n  // SyntaxError: Invalid Unicode escape sequence\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.\n- Some versions of JavaScript will throw `SyntaxError` with the\n  following:\n  ```javascript\n  try {} catch (e) {\n      for (var e of []);\n  }\n  // SyntaxError: Identifier 'e' has already been declared\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.\n- Some versions of Chrome and Node.js will give incorrect results with the\n  following:\n  ```javascript\n  console.log({\n      ...{\n          set 42(v) {},\n          42: \"PASS\",\n      },\n  });\n  // Expected: { '42': 'PASS' }\n  // Actual:   { '42': undefined }\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.\n- Later versions of JavaScript will throw `SyntaxError` with the following:\n  ```javascript\n  var await;\n  class A {\n      static p = await;\n  }\n  // SyntaxError: Unexpected reserved word\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.\n- Later versions of JavaScript will throw `SyntaxError` with the following:\n  ```javascript\n  var async;\n  for (async of []);\n  // SyntaxError: The left-hand side of a for-of loop may not be 'async'.\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.\n- Some versions of Chrome and Node.js will give incorrect results with the\n  following:\n  ```javascript\n  console.log({\n      ...console,\n      get 42() {\n          return \"FAIL\";\n      },\n      [42]: \"PASS\",\n  }[42], {\n      ...console,\n      get 42() {\n          return \"FAIL\";\n      },\n      42: \"PASS\",\n  }[42]);\n  // Expected: \"PASS PASS\"\n  // Actual:   \"PASS FAIL\"\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.\n- Earlier versions of JavaScript will throw `TypeError` with the following:\n  ```javascript\n  (function() {\n      {\n          const a = \"foo\";\n      }\n      {\n          const a = \"bar\";\n      }\n  })();\n  // TypeError: const 'a' has already been declared\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.\n- Later versions of Chrome and Node.js will give incorrect results with the\n  following:\n  ```javascript\n  try {\n      class A {\n          static 42;\n          static get 42() {}\n      }\n      console.log(\"PASS\");\n  } catch (e) {\n      console.log(\"FAIL\");\n  }\n  // Expected: \"PASS\"\n  // Actual:   \"FAIL\"\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.\n- Some versions of Chrome and Node.js will give incorrect results with the\n  following:\n  ```javascript\n  (async function(a) {\n      (function() {\n          var b = await => console.log(\"PASS\");\n          b();\n      })();\n  })().catch(console.error);\n  // Expected: \"PASS\"\n  // Actual:   SyntaxError: Unexpected reserved word\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.\n- Later versions of Chrome and Node.js will give incorrect results with the\n  following:\n  ```javascript\n  try {\n      f();\n      function f() {\n          throw 42;\n      }\n  } catch (e) {\n      console.log(typeof f, e);\n  }\n  // Expected: \"function 42\"\n  // Actual:   \"undefined 42\"\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.\n- Later versions of JavaScript will throw `SyntaxError` with the following:\n  ```javascript\n  \"use strict\";\n  console.log(function f() {\n      return f = \"PASS\";\n  }());\n  // Expected: \"PASS\"\n  // Actual:   TypeError: invalid assignment to const 'f'\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.\n- Adobe ExtendScript will give incorrect results with the following:\n  ```javascript\n  alert(true ? \"PASS\" : false ? \"FAIL\" : null);\n  // Expected: \"PASS\"\n  // Actual:   \"FAIL\"\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.\n- Adobe ExtendScript will give incorrect results with the following:\n  ```javascript\n  alert(42 ? null ? \"FAIL\" : \"PASS\" : \"FAIL\");\n  // Expected: \"PASS\"\n  // Actual:   SyntaxError: Expected: :\n  ```\n  UglifyJS may modify the input which in turn may suppress those errors.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{24/62/2028204bc57435bb59230c6b8fb8b6b2758ab5313464ffde2fc473d158427297f08f74267bb9f1ed3b900fc30abaf9c60c4f3358e67024129fa003b8d6f0 → 6a/f3/92572fee09769406ff6a00b10fdf46100e0df2939389a3e8784b111cb1b17a3c423d81b97d2d9eb8facd9d65f06b7e9aba276e49431caa90691a59aa81b1}

@@ -1251,7 +1251,7 @@
   "dist-tags": {
     "latest": "1.2.1"
   },
-  "_rev": "1993-39afc311a8efd96c",
+  "_rev": "2006-2b122e1d126d1b38",
   "_id": "ieee754",
   "readme": "# ieee754 [![travis][travis-image]][travis-url] [![npm][npm-image]][npm-url] [![downloads][downloads-image]][downloads-url] [![javascript style guide][standard-image]][standard-url]\n\n[travis-image]: https://img.shields.io/travis/feross/ieee754/master.svg\n[travis-url]: https://travis-ci.org/feross/ieee754\n[npm-image]: https://img.shields.io/npm/v/ieee754.svg\n[npm-url]: https://npmjs.org/package/ieee754\n[downloads-image]: https://img.shields.io/npm/dm/ieee754.svg\n[downloads-url]: https://npmjs.org/package/ieee754\n[standard-image]: https://img.shields.io/badge/code_style-standard-brightgreen.svg\n[standard-url]: https://standardjs.com\n\n[![saucelabs][saucelabs-image]][saucelabs-url]\n\n[saucelabs-image]: https://saucelabs.com/browser-matrix/ieee754.svg\n[saucelabs-url]: https://saucelabs.com/u/ieee754\n\n### Read/write IEEE754 floating point numbers from/to a Buffer or array-like object.\n\n## install\n\n```\nnpm install ieee754\n```\n\n## methods\n\n`var ieee754 = require('ieee754')`\n\nThe `ieee754` object has the following functions:\n\n```\nieee754.read = function (buffer, offset, isLE, mLen, nBytes)\nieee754.write = function (buffer, value, offset, isLE, mLen, nBytes)\n```\n\nThe arguments mean the following:\n\n- buffer = the buffer\n- offset = offset into the buffer\n- value = value to set (only for `write`)\n- isLe = is little endian?\n- mLen = mantissa length\n- nBytes = number of bytes\n\n## what is ieee754?\n\nThe IEEE Standard for Floating-Point Arithmetic (IEEE 754) is a technical standard for floating-point computation. [Read more](http://en.wikipedia.org/wiki/IEEE_floating_point).\n\n## license\n\nBSD 3 Clause. Copyright (c) 2008, Fair Oaks Labs, Inc.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{24/74/e2eeb6a253bc73f35cebad55b15dca2dd115e09a753e965a73fd5ddd06ebc16298dc385e3f9214c0d4892354cd8901b297ff49d95e98d53af911144ecbf3 → 6b/9c/1713822bcd0ae28f42c1d579abb719a21641c1f48f27141b6e7c7c9b6bf56b2e02e8d3a0b0d79165d1414d848f572f76ecc44be7a03401377029c84e2b9d}

@@ -2702,7 +2702,7 @@
     "latest": "6.0.6",
     "n-api": "4.0.0-napi"
   },
-  "_rev": "348-58bd7b83777ab100",
+  "_rev": "356-11281bcf64736039",
   "_id": "utf-8-validate",
   "readme": "# utf-8-validate\n\n[![Version npm](https://img.shields.io/npm/v/utf-8-validate.svg?logo=npm)](https://www.npmjs.com/package/utf-8-validate)\n[![Linux/macOS/Windows Build](https://img.shields.io/github/actions/workflow/status/websockets/utf-8-validate/ci.yml?branch=master&label=build&logo=github)](https://github.com/websockets/utf-8-validate/actions?query=workflow%3ACI+branch%3Amaster)\n\nCheck if a buffer contains valid UTF-8 encoded text.\n\n## Installation\n\n```\nnpm install utf-8-validate --save-optional\n```\n\nThe `--save-optional` flag tells npm to save the package in your package.json\nunder the\n[`optionalDependencies`](https://docs.npmjs.com/files/package.json#optionaldependencies)\nkey.\n\n## API\n\nThe module exports a single function that takes one argument. To maximize\nperformance, the argument is not validated. It is the caller's responsibility to\nensure that it is correct.\n\n### `isValidUTF8(buffer)`\n\nChecks whether a buffer contains valid UTF-8.\n\n#### Arguments\n\n- `buffer` - The buffer to check.\n\n#### Return value\n\n`true` if the buffer contains only correct UTF-8, else `false`.\n\n#### Example\n\n```js\n'use strict';\n\nconst isValidUTF8 = require('utf-8-validate');\n\nconst buf = Buffer.from([0xf0, 0x90, 0x80, 0x80]);\n\nconsole.log(isValidUTF8(buf));\n// => true\n```\n\n## License\n\n[MIT](LICENSE)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{33/ee/43905854b12fd24bddd2f9fe63139166dac6fc3de1de49e310323946d7d6296184ebf129a9459690f767cd9dba2f73245d8030ca0063afa864bbb40157ea → 6c/cf/4fa868e66731e9fcc511c1a0417b5ef65167d23b016fa6031a1703b583daf166c8d66b18dfb74464bde824315e04bc5e3d2c33179c7ec303df05b11fcc8a}

@@ -18119,7 +18119,7 @@
   "dist-tags": {
     "latest": "3.972.15"
   },
-  "_rev": "206-95bb9b252b680b87",
+  "_rev": "214-e903f783da7f7b61",
   "_id": "@aws-sdk/credential-provider-http",
   "readme": "# @aws-sdk/credential-provider-http\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/credential-provider-http/latest.svg)](https://www.npmjs.com/package/@aws-sdk/credential-provider-http)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/credential-provider-http.svg)](https://www.npmjs.com/package/@aws-sdk/credential-provider-http)\n\n> An internal transitively required package.\n\n## Usage\n\nSee https://www.npmjs.com/package/@aws-sdk/credential-providers",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{f4/0f/d7cbbcbcfdda55859f77fd98c891783920cea4ce605ab0e5e148cff5f1d64e5eae910c2d4b8c39cecbab3ab1c636b8cb6ce89e4eb72d74b05575121c9dc1 → 6f/87/91462b9e4ec1f874b3a34bbf97f836ce509ee40acc69496fecd10c7bd91c356c764dffeff4f2aeb741ae5c56a8e30a8b3ed649a1576c20e09690af611a5a}

@@ -606,7 +606,7 @@
   "dist-tags": {
     "latest": "4.0.1"
   },
-  "_rev": "2057-dda2587a984b4805",
+  "_rev": "2070-7ae92d4440c96723",
   "_id": "is-stream",
   "readme": "# is-stream\n\n> Check if something is a [Node.js stream](https://nodejs.org/api/stream.html)\n\n## Install\n\n```sh\nnpm install is-stream\n```\n\n## Usage\n\n```js\nimport fs from 'node:fs';\nimport {isStream} from 'is-stream';\n\nisStream(fs.createReadStream('unicorn.png'));\n//=> true\n\nisStream({});\n//=> false\n```\n\n## API\n\n### isStream(stream, options?)\n\nReturns a `boolean` for whether it's a [`Stream`](https://nodejs.org/api/stream.html#stream_stream).\n\n### isWritableStream(stream, options?)\n\nReturns a `boolean` for whether it's a [`stream.Writable`](https://nodejs.org/api/stream.html#stream_class_stream_writable), an [`http.OutgoingMessage`](https://nodejs.org/api/http.html#class-httpoutgoingmessage), an [`http.ServerResponse`](https://nodejs.org/api/http.html#class-httpserverresponse) or an [`http.ClientRequest`](https://nodejs.org/api/http.html#class-httpserverresponse).\n\n### isReadableStream(stream, options?)\n\nReturns a `boolean` for whether it's a [`stream.Readable`](https://nodejs.org/api/stream.html#stream_class_stream_readable) or an [`http.IncomingMessage`](https://nodejs.org/api/http.html#class-httpincomingmessage).\n\n### isDuplexStream(stream, options?)\n\nReturns a `boolean` for whether it's a [`stream.Duplex`](https://nodejs.org/api/stream.html#stream_class_stream_duplex).\n\n### isTransformStream(stream, options?)\n\nReturns a `boolean` for whether it's a [`stream.Transform`](https://nodejs.org/api/stream.html#stream_class_stream_transform).\n\n### Options\n\n#### checkOpen\n\nType: `boolean`\\\nDefault: `true`\n\nWhen this option is `true`, the method returns `false` if the stream has already been closed.\n\n## Related\n\n- [is-file-stream](https://github.com/jamestalmage/is-file-stream) - Detect if a stream is a file stream",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{c0/f5/7752c5dd499bace87b0d84b453da07854ae571a07dae52427d583fe6f7e14414372c03796666f29da46b6755e6d311927498a993f73919198d50c1ef5a4d → 71/5d/2733bc77ce1cf2a875fabe866cba3e2baeccadfb343cfc19fd6fd27ccdc96cd05e14c5e2f63b8b86c36f17e9d24a7bae060b2eede0bb8d061b34ed1ba809}

@@ -13308,7 +13308,7 @@
     "legacy-v6": "6.2.3",
     "legacy-v3": "3.1.5"
   },
-  "_rev": "4297-22427550e4576cf1",
+  "_rev": "4370-70789a3cb6aad6d8",
   "_id": "minimatch",
   "readme": "",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{5c/b8/8847fafb4dee0e94e4b20d422f12730a7b8ac6ef07a53a291e41de96b4674e66257d1aae253151e1da38b69ab9062369b5448f9688f97182de8c6eab40da → 72/35/39f71431205e3d6dca6a2a25b1f2815858b7d1443e3603c0a48b124ef94fbedb82040667bd0e307366a18d24148a8e9584e90a7b34dfd707b5e8a008c937}

@@ -1473,7 +1473,7 @@
   "dist-tags": {
     "latest": "4.0.4"
   },
-  "_rev": "3959-bfb76529896afabc",
+  "_rev": "4027-7b985b3b5dd2fbd2",
   "_id": "balanced-match",
   "readme": "# balanced-match\n\nMatch balanced string pairs, like `{` and `}` or `<b>` and\n`</b>`. Supports regular expressions as well!\n\n## Example\n\nGet the first matching pair of braces:\n\n```js\nimport { balanced } from 'balanced-match'\n\nconsole.log(balanced('{', '}', 'pre{in{nested}}post'))\nconsole.log(balanced('{', '}', 'pre{first}between{second}post'))\nconsole.log(\n  balanced(/\\s+\\{\\s+/, /\\s+\\}\\s+/, 'pre  {   in{nest}   }  post'),\n)\n```\n\nThe matches are:\n\n```bash\n$ node example.js\n{ start: 3, end: 14, pre: 'pre', body: 'in{nested}', post: 'post' }\n{ start: 3,\n  end: 9,\n  pre: 'pre',\n  body: 'first',\n  post: 'between{second}post' }\n{ start: 3, end: 17, pre: 'pre', body: 'in{nest}', post: 'post' }\n```\n\n## API\n\n### const m = balanced(a, b, str)\n\nFor the first non-nested matching pair of `a` and `b` in `str`, return an\nobject with those keys:\n\n- **start** the index of the first match of `a`\n- **end** the index of the matching `b`\n- **pre** the preamble, `a` and `b` not included\n- **body** the match, `a` and `b` not included\n- **post** the postscript, `a` and `b` not included\n\nIf there's no match, `undefined` will be returned.\n\nIf the `str` contains more `a` than `b` / there are unmatched pairs, the first match that was closed will be used. For example, `{{a}` will match `['{', 'a', '']` and `{a}}` will match `['', 'a', '}']`.\n\n### const r = balanced.range(a, b, str)\n\nFor the first non-nested matching pair of `a` and `b` in `str`, return an\narray with indexes: `[ <a index>, <b index> ]`.\n\nIf there's no match, `undefined` will be returned.\n\nIf the `str` contains more `a` than `b` / there are unmatched pairs, the first match that was closed will be used. For example, `{{a}` will match `[ 1, 3 ]` and `{a}}` will match `[0, 2]`.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{ad/a2/4658d763aea213192839b18f0495b4a17b4d5b3d06cd86456ca02cac835e57f85c8d19f5729197475187956c80ab3e1a659f583b326566896e817061690c → 72/3c/d2c4a742742e0a24a0ddfa54ff6c81daa6885830f67e99308842a55e21d66b2901bd4a53744667151b8118583de0a5ce02e86acd115883ebdb361b16fa79}

@@ -5630,7 +5630,7 @@
   "dist-tags": {
     "latest": "3.3.1"
   },
-  "_rev": "206-c952bdf7b6fbffe2",
+  "_rev": "214-c56c8eb410ba6408",
   "_id": "@smithy/util-endpoints",
   "readme": "# @smithy/util-endpoints\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/util-endpoints/latest.svg)](https://www.npmjs.com/package/@smithy/util-endpoints)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/util-endpoints.svg)](https://www.npmjs.com/package/@smithy/util-endpoints)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{71/cc/587c0693b007695254820955017556da01163c1b9b7ea79ddde0bb59aff8c0006f04d2396ec028e05eb529201f9fa11fab3bf52a182165d1c2722e75f71c → 75/98/1bc23690ca5a6794dbda8bc4d4e0d30abe4da8de1a95612eac4cebb34a949653428951ee032754b88ea0bf05ca17fca9e9f414805b1525e33e41154f7d77}

@@ -9224,7 +9224,7 @@
     "patch-4.3": "4.3.5",
     "patch-4.2": "4.2.2"
   },
-  "_rev": "876-9fe567099d3fba03",
+  "_rev": "883-00dec4be657d3abc",
   "_id": "handlebars",
   "readme": "[![CI Build Status](https://github.com/handlebars-lang/handlebars.js/actions/workflows/ci.yml/badge.svg)](https://github.com/handlebars-lang/handlebars.js/actions/workflows/ci.yml)\n[![jsDelivr Hits](https://data.jsdelivr.com/v1/package/npm/handlebars/badge?style=rounded)](https://www.jsdelivr.com/package/npm/handlebars)\n[![npm downloads](https://badgen.net/npm/dm/handlebars)](https://www.npmjs.com/package/handlebars)\n[![npm version](https://badgen.net/npm/v/handlebars)](https://www.npmjs.com/package/handlebars)\n[![Bundle size](https://badgen.net/bundlephobia/minzip/handlebars?label=minified%20%2B%20gzipped)](https://bundlephobia.com/package/handlebars)\n[![Install size](https://packagephobia.com/badge?p=handlebars)](https://packagephobia.com/result?p=handlebars)\n\nHandlebars.js\n=============\n\nHandlebars.js is an extension to the [Mustache templating\nlanguage](https://mustache.github.io/) created by Chris Wanstrath.\nHandlebars.js and Mustache are both logicless templating languages that\nkeep the view and the code separated like we all know they should be.\n\nCheckout the official Handlebars docs site at\n[https://handlebarsjs.com/](https://handlebarsjs.com) and the live demo at [http://tryhandlebarsjs.com/](http://tryhandlebarsjs.com/).\n\nInstalling\n----------\n\nSee our [installation documentation](https://handlebarsjs.com/installation/).\n\nUsage\n-----\nIn general, the syntax of Handlebars.js templates is a superset\nof Mustache templates. For basic syntax, check out the [Mustache\nmanpage](https://mustache.github.io/mustache.5.html).\n\nOnce you have a template, use the `Handlebars.compile` method to compile\nthe template into a function. The generated function takes a context\nargument, which will be used to render the template.\n\n```js\nvar source = \"<p>Hello, my name is {{name}}. I am from {{hometown}}. I have \" +\n             \"{{kids.length}} kids:</p>\" +\n             \"<ul>{{#kids}}<li>{{name}} is {{age}}</li>{{/kids}}</ul>\";\nvar template = Handlebars.compile(source);\n\nvar data = { \"name\": \"Alan\", \"hometown\": \"Somewhere, TX\",\n             \"kids\": [{\"name\": \"Jimmy\", \"age\": \"12\"}, {\"name\": \"Sally\", \"age\": \"4\"}]};\nvar result = template(data);\n\n// Would render:\n// <p>Hello, my name is Alan. I am from Somewhere, TX. I have 2 kids:</p>\n// <ul>\n//   <li>Jimmy is 12</li>\n//   <li>Sally is 4</li>\n// </ul>\n```\n\nFull documentation and more examples are at [handlebarsjs.com](https://handlebarsjs.com/).\n\nPrecompiling Templates\n----------------------\n\nHandlebars allows templates to be precompiled and included as javascript code rather than the handlebars template allowing for faster startup time. Full details are located [here](https://handlebarsjs.com/installation/precompilation.html).\n\nDifferences Between Handlebars.js and Mustache\n----------------------------------------------\nHandlebars.js adds a couple of additional features to make writing\ntemplates easier and also changes a tiny detail of how partials work.\n\n- [Nested Paths](https://handlebarsjs.com/guide/expressions.html#path-expressions)\n- [Helpers](https://handlebarsjs.com/guide/expressions.html#helpers)\n- [Block Expressions](https://handlebarsjs.com/guide/block-helpers.html#basic-blocks)\n- [Literal Values](https://handlebarsjs.com/guide/expressions.html#literal-segments)\n- [Delimited Comments](https://handlebarsjs.com/guide/#template-comments)\n\nBlock expressions have the same syntax as mustache sections but should not be confused with one another. Sections are akin to an implicit `each` or `with` statement depending on the input data and helpers are explicit pieces of code that are free to implement whatever behavior they like. The [mustache spec](https://mustache.github.io/mustache.5.html) defines the exact behavior of sections. In the case of name conflicts, helpers are given priority.\n\n### Compatibility\n\nThere are a few Mustache behaviors that Handlebars does not implement.\n- Handlebars deviates from Mustache slightly in that it does not perform recursive lookup by default. The compile time `compat` flag must be set to enable this functionality. Users should note that there is a performance cost for enabling this flag. The exact cost varies by template, but it's recommended that performance sensitive operations should avoid this mode and instead opt for explicit path references.\n- The optional Mustache-style lambdas are not supported. Instead Handlebars provides its own lambda resolution that follows the behaviors of helpers.\n- Alternative delimiters are not supported.\n\n\nSupported Environments\n----------------------\n\nHandlebars has been designed to work in any ECMAScript 3 environment. This includes\n\n- Node.js\n- Chrome\n- Firefox\n- Safari 5+\n- Opera 11+\n- IE 6+\n\nOlder versions and other runtimes are likely to work but have not been formally\ntested. The compiler requires `JSON.stringify` to be implemented natively or via a polyfill. If using the precompiler this is not necessary.\n\nPerformance\n-----------\n\nIn a rough performance test, precompiled Handlebars.js templates (in\nthe original version of Handlebars.js) rendered in about half the\ntime of Mustache templates. It would be a shame if it were any other\nway, since they were precompiled, but the difference in architecture\ndoes have some big performance advantages. Justin Marney, a.k.a.\n[gotascii](http://github.com/gotascii), confirmed that with an\n[independent test](http://sorescode.com/2010/09/12/benchmarks.html). The\nrewritten Handlebars (current version) is faster than the old version,\nwith many performance tests being 5 to 7 times faster than the Mustache equivalent.\n\n\nUpgrading\n---------\n\nSee [release-notes.md](https://github.com/handlebars-lang/handlebars.js/blob/master/release-notes.md) for upgrade notes.\n\nKnown Issues\n------------\n\nSee [FAQ.md](https://github.com/handlebars-lang/handlebars.js/blob/master/FAQ.md) for known issues and common pitfalls.\n\n\nHandlebars in the Wild\n----------------------\n\n* [Assemble](http://assemble.io), by [@jonschlinkert](https://github.com/jonschlinkert)\n  and [@doowb](https://github.com/doowb), is a static site generator that uses Handlebars.js\n  as its template engine.\n* [Cory](https://github.com/leo/cory), by [@leo](https://github.com/leo), is another tiny static site generator\n* [CoSchedule](http://coschedule.com) An editorial calendar for WordPress that uses Handlebars.js\n* [dashbars](https://github.com/pismute/dashbars) A modern helper library for Handlebars.js.\n* [Ember.js](http://www.emberjs.com) makes Handlebars.js the primary way to\n  structure your views, also with automatic data binding support.\n* [Ghost](https://ghost.org/) Just a blogging platform.\n* [handlebars_assets](http://github.com/leshill/handlebars_assets): A Rails Asset Pipeline gem\n  from Les Hill (@leshill).\n* [handlebars-helpers](https://github.com/assemble/handlebars-helpers) is an extensive library\n  with 100+ handlebars helpers.\n* [handlebars-layouts](https://github.com/shannonmoeller/handlebars-layouts) is a set of helpers which implement extendible and embeddable layout blocks as seen in other popular templating languages.\n* [hbs](http://github.com/donpark/hbs): An Express.js view engine adapter for Handlebars.js,\n  from Don Park.\n* [koa-hbs](https://github.com/jwilm/koa-hbs): [koa](https://github.com/koajs/koa) generator based\n  renderer for Handlebars.js.\n* [jblotus](http://github.com/jblotus) created [http://tryhandlebarsjs.com](http://tryhandlebarsjs.com)\n  for anyone who would like to try out Handlebars.js in their browser.\n* [jQuery plugin](http://71104.github.io/jquery-handlebars/): allows you to use\n  Handlebars.js with [jQuery](http://jquery.com/).\n* [Lumbar](http://walmartlabs.github.io/lumbar) provides easy module-based template management for\n  handlebars projects.\n* [Marionette.Handlebars](https://github.com/hashchange/marionette.handlebars) adds support for Handlebars and Mustache templates to Marionette.\n* [sammy.js](http://github.com/quirkey/sammy) by Aaron Quint, a.k.a. quirkey,\n  supports Handlebars.js as one of its template plugins.\n* [SproutCore](http://www.sproutcore.com) uses Handlebars.js as its main\n  templating engine, extending it with automatic data binding support.\n* [YUI](http://yuilibrary.com/yui/docs/handlebars/) implements a port of handlebars\n* [Swag](https://github.com/elving/swag) by [@elving](https://github.com/elving) is a growing collection of helpers for handlebars.js. Give your handlebars.js templates some swag son!\n* [DOMBars](https://github.com/blakeembrey/dombars) is a DOM-based templating engine built on the Handlebars parser and runtime **DEPRECATED**\n* [promised-handlebars](https://github.com/nknapp/promised-handlebars) is a wrapper for Handlebars that allows helpers to return Promises.\n* [just-handlebars-helpers](https://github.com/leapfrogtechnology/just-handlebars-helpers) A fully tested lightweight package with common Handlebars helpers.\n\nExternal Resources\n------------------\n\n* [Gist about Synchronous and asynchronous loading of external handlebars templates](https://gist.github.com/2287070)\n\nHave a project using Handlebars? Send us a [pull request][pull-request]!\n\nLicense\n-------\nHandlebars.js is released under the MIT license.\n\n[pull-request]: https://github.com/handlebars-lang/handlebars.js/pull/new/master",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{4b/fd/273f1c8d2ae835a73d598f291ddc4b885df01249f5df9f3d7d95a9ab1f3107469160ea152d6e76691fb37bf11c4476bbf0257feeaa2866c2978bddf380ad → 77/df/5032896b0387a27eda44b0860b2209cbbd38ac2c06427f1f90e4bab18b732602e84c7d931a3c73bbd16f33d2dcfcbdbf166d0e25d2e28d35b60768638050}

@@ -3239,7 +3239,7 @@
   "dist-tags": {
     "latest": "7.0.0"
   },
-  "_rev": "269-965a20a174027644",
+  "_rev": "277-2afac99ff0b8176d",
   "_id": "compress-commons",
   "readme": "# Compress Commons\n\nCompress Commons is a library that defines a common interface for working with archive formats within node.\n\n[![NPM](https://nodei.co/npm/compress-commons.png)](https://nodei.co/npm/compress-commons/)\n\n## Install\n\n```bash\nnpm install compress-commons --save\n```\n\nYou can also use `npm install https://github.com/archiverjs/node-compress-commons/archive/master.tar.gz` to test upcoming versions.\n\n## Things of Interest\n\n- [Changelog](https://github.com/archiverjs/node-compress-commons/releases)\n- [Contributing](https://github.com/archiverjs/node-compress-commons/blob/master/CONTRIBUTING.md)\n- [MIT License](https://github.com/archiverjs/node-compress-commons/blob/master/LICENSE-MIT)\n\n## Credits\n\nConcept inspired by [Apache Commons Compress](http://commons.apache.org/proper/commons-compress/)™.\n\nSome logic derived from [Apache Commons Compress](http://commons.apache.org/proper/commons-compress/)™ and [OpenJDK 7](http://openjdk.java.net/).",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{40/97/f0bea445490ec0d6ae290744b3fd81f3d92e4a0ad477014d6210e4419b5d295389cccd555c1d32b9fee136afa746db4cc3aa8747484f8478e5cdd0c5b874 → 78/3d/e1e4b563c856ab6fd93606a1808771ed99f4a98fb8132aa1f91590d9a3b8be4ac1d1bcf5403c00387a9d6c8e1ab74f9dabf6289b550a4dc04f276b37056f}

@@ -695,7 +695,7 @@
   "dist-tags": {
     "latest": "2.1.0"
   },
-  "_rev": "4612-5cd8dbd6a8f83562",
+  "_rev": "4681-3ac568e8955e59fb",
   "_id": "color-name",
   "readme": "A JSON with color names and its values. Based on http://dev.w3.org/csswg/css-color/#named-colors.\n\n[![NPM](https://nodei.co/npm/color-name.png?mini=true)](https://nodei.co/npm/color-name/)\n\n\n```js\nimport colors from 'color-name';\ncolors.red // [255,0,0]\n```\n\n<a href=\"LICENSE\"><img src=\"https://upload.wikimedia.org/wikipedia/commons/0/0c/MIT_logo.svg\" width=\"120\"/></a>",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{3f/93/b399c94ef8d3559db94b9b6b772403a12e7a98d3b172735b8f9354bd70670e0bbb668613d1c3653abbef3384b220195300eb1d586db97cdb3f6d6b2f1821 → 79/d7/37e3bbfb1934d18b48adbf1ea3a736ff21db6d8d17ba50bb6462b73f73365f53667c1b57b9e8918112cb37c6baad41b79cd24aa5f018d80b32559f6babf2}

@@ -6551,7 +6551,7 @@
   "dist-tags": {
     "latest": "4.2.10"
   },
-  "_rev": "214-625cdb0c50d4d012",
+  "_rev": "222-1f2195bc19c788a8",
   "_id": "@smithy/hash-stream-node",
   "readme": "# @smithy/hash-stream-node\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/hash-stream-node/latest.svg)](https://www.npmjs.com/package/@smithy/hash-stream-node)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/hash-stream-node.svg)](https://www.npmjs.com/package/@smithy/hash-stream-node)\n\nA utility for calculating the hash of Node.JS readable streams.\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{c0/7a/2d7dfd9b2587bd8e9f99b88b1c9fdaa22e280c71ca095055a0603e5c1de6fc88136b6d14d9f5d3cdc61987350e7786cf966cf9be488217fe7991373a8d3a → 7b/44/71d30d3e5beec488ecbe8f04e1f0ad25c10dd7e2cd2df79a88acb66f3c5f3080e75c4fcf3479e1cf84672d6948b7781318aef93c204cde3110540f14654a}

@@ -1172,7 +1172,7 @@
   "dist-tags": {
     "latest": "3.3.0"
   },
-  "_rev": "3368-7979a81415aac359",
+  "_rev": "3436-4ffc66e1c56fb00d",
   "_id": "events",
   "readme": "# events [![Build Status](https://travis-ci.org/Gozala/events.png?branch=master)](https://travis-ci.org/Gozala/events)\n\n> Node's event emitter for all engines.\n\nThis implements the Node.js [`events`][node.js docs] module for environments that do not have it, like browsers.\n\n> `events` currently matches the **Node.js 11.13.0** API.\n\nNote that the `events` module uses ES5 features. If you need to support very old browsers like IE8, use a shim like [`es5-shim`](https://www.npmjs.com/package/es5-shim). You need both the shim and the sham versions of `es5-shim`.\n\nThis module is maintained, but only by very few people. If you'd like to help, let us know in the [Maintainer Needed](https://github.com/Gozala/events/issues/43) issue!\n\n## Install\n\nYou usually do not have to install `events` yourself! If your code runs in Node.js, `events` is built in. If your code runs in the browser, bundlers like [browserify](https://github.com/browserify/browserify) or [webpack](https://github.com/webpack/webpack) also include the `events` module.\n\nBut if none of those apply, with npm do:\n\n```\nnpm install events\n```\n\n## Usage\n\n```javascript\nvar EventEmitter = require('events')\n\nvar ee = new EventEmitter()\nee.on('message', function (text) {\n  console.log(text)\n})\nee.emit('message', 'hello world')\n```\n\n## API\n\nSee the [Node.js EventEmitter docs][node.js docs]. `events` currently matches the Node.js 11.13.0 API.\n\n## Contributing\n\nPRs are very welcome! The main way to contribute to `events` is by porting features, bugfixes and tests from Node.js. Ideally, code contributions to this module are copy-pasted from Node.js and transpiled to ES5, rather than reimplemented from scratch. Matching the Node.js code as closely as possible makes maintenance simpler when new changes land in Node.js.\nThis module intends to provide exactly the same API as Node.js, so features that are not available in the core `events` module will not be accepted. Feature requests should instead be directed at [nodejs/node](https://github.com/nodejs/node) and will be added to this module once they are implemented in Node.js.\n\nIf there is a difference in behaviour between Node.js's `events` module and this module, please open an issue!\n\n## License\n\n[MIT](./LICENSE)\n\n[node.js docs]: https://nodejs.org/dist/v11.13.0/docs/api/events.html",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{93/14/833c230ad6196acd3bc5f3d879b1b3a0b586fd1c42706172f4119012d7b8464411775e462a14ce88e4d417f1f4cd92cea3ee780099186008c7112856ef37 → 7c/44/7c992d17d30e5f110a7ddda81a515eedb0be7d854f2e01f5786adaf0fbe033c917b01a8e942db045c3da06ce92dcab70b9142682b010a238b653267a6cc3}

@@ -4366,7 +4366,7 @@
     "latest": "4.2.11",
     "old": "3.0.12"
   },
-  "_rev": "4418-a2759edbab69630a",
+  "_rev": "4485-733f43f2ba3c6985",
   "_id": "graceful-fs",
   "readme": "# graceful-fs\n\ngraceful-fs functions as a drop-in replacement for the fs module,\nmaking various improvements.\n\nThe improvements are meant to normalize behavior across different\nplatforms and environments, and to make filesystem access more\nresilient to errors.\n\n## Improvements over [fs module](https://nodejs.org/api/fs.html)\n\n* Queues up `open` and `readdir` calls, and retries them once\n  something closes if there is an EMFILE error from too many file\n  descriptors.\n* fixes `lchmod` for Node versions prior to 0.6.2.\n* implements `fs.lutimes` if possible. Otherwise it becomes a noop.\n* ignores `EINVAL` and `EPERM` errors in `chown`, `fchown` or\n  `lchown` if the user isn't root.\n* makes `lchmod` and `lchown` become noops, if not available.\n* retries reading a file if `read` results in EAGAIN error.\n\nOn Windows, it retries renaming a file for up to one second if `EACCESS`\nor `EPERM` error occurs, likely because antivirus software has locked\nthe directory.\n\n## USAGE\n\n```javascript\n// use just like fs\nvar fs = require('graceful-fs')\n\n// now go and do stuff with it...\nfs.readFile('some-file-or-whatever', (err, data) => {\n  // Do stuff here.\n})\n```\n\n## Sync methods\n\nThis module cannot intercept or handle `EMFILE` or `ENFILE` errors from sync\nmethods.  If you use sync methods which open file descriptors then you are\nresponsible for dealing with any errors.\n\nThis is a known limitation, not a bug.\n\n## Global Patching\n\nIf you want to patch the global fs module (or any other fs-like\nmodule) you can do this:\n\n```javascript\n// Make sure to read the caveat below.\nvar realFs = require('fs')\nvar gracefulFs = require('graceful-fs')\ngracefulFs.gracefulify(realFs)\n```\n\nThis should only ever be done at the top-level application layer, in\norder to delay on EMFILE errors from any fs-using dependencies.  You\nshould **not** do this in a library, because it can cause unexpected\ndelays in other parts of the program.\n\n## Changes\n\nThis module is fairly stable at this point, and used by a lot of\nthings.  That being said, because it implements a subtle behavior\nchange in a core part of the node API, even modest changes can be\nextremely breaking, and the versioning is thus biased towards\nbumping the major when in doubt.\n\nThe main change between major versions has been switching between\nproviding a fully-patched `fs` module vs monkey-patching the node core\nbuiltin, and the approach by which a non-monkey-patched `fs` was\ncreated.\n\nThe goal is to trade `EMFILE` errors for slower fs operations.  So, if\nyou try to open a zillion files, rather than crashing, `open`\noperations will be queued up and wait for something else to `close`.\n\nThere are advantages to each approach.  Monkey-patching the fs means\nthat no `EMFILE` errors can possibly occur anywhere in your\napplication, because everything is using the same core `fs` module,\nwhich is patched.  However, it can also obviously cause undesirable\nside-effects, especially if the module is loaded multiple times.\n\nImplementing a separate-but-identical patched `fs` module is more\nsurgical (and doesn't run the risk of patching multiple times), but\nalso imposes the challenge of keeping in sync with the core module.\n\nThe current approach loads the `fs` module, and then creates a\nlookalike object that has all the same methods, except a few that are\npatched.  It is safe to use in all versions of Node from 0.8 through\n7.0.\n\n### v4\n\n* Do not monkey-patch the fs module.  This module may now be used as a\n  drop-in dep, and users can opt into monkey-patching the fs builtin\n  if their app requires it.\n\n### v3\n\n* Monkey-patch fs, because the eval approach no longer works on recent\n  node.\n* fixed possible type-error throw if rename fails on windows\n* verify that we *never* get EMFILE errors\n* Ignore ENOSYS from chmod/chown\n* clarify that graceful-fs must be used as a drop-in\n\n### v2.1.0\n\n* Use eval rather than monkey-patching fs.\n* readdir: Always sort the results\n* win32: requeue a file if error has an OK status\n\n### v2.0\n\n* A return to monkey patching\n* wrap process.cwd\n\n### v1.1\n\n* wrap readFile\n* Wrap fs.writeFile.\n* readdir protection\n* Don't clobber the fs builtin\n* Handle fs.read EAGAIN errors by trying again\n* Expose the curOpen counter\n* No-op lchown/lchmod if not implemented\n* fs.rename patch only for win32\n* Patch fs.rename to handle AV software on Windows\n* Close #4 Chown should not fail on einval or eperm if non-root\n* Fix isaacs/fstream#1 Only wrap fs one time\n* Fix #3 Start at 1024 max files, then back off on EMFILE\n* lutimes that doens't blow up on Linux\n* A full on-rewrite using a queue instead of just swallowing the EMFILE error\n* Wrap Read/Write streams as well\n\n### 1.0\n\n* Update engines for node 0.6\n* Be lstat-graceful on Windows\n* first",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{95/87/46195f33ec7620c89e51a71414771b2b50caa79426c462d742616fda454747e89778c606ea4739cf87986345a43a76dcc1bb635aac51436f099ceee76d82 → 7d/66/315d431c9ada543ee38f821523951111756159796b761006ed1b78e32bc21faa92c5a3fd184f2e4d0faf228b6ee7ba6ba842336725323a9120e22604f910}

@@ -1386,7 +1386,7 @@
   "dist-tags": {
     "latest": "5.2.1"
   },
-  "_rev": "203-37d43ffabceebb59",
+  "_rev": "211-5f6cf560aee473c5",
   "_id": "@smithy/chunked-blob-reader",
   "readme": "# @smithy/chunked-blob-reader\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/chunked-blob-reader/latest.svg)](https://www.npmjs.com/package/@smithy/chunked-blob-reader)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/chunked-blob-reader.svg)](https://www.npmjs.com/package/@smithy/chunked-blob-reader)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{1b/54/64acec1c3ed63d43fb1ed122fb112e365d11a3527de6a226fd084538f8921c2292abe926d2c8c15838d790b00fbc48df2831755b2ccfdfaf72e5f831a44c → 7f/09/6cc4a18a0d7c44af4856dfb2d884c19fe35081e0667b80ea2f0a916fdddaacf6a9e6f5bb02f19c854f3aa81292734823037cb271c160e7da8d74963238c6}

@@ -758,7 +758,7 @@
   "dist-tags": {
     "latest": "5.2.1"
   },
-  "_rev": "3968-cae04e16bd9fb374",
+  "_rev": "4035-400130db41c621e6",
   "_id": "safe-buffer",
   "readme": "# safe-buffer [![travis][travis-image]][travis-url] [![npm][npm-image]][npm-url] [![downloads][downloads-image]][downloads-url] [![javascript style guide][standard-image]][standard-url]\n\n[travis-image]: https://img.shields.io/travis/feross/safe-buffer/master.svg\n[travis-url]: https://travis-ci.org/feross/safe-buffer\n[npm-image]: https://img.shields.io/npm/v/safe-buffer.svg\n[npm-url]: https://npmjs.org/package/safe-buffer\n[downloads-image]: https://img.shields.io/npm/dm/safe-buffer.svg\n[downloads-url]: https://npmjs.org/package/safe-buffer\n[standard-image]: https://img.shields.io/badge/code_style-standard-brightgreen.svg\n[standard-url]: https://standardjs.com\n\n#### Safer Node.js Buffer API\n\n**Use the new Node.js Buffer APIs (`Buffer.from`, `Buffer.alloc`,\n`Buffer.allocUnsafe`, `Buffer.allocUnsafeSlow`) in all versions of Node.js.**\n\n**Uses the built-in implementation when available.**\n\n## install\n\n```\nnpm install safe-buffer\n```\n\n## usage\n\nThe goal of this package is to provide a safe replacement for the node.js `Buffer`.\n\nIt's a drop-in replacement for `Buffer`. You can use it by adding one `require` line to\nthe top of your node.js modules:\n\n```js\nvar Buffer = require('safe-buffer').Buffer\n\n// Existing buffer code will continue to work without issues:\n\nnew Buffer('hey', 'utf8')\nnew Buffer([1, 2, 3], 'utf8')\nnew Buffer(obj)\nnew Buffer(16) // create an uninitialized buffer (potentially unsafe)\n\n// But you can use these new explicit APIs to make clear what you want:\n\nBuffer.from('hey', 'utf8') // convert from many types to a Buffer\nBuffer.alloc(16) // create a zero-filled buffer (safe)\nBuffer.allocUnsafe(16) // create an uninitialized buffer (potentially unsafe)\n```\n\n## api\n\n### Class Method: Buffer.from(array)\n<!-- YAML\nadded: v3.0.0\n-->\n\n* `array` {Array}\n\nAllocates a new `Buffer` using an `array` of octets.\n\n```js\nconst buf = Buffer.from([0x62,0x75,0x66,0x66,0x65,0x72]);\n  // creates a new Buffer containing ASCII bytes\n  // ['b','u','f','f','e','r']\n```\n\nA `TypeError` will be thrown if `array` is not an `Array`.\n\n### Class Method: Buffer.from(arrayBuffer[, byteOffset[, length]])\n<!-- YAML\nadded: v5.10.0\n-->\n\n* `arrayBuffer` {ArrayBuffer} The `.buffer` property of a `TypedArray` or\n  a `new ArrayBuffer()`\n* `byteOffset` {Number} Default: `0`\n* `length` {Number} Default: `arrayBuffer.length - byteOffset`\n\nWhen passed a reference to the `.buffer` property of a `TypedArray` instance,\nthe newly created `Buffer` will share the same allocated memory as the\nTypedArray.\n\n```js\nconst arr = new Uint16Array(2);\narr[0] = 5000;\narr[1] = 4000;\n\nconst buf = Buffer.from(arr.buffer); // shares the memory with arr;\n\nconsole.log(buf);\n  // Prints: <Buffer 88 13 a0 0f>\n\n// changing the TypedArray changes the Buffer also\narr[1] = 6000;\n\nconsole.log(buf);\n  // Prints: <Buffer 88 13 70 17>\n```\n\nThe optional `byteOffset` and `length` arguments specify a memory range within\nthe `arrayBuffer` that will be shared by the `Buffer`.\n\n```js\nconst ab = new ArrayBuffer(10);\nconst buf = Buffer.from(ab, 0, 2);\nconsole.log(buf.length);\n  // Prints: 2\n```\n\nA `TypeError` will be thrown if `arrayBuffer` is not an `ArrayBuffer`.\n\n### Class Method: Buffer.from(buffer)\n<!-- YAML\nadded: v3.0.0\n-->\n\n* `buffer` {Buffer}\n\nCopies the passed `buffer` data onto a new `Buffer` instance.\n\n```js\nconst buf1 = Buffer.from('buffer');\nconst buf2 = Buffer.from(buf1);\n\nbuf1[0] = 0x61;\nconsole.log(buf1.toString());\n  // 'auffer'\nconsole.log(buf2.toString());\n  // 'buffer' (copy is not changed)\n```\n\nA `TypeError` will be thrown if `buffer` is not a `Buffer`.\n\n### Class Method: Buffer.from(str[, encoding])\n<!-- YAML\nadded: v5.10.0\n-->\n\n* `str` {String} String to encode.\n* `encoding` {String} Encoding to use, Default: `'utf8'`\n\nCreates a new `Buffer` containing the given JavaScript string `str`. If\nprovided, the `encoding` parameter identifies the character encoding.\nIf not provided, `encoding` defaults to `'utf8'`.\n\n```js\nconst buf1 = Buffer.from('this is a tést');\nconsole.log(buf1.toString());\n  // prints: this is a tést\nconsole.log(buf1.toString('ascii'));\n  // prints: this is a tC)st\n\nconst buf2 = Buffer.from('7468697320697320612074c3a97374', 'hex');\nconsole.log(buf2.toString());\n  // prints: this is a tést\n```\n\nA `TypeError` will be thrown if `str` is not a string.\n\n### Class Method: Buffer.alloc(size[, fill[, encoding]])\n<!-- YAML\nadded: v5.10.0\n-->\n\n* `size` {Number}\n* `fill` {Value} Default: `undefined`\n* `encoding` {String} Default: `utf8`\n\nAllocates a new `Buffer` of `size` bytes. If `fill` is `undefined`, the\n`Buffer` will be *zero-filled*.\n\n```js\nconst buf = Buffer.alloc(5);\nconsole.log(buf);\n  // <Buffer 00 00 00 00 00>\n```\n\nThe `size` must be less than or equal to the value of\n`require('buffer').kMaxLength` (on 64-bit architectures, `kMaxLength` is\n`(2^31)-1`). Otherwise, a [`RangeError`][] is thrown. A zero-length Buffer will\nbe created if a `size` less than or equal to 0 is specified.\n\nIf `fill` is specified, the allocated `Buffer` will be initialized by calling\n`buf.fill(fill)`. See [`buf.fill()`][] for more information.\n\n```js\nconst buf = Buffer.alloc(5, 'a');\nconsole.log(buf);\n  // <Buffer 61 61 61 61 61>\n```\n\nIf both `fill` and `encoding` are specified, the allocated `Buffer` will be\ninitialized by calling `buf.fill(fill, encoding)`. For example:\n\n```js\nconst buf = Buffer.alloc(11, 'aGVsbG8gd29ybGQ=', 'base64');\nconsole.log(buf);\n  // <Buffer 68 65 6c 6c 6f 20 77 6f 72 6c 64>\n```\n\nCalling `Buffer.alloc(size)` can be significantly slower than the alternative\n`Buffer.allocUnsafe(size)` but ensures that the newly created `Buffer` instance\ncontents will *never contain sensitive data*.\n\nA `TypeError` will be thrown if `size` is not a number.\n\n### Class Method: Buffer.allocUnsafe(size)\n<!-- YAML\nadded: v5.10.0\n-->\n\n* `size` {Number}\n\nAllocates a new *non-zero-filled* `Buffer` of `size` bytes.  The `size` must\nbe less than or equal to the value of `require('buffer').kMaxLength` (on 64-bit\narchitectures, `kMaxLength` is `(2^31)-1`). Otherwise, a [`RangeError`][] is\nthrown. A zero-length Buffer will be created if a `size` less than or equal to\n0 is specified.\n\nThe underlying memory for `Buffer` instances created in this way is *not\ninitialized*. The contents of the newly created `Buffer` are unknown and\n*may contain sensitive data*. Use [`buf.fill(0)`][] to initialize such\n`Buffer` instances to zeroes.\n\n```js\nconst buf = Buffer.allocUnsafe(5);\nconsole.log(buf);\n  // <Buffer 78 e0 82 02 01>\n  // (octets will be different, every time)\nbuf.fill(0);\nconsole.log(buf);\n  // <Buffer 00 00 00 00 00>\n```\n\nA `TypeError` will be thrown if `size` is not a number.\n\nNote that the `Buffer` module pre-allocates an internal `Buffer` instance of\nsize `Buffer.poolSize` that is used as a pool for the fast allocation of new\n`Buffer` instances created using `Buffer.allocUnsafe(size)` (and the deprecated\n`new Buffer(size)` constructor) only when `size` is less than or equal to\n`Buffer.poolSize >> 1` (floor of `Buffer.poolSize` divided by two). The default\nvalue of `Buffer.poolSize` is `8192` but can be modified.\n\nUse of this pre-allocated internal memory pool is a key difference between\ncalling `Buffer.alloc(size, fill)` vs. `Buffer.allocUnsafe(size).fill(fill)`.\nSpecifically, `Buffer.alloc(size, fill)` will *never* use the internal Buffer\npool, while `Buffer.allocUnsafe(size).fill(fill)` *will* use the internal\nBuffer pool if `size` is less than or equal to half `Buffer.poolSize`. The\ndifference is subtle but can be important when an application requires the\nadditional performance that `Buffer.allocUnsafe(size)` provides.\n\n### Class Method: Buffer.allocUnsafeSlow(size)\n<!-- YAML\nadded: v5.10.0\n-->\n\n* `size` {Number}\n\nAllocates a new *non-zero-filled* and non-pooled `Buffer` of `size` bytes.  The\n`size` must be less than or equal to the value of\n`require('buffer').kMaxLength` (on 64-bit architectures, `kMaxLength` is\n`(2^31)-1`). Otherwise, a [`RangeError`][] is thrown. A zero-length Buffer will\nbe created if a `size` less than or equal to 0 is specified.\n\nThe underlying memory for `Buffer` instances created in this way is *not\ninitialized*. The contents of the newly created `Buffer` are unknown and\n*may contain sensitive data*. Use [`buf.fill(0)`][] to initialize such\n`Buffer` instances to zeroes.\n\nWhen using `Buffer.allocUnsafe()` to allocate new `Buffer` instances,\nallocations under 4KB are, by default, sliced from a single pre-allocated\n`Buffer`. This allows applications to avoid the garbage collection overhead of\ncreating many individually allocated Buffers. This approach improves both\nperformance and memory usage by eliminating the need to track and cleanup as\nmany `Persistent` objects.\n\nHowever, in the case where a developer may need to retain a small chunk of\nmemory from a pool for an indeterminate amount of time, it may be appropriate\nto create an un-pooled Buffer instance using `Buffer.allocUnsafeSlow()` then\ncopy out the relevant bits.\n\n```js\n// need to keep around a few small chunks of memory\nconst store = [];\n\nsocket.on('readable', () => {\n  const data = socket.read();\n  // allocate for retained data\n  const sb = Buffer.allocUnsafeSlow(10);\n  // copy the data into the new allocation\n  data.copy(sb, 0, 0, 10);\n  store.push(sb);\n});\n```\n\nUse of `Buffer.allocUnsafeSlow()` should be used only as a last resort *after*\na developer has observed undue memory retention in their applications.\n\nA `TypeError` will be thrown if `size` is not a number.\n\n### All the Rest\n\nThe rest of the `Buffer` API is exactly the same as in node.js.\n[See the docs](https://nodejs.org/api/buffer.html).\n\n\n## Related links\n\n- [Node.js issue: Buffer(number) is unsafe](https://github.com/nodejs/node/issues/4660)\n- [Node.js Enhancement Proposal: Buffer.from/Buffer.alloc/Buffer.zalloc/Buffer() soft-deprecate](https://github.com/nodejs/node-eps/pull/4)\n\n## Why is `Buffer` unsafe?\n\nToday, the node.js `Buffer` constructor is overloaded to handle many different argument\ntypes like `String`, `Array`, `Object`, `TypedArrayView` (`Uint8Array`, etc.),\n`ArrayBuffer`, and also `Number`.\n\nThe API is optimized for convenience: you can throw any type at it, and it will try to do\nwhat you want.\n\nBecause the Buffer constructor is so powerful, you often see code like this:\n\n```js\n// Convert UTF-8 strings to hex\nfunction toHex (str) {\n  return new Buffer(str).toString('hex')\n}\n```\n\n***But what happens if `toHex` is called with a `Number` argument?***\n\n### Remote Memory Disclosure\n\nIf an attacker can make your program call the `Buffer` constructor with a `Number`\nargument, then they can make it allocate uninitialized memory from the node.js process.\nThis could potentially disclose TLS private keys, user data, or database passwords.\n\nWhen the `Buffer` constructor is passed a `Number` argument, it returns an\n**UNINITIALIZED** block of memory of the specified `size`. When you create a `Buffer` like\nthis, you **MUST** overwrite the contents before returning it to the user.\n\nFrom the [node.js docs](https://nodejs.org/api/buffer.html#buffer_new_buffer_size):\n\n> `new Buffer(size)`\n>\n> - `size` Number\n>\n> The underlying memory for `Buffer` instances created in this way is not initialized.\n> **The contents of a newly created `Buffer` are unknown and could contain sensitive\n> data.** Use `buf.fill(0)` to initialize a Buffer to zeroes.\n\n(Emphasis our own.)\n\nWhenever the programmer intended to create an uninitialized `Buffer` you often see code\nlike this:\n\n```js\nvar buf = new Buffer(16)\n\n// Immediately overwrite the uninitialized buffer with data from another buffer\nfor (var i = 0; i < buf.length; i++) {\n  buf[i] = otherBuf[i]\n}\n```\n\n\n### Would this ever be a problem in real code?\n\nYes. It's surprisingly common to forget to check the type of your variables in a\ndynamically-typed language like JavaScript.\n\nUsually the consequences of assuming the wrong type is that your program crashes with an\nuncaught exception. But the failure mode for forgetting to check the type of arguments to\nthe `Buffer` constructor is more catastrophic.\n\nHere's an example of a vulnerable service that takes a JSON payload and converts it to\nhex:\n\n```js\n// Take a JSON payload {str: \"some string\"} and convert it to hex\nvar server = http.createServer(function (req, res) {\n  var data = ''\n  req.setEncoding('utf8')\n  req.on('data', function (chunk) {\n    data += chunk\n  })\n  req.on('end', function () {\n    var body = JSON.parse(data)\n    res.end(new Buffer(body.str).toString('hex'))\n  })\n})\n\nserver.listen(8080)\n```\n\nIn this example, an http client just has to send:\n\n```json\n{\n  \"str\": 1000\n}\n```\n\nand it will get back 1,000 bytes of uninitialized memory from the server.\n\nThis is a very serious bug. It's similar in severity to the\n[the Heartbleed bug](http://heartbleed.com/) that allowed disclosure of OpenSSL process\nmemory by remote attackers.\n\n\n### Which real-world packages were vulnerable?\n\n#### [`bittorrent-dht`](https://www.npmjs.com/package/bittorrent-dht)\n\n[Mathias Buus](https://github.com/mafintosh) and I\n([Feross Aboukhadijeh](http://feross.org/)) found this issue in one of our own packages,\n[`bittorrent-dht`](https://www.npmjs.com/package/bittorrent-dht). The bug would allow\nanyone on the internet to send a series of messages to a user of `bittorrent-dht` and get\nthem to reveal 20 bytes at a time of uninitialized memory from the node.js process.\n\nHere's\n[the commit](https://github.com/feross/bittorrent-dht/commit/6c7da04025d5633699800a99ec3fbadf70ad35b8)\nthat fixed it. We released a new fixed version, created a\n[Node Security Project disclosure](https://nodesecurity.io/advisories/68), and deprecated all\nvulnerable versions on npm so users will get a warning to upgrade to a newer version.\n\n#### [`ws`](https://www.npmjs.com/package/ws)\n\nThat got us wondering if there were other vulnerable packages. Sure enough, within a short\nperiod of time, we found the same issue in [`ws`](https://www.npmjs.com/package/ws), the\nmost popular WebSocket implementation in node.js.\n\nIf certain APIs were called with `Number` parameters instead of `String` or `Buffer` as\nexpected, then uninitialized server memory would be disclosed to the remote peer.\n\nThese were the vulnerable methods:\n\n```js\nsocket.send(number)\nsocket.ping(number)\nsocket.pong(number)\n```\n\nHere's a vulnerable socket server with some echo functionality:\n\n```js\nserver.on('connection', function (socket) {\n  socket.on('message', function (message) {\n    message = JSON.parse(message)\n    if (message.type === 'echo') {\n      socket.send(message.data) // send back the user's message\n    }\n  })\n})\n```\n\n`socket.send(number)` called on the server, will disclose server memory.\n\nHere's [the release](https://github.com/websockets/ws/releases/tag/1.0.1) where the issue\nwas fixed, with a more detailed explanation. Props to\n[Arnout Kazemier](https://github.com/3rd-Eden) for the quick fix. Here's the\n[Node Security Project disclosure](https://nodesecurity.io/advisories/67).\n\n\n### What's the solution?\n\nIt's important that node.js offers a fast way to get memory otherwise performance-critical\napplications would needlessly get a lot slower.\n\nBut we need a better way to *signal our intent* as programmers. **When we want\nuninitialized memory, we should request it explicitly.**\n\nSensitive functionality should not be packed into a developer-friendly API that loosely\naccepts many different types. This type of API encourages the lazy practice of passing\nvariables in without checking the type very carefully.\n\n#### A new API: `Buffer.allocUnsafe(number)`\n\nThe functionality of creating buffers with uninitialized memory should be part of another\nAPI. We propose `Buffer.allocUnsafe(number)`. This way, it's not part of an API that\nfrequently gets user input of all sorts of different types passed into it.\n\n```js\nvar buf = Buffer.allocUnsafe(16) // careful, uninitialized memory!\n\n// Immediately overwrite the uninitialized buffer with data from another buffer\nfor (var i = 0; i < buf.length; i++) {\n  buf[i] = otherBuf[i]\n}\n```\n\n\n### How do we fix node.js core?\n\nWe sent [a PR to node.js core](https://github.com/nodejs/node/pull/4514) (merged as\n`semver-major`) which defends against one case:\n\n```js\nvar str = 16\nnew Buffer(str, 'utf8')\n```\n\nIn this situation, it's implied that the programmer intended the first argument to be a\nstring, since they passed an encoding as a second argument. Today, node.js will allocate\nuninitialized memory in the case of `new Buffer(number, encoding)`, which is probably not\nwhat the programmer intended.\n\nBut this is only a partial solution, since if the programmer does `new Buffer(variable)`\n(without an `encoding` parameter) there's no way to know what they intended. If `variable`\nis sometimes a number, then uninitialized memory will sometimes be returned.\n\n### What's the real long-term fix?\n\nWe could deprecate and remove `new Buffer(number)` and use `Buffer.allocUnsafe(number)` when\nwe need uninitialized memory. But that would break 1000s of packages.\n\n~~We believe the best solution is to:~~\n\n~~1. Change `new Buffer(number)` to return safe, zeroed-out memory~~\n\n~~2. Create a new API for creating uninitialized Buffers. We propose: `Buffer.allocUnsafe(number)`~~\n\n#### Update\n\nWe now support adding three new APIs:\n\n- `Buffer.from(value)` - convert from any type to a buffer\n- `Buffer.alloc(size)` - create a zero-filled buffer\n- `Buffer.allocUnsafe(size)` - create an uninitialized buffer with given size\n\nThis solves the core problem that affected `ws` and `bittorrent-dht` which is\n`Buffer(variable)` getting tricked into taking a number argument.\n\nThis way, existing code continues working and the impact on the npm ecosystem will be\nminimal. Over time, npm maintainers can migrate performance-critical code to use\n`Buffer.allocUnsafe(number)` instead of `new Buffer(number)`.\n\n\n### Conclusion\n\nWe think there's a serious design issue with the `Buffer` API as it exists today. It\npromotes insecure software by putting high-risk functionality into a convenient API\nwith friendly \"developer ergonomics\".\n\nThis wasn't merely a theoretical exercise because we found the issue in some of the\nmost popular npm packages.\n\nFortunately, there's an easy fix that can be applied today. Use `safe-buffer` in place of\n`buffer`.\n\n```js\nvar Buffer = require('safe-buffer').Buffer\n```\n\nEventually, we hope that node.js core can switch to this new, safer behavior. We believe\nthe impact on the ecosystem would be minimal since it's not a breaking change.\nWell-maintained, popular packages would be updated to use `Buffer.alloc` quickly, while\nolder, insecure packages would magically become safe from this attack vector.\n\n\n## links\n\n- [Node.js PR: buffer: throw if both length and enc are passed](https://github.com/nodejs/node/pull/4514)\n- [Node Security Project disclosure for `ws`](https://nodesecurity.io/advisories/67)\n- [Node Security Project disclosure for`bittorrent-dht`](https://nodesecurity.io/advisories/68)\n\n\n## credit\n\nThe original issues in `bittorrent-dht`\n([disclosure](https://nodesecurity.io/advisories/68)) and\n`ws` ([disclosure](https://nodesecurity.io/advisories/67)) were discovered by\n[Mathias Buus](https://github.com/mafintosh) and\n[Feross Aboukhadijeh](http://feross.org/).\n\nThanks to [Adam Baldwin](https://github.com/evilpacket) for helping disclose these issues\nand for his work running the [Node Security Project](https://nodesecurity.io/).\n\nThanks to [John Hiesey](https://github.com/jhiesey) for proofreading this README and\nauditing the code.\n\n\n## license\n\nMIT. Copyright (C) [Feross Aboukhadijeh](http://feross.org)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{2c/bc/c4f6497f6c07210366300a6c31d9df1a7c8cce9b38fd20728974bd67c12ff6240404f69233eefc5e0d51f2bd70ee9a6f38b05319f0153b56061578903dfa → 7f/cc/38e6adfcacb265cd5f2eeef224ace23ab5085704a341252d540545075748be39a5b1bbc9129362d145f13ae498af2bddb2cbb89c540878c1d0f9663dd1f0}

@@ -6469,7 +6469,7 @@
   "dist-tags": {
     "latest": "4.2.10"
   },
-  "_rev": "218-0a54251b643a6259",
+  "_rev": "226-d217aa4cdf6a2e72",
   "_id": "@smithy/util-waiter",
   "readme": "# @smithy/util-waiter\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/util-waiter/latest.svg)](https://www.npmjs.com/package/@smithy/util-waiter)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/util-waiter.svg)](https://www.npmjs.com/package/@smithy/util-waiter)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{d6/2a/dbf09a02cedf3b742f2443bee80e55dd2777e3f23db59e75c29c031feb48ba704373abbd5864fbd294f860f0f4a3481a1435d048484cfe19691c3166327b → 81/35/e340cd0680ce86d3b7167bf43d7411b6bb6fe33c5713d33f1ab7a07e3390fc28a6aec2a539e252d1effe76af565590d11469f16098a341ed1ac9534f79a8}

@@ -3074,7 +3074,7 @@
   "dist-tags": {
     "latest": "3.1.3"
   },
-  "_rev": "4665-46ec965fb68209e9",
+  "_rev": "4733-25c510ab9f84e46e",
   "_id": "color-convert",
   "readme": "# color-convert\n\nColor-convert is a color conversion library for JavaScript and node.\nIt converts all ways between `rgb`, `hsl`, `hsv`, `hwb`, `cmyk`, `ansi`, `ansi16`, `hex` strings, and CSS `keyword`s (will round to closest):\n\n```js\nimport convert from 'color-convert';\n\nconvert.rgb.hsl(140, 200, 100);             // [96, 48, 59]\nconvert.keyword.rgb('blue');                // [0, 0, 255]\n\nconst rgbChannels = convert.rgb.channels;     // 3\nconst cmykChannels = convert.cmyk.channels;   // 4\nconst ansiChannels = convert.ansi16.channels; // 1\n```\n\n# Install\n\n```sh\nnpm install color-convert\n```\n\n# API\n\nSimply get the property of the _from_ and _to_ conversion that you're looking for.\n\nAll functions have a rounded and unrounded variant. By default, return values are rounded. To get the unrounded (raw) results, simply tack on `.raw` to the function.\n\nAll 'from' functions have a hidden property called `.channels` that indicates the number of channels the function expects (not including alpha).\n\n```js\nimport convert from 'color-convert';\n\n// Hex to LAB\nconvert.hex.lab('DEADBF');         // [ 76, 21, -2 ]\nconvert.hex.lab.raw('DEADBF');     // [ 75.56213190997677, 20.653827952644754, -2.290532499330533 ]\n\n// RGB to CMYK\nconvert.rgb.cmyk(167, 255, 4);     // [ 35, 0, 98, 0 ]\nconvert.rgb.cmyk.raw(167, 255, 4); // [ 34.509803921568626, 0, 98.43137254901961, 0 ]\n```\n\n### Arrays\nAll functions that accept multiple arguments also support passing an array.\n\nNote that this does **not** apply to functions that convert from a color that only requires one value (e.g. `keyword`, `ansi256`, `hex`, etc.)\n\n```js\nimport convert from 'color-convert';\n\nconvert.rgb.hex(123, 45, 67);      // '7B2D43'\nconvert.rgb.hex([123, 45, 67]);    // '7B2D43'\n```\n\n## Routing\n\nConversions that don't have an _explicitly_ defined conversion (in [conversions.js](conversions.js)), but can be converted by means of sub-conversions (e.g. XYZ -> **RGB** -> CMYK), are automatically routed together. This allows just about any color model supported by `color-convert` to be converted to any other model, so long as a sub-conversion path exists. This is also true for conversions requiring more than one step in between (e.g. LCH -> **LAB** -> **XYZ** -> **RGB** -> Hex).\n\nKeep in mind that extensive conversions _may_ result in a loss of precision, and exist only to be complete. For a list of \"direct\" (single-step) conversions, see [conversions.js](conversions.js).\n\n## Color Space Scales\nConversions rely on an agreed upon 'full-scale' value for each of the channels. Listed here are those values for the most common color spaces\n\n### rgb\nchannel | full-scale value\n---|---\nr | 255\ng | 255\nb | 255\n\n### hsl\nchannel | full-scale value\n---|---\nh | 360\ns | 100\nl | 100\n\n### hsv\nchannel | full-scale value\n---|---\nh | 360\ns | 100\nv | 100\n\n### hwb\nchannel | full-scale value\n---|---\nh | 360\nw | 100\nb | 100\n\n### xyz\nchannel | full-scale value\n---|---\nx | 94\ny | 99\nz | 108\n\n### lab\nchannel | full-scale value\n---|---\nl | 100\na | -86, 98\nb | -108, 94\n\n### lch\nchannel | full-scale value\n---|---\nl | 100\nc | 133\nh | 360\n\n### oklab\nchannel | full-scale value\n---|---\nl | 100\na | -23, 28\nb | -31, 20\n\n### oklch\nchannel | full-scale value\n---|---\nl | 100\nc | 32\nh | 360\n\n### cmyk\nchannel | full-scale value\n---|---\nc | 100\nm | 100\ny | 100\nk | 100\n\n### hex\nchannel | full-scale value\n---|---\nhex | ```0xffffff```\n\n### keyword\nchannel | value\n---|---\nname | any key from [color-name](https://github.com/colorjs/color-name/blob/master/index.js)\n\n### apple\nchannel | full-scale value\n---|---\n0 | 65535\n1 | 65535\n2 | 65535\n\n### gray\nchannel | full-scale value\n---|---\ngray | 100\n\n# Contribute\n\nIf there is a new model you would like to support, or want to add a direct conversion between two existing models, please send us a pull request.\n\n# License\nCopyright © 2011-2016, Heather Arthur.\nCopyright © 2016-2021, Josh Junon.\n\nLicensed under the [MIT License](LICENSE).",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{65/88/cf0b4cd3498c1b0af36849d5106b0571b3ead903265515faff2e3169ca5e0d12fb7d8af585106ef5daa74eee27a2ac4bfe8038d15149a94fa741e3481902 → 8b/0d/a77c9924fbfcbc69b8321ee7e76fc0d4991c5c1430823091eceed09c7ad66b7eab9b2d00915dc9a6d1234ac882af999c2e133a8b376648ecf0288d4b8e77}

@@ -4551,7 +4551,7 @@
     "latest": "7.0.6",
     "6x": "6.0.6"
   },
-  "_rev": "4135-479c269a7101ce13",
+  "_rev": "4202-ad07ab5eaead4a1d",
   "_id": "cross-spawn",
   "readme": "",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{c9/73/bda61dbcf868e1717c8162019e419e0692929c4f79fd6377283acee26b67947c72c9731ab5124b072b61141a238fb0747f9db7894f1c35415e66c5835110 → 8c/01/ee9131812f0711f941bd3eef1599c016bbdda304790a219dcc268f78532573559b832630884cfea2380c76313c042083288e5036daff07653d2de4f08091}

@@ -372,7 +372,7 @@
   "dist-tags": {
     "latest": "2.0.4"
   },
-  "_rev": "4644-d61c57c9e6829b4b",
+  "_rev": "4712-a27b543e655d65df",
   "_id": "inherits",
   "readme": "Browser-friendly inheritance fully compatible with standard node.js\n[inherits](http://nodejs.org/api/util.html#util_util_inherits_constructor_superconstructor).\n\nThis package exports standard `inherits` from node.js `util` module in\nnode environment, but also provides alternative browser-friendly\nimplementation through [browser\nfield](https://gist.github.com/shtylman/4339901). Alternative\nimplementation is a literal copy of standard one located in standalone\nmodule to avoid requiring of `util`. It also has a shim for old\nbrowsers with no `Object.create` support.\n\nWhile keeping you sure you are using standard `inherits`\nimplementation in node.js environment, it allows bundlers such as\n[browserify](https://github.com/substack/node-browserify) to not\ninclude full `util` package to your client code if all you need is\njust `inherits` function. It worth, because browser shim for `util`\npackage is large and `inherits` is often the single function you need\nfrom it.\n\nIt's recommended to use this package instead of\n`require('util').inherits` for any code that has chances to be used\nnot only in node.js but in browser too.\n\n## usage\n\n```js\nvar inherits = require('inherits');\n// then use exactly as the standard one\n```\n\n## note on version ~1.0\n\nVersion ~1.0 had completely different motivation and is not compatible\nneither with 2.0 nor with standard node.js `inherits`.\n\nIf you are using version ~1.0 and planning to switch to ~2.0, be\ncareful:\n\n* new version uses `super_` instead of `super` for referencing\n  superclass\n* new version overwrites current prototype while old one preserves any\n  existing fields on it",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{d7/7d/47aafa5259e8926b3743d5b526e2c5f4c4785ab95725f6802a276b59555dd82b45e36c58533ff13a250e066f93684cce60766efa8bfb8230225de2588e8b → 8c/c7/693c0cff1d79108da3391ca6639884de95c71bfe0f95b477d05441e0ff796106d03d3efa4d81b7498c7f4be9b5e0749c52fdee6be0cbd08c4bb44211a659}

@@ -165,7 +165,7 @@
   "dist-tags": {
     "latest": "1.0.2"
   },
-  "_rev": "1845-7afe7098cef6deb7",
+  "_rev": "1862-9b56ca5acfa08cf1",
   "_id": "util-deprecate",
   "readme": "util-deprecate\n==============\n### The Node.js `util.deprecate()` function with browser support\n\nIn Node.js, this module simply re-exports the `util.deprecate()` function.\n\nIn the web browser (i.e. via browserify), a browser-specific implementation\nof the `util.deprecate()` function is used.\n\n\n## API\n\nA `deprecate()` function is the only thing exposed by this module.\n\n``` javascript\n// setup:\nexports.foo = deprecate(foo, 'foo() is deprecated, use bar() instead');\n\n\n// users see:\nfoo();\n// foo() is deprecated, use bar() instead\nfoo();\nfoo();\n```\n\n\n## License\n\n(The MIT License)\n\nCopyright (c) 2014 Nathan Rajlich <nathan@tootallnate.net>\n\nPermission is hereby granted, free of charge, to any person\nobtaining a copy of this software and associated documentation\nfiles (the \"Software\"), to deal in the Software without\nrestriction, including without limitation the rights to use,\ncopy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the\nSoftware is furnished to do so, subject to the following\nconditions:\n\nThe above copyright notice and this permission notice shall be\nincluded in all copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND,\nEXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES\nOF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND\nNONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT\nHOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,\nWHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING\nFROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR\nOTHER DEALINGS IN THE SOFTWARE.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{0b/f6/98e2a12bacc0737f41392a0a9284a387a315060f5841b1be6a5cdd18efbf0c6e31ef731dd3e06c481920964cb5b1047e824cfed6912113e9d95cff764940 → 8f/32/5918d0e44fec7145b3b5e5ff9826f6ca60df75dcbb44d257d2abeb2a9e318d79d7d994bfac8ad66345bd04abf1228b6afd2b6c8e138ad0a49a3cfb209e94}

@@ -6448,7 +6448,7 @@
   "dist-tags": {
     "latest": "4.2.10"
   },
-  "_rev": "217-483b2138a37e0b89",
+  "_rev": "225-5af4ea3b7a7d2c2c",
   "_id": "@smithy/hash-node",
   "readme": "# @smithy/md5-node\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/hash-node/latest.svg)](https://www.npmjs.com/package/@smithy/hash-node)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/hash-node.svg)](https://www.npmjs.com/package/@smithy/hash-node)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{9d/77/d46752cd8c5899a7e5bad641f5253dc48e8cec256a09b44ebe447a987a262f47659e31596708fb4ffca0c4c4841d34ca4ca2fe2d1cc007a6b342db3258c4 → 93/95/7b203aecce0fbc86e4cec25dba8f3f2c4a8d321d5c0733e2a01e3f7705fa3aaba6a1f0c0c63d68077d365c4edee983563eda5e2353ebe64fcc98f03decd5}

@@ -19530,7 +19530,7 @@
     "gamma": "1.0.0-gamma.8",
     "rc": "1.0.0-rc.10"
   },
-  "_rev": "320-1808b665469c19e6",
+  "_rev": "328-67be2c762c33c3f7",
   "_id": "@aws-sdk/middleware-ssec",
   "readme": "# @aws-sdk/middleware-ssec\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/middleware-ssec/latest.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-ssec)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/middleware-ssec.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-ssec)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{9c/f4/8ca593196217cec502aa235edb8e44a9ff7406e20dffbe763049570731e2c37f0992a9eed69cfb71bd3fe57b3c81f8ec9be30d2c03782a0f4220394d1024 → 93/be/50a9c064bf75dbc02b258ee90be5e07aad29494d67d08a7e7364e98e4791b055e0ee71e4d6494918fc820bd70d1277f480f3e9011b9aeaf5ff185e9d8ba1}

@@ -6383,7 +6383,7 @@
   "dist-tags": {
     "latest": "4.2.10"
   },
-  "_rev": "218-4817fd368f034654",
+  "_rev": "226-f04909e7cb91aef2",
   "_id": "@smithy/md5-js",
   "readme": "# @smithy/md5-js\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/md5-js/latest.svg)](https://www.npmjs.com/package/@smithy/md5-js)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/md5-js.svg)](https://www.npmjs.com/package/@smithy/md5-js)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{17/fa/effe7b71126d573e8280fd76ddb13089418ef414211eaee1345e5b3359fde17ecf707c5312544a6a06d75047c68fdffb89f8dd7a639a9fda3ffcac52f4da → 94/e2/bc3879cb2c68b460f9eaacf7e6ccf7bbbd930ac5da4fbf2acb20033f35b3c243d9385cc1096dbcb85a5185d49fdc5098e40515397035698d69bfc1a9dd02}

@@ -154,7 +154,7 @@
   "dist-tags": {
     "latest": "1.0.1"
   },
-  "_rev": "395-da48d06360d96eab",
+  "_rev": "408-c2299eecddec241d",
   "_id": "events-universal",
   "readme": "# events-universal\n\nUniversal wrapper for the Node.js `events` module.\n\n```\nnpm i events-universal\n```\n\n## Usage\n\n```js\nconst EventEmitter = require('events-universal')\n```\n\n## License\n\nApache-2.0",
   "_attachments": {}