mrs-toolbox-cli 8.1.4-21be8fb → 8.1.4-5ab6718

package/npm-cache/_cacache/content-v2/sha512/{0c/8e/6005d8fed58a499b4433a2938544fac7d2b8440fd8b129daac12b697b7014e2a86f208492af96a2764c967f37baa2e47a5f99bb95f87f7231baded36f40e → 37/a0/b097f74a79de63556d617b471185cdd013ef4b4e68c78f6fe4215d548eef7052f7244054b3e106c6c33df29afbd1c692ce38ffec4977de925734139dde39}

@@ -9206,12 +9206,112 @@
       },
       "_hasShrinkwrap": false,
       "contributors": []
+    },
+    "3.930.0": {
+      "name": "@aws-sdk/xml-builder",
+      "version": "3.930.0",
+      "description": "XML builder for the AWS SDK",
+      "dependencies": {
+        "@smithy/types": "^4.9.0",
+        "fast-xml-parser": "5.2.5",
+        "tslib": "^2.6.2"
+      },
+      "scripts": {
+        "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
+        "build:cjs": "node ../../scripts/compilation/inline xml-builder",
+        "build:es": "tsc -p tsconfig.es.json",
+        "build:include:deps": "lerna run --scope $npm_package_name --include-dependencies build",
+        "build:types": "tsc -p tsconfig.types.json",
+        "build:types:downlevel": "downlevel-dts dist-types dist-types/ts3.4",
+        "clean": "rimraf ./dist-* && rimraf *.tsbuildinfo",
+        "test": "yarn g:vitest run",
+        "test:watch": "yarn g:vitest watch"
+      },
+      "sideEffects": false,
+      "author": {
+        "name": "AWS SDK for JavaScript Team",
+        "url": "https://aws.amazon.com/javascript/"
+      },
+      "license": "Apache-2.0",
+      "main": "./dist-cjs/index.js",
+      "module": "./dist-es/index.js",
+      "types": "./dist-types/index.d.ts",
+      "engines": {
+        "node": ">=18.0.0"
+      },
+      "typesVersions": {
+        "<4.0": {
+          "dist-types/*": [
+            "dist-types/ts3.4/*"
+          ]
+        }
+      },
+      "browser": {
+        "./dist-es/xml-parser": "./dist-es/xml-parser.browser"
+      },
+      "react-native": {
+        "./dist-es/xml-parser": "./dist-es/xml-parser",
+        "./dist-cjs/xml-parser": "./dist-cjs/xml-parser"
+      },
+      "homepage": "https://github.com/aws/aws-sdk-js-v3/tree/main/packages/xml-builder",
+      "repository": {
+        "type": "git",
+        "url": "git+https://github.com/aws/aws-sdk-js-v3.git",
+        "directory": "packages/xml-builder"
+      },
+      "devDependencies": {
+        "@tsconfig/recommended": "1.0.1",
+        "concurrently": "7.0.0",
+        "downlevel-dts": "0.10.1",
+        "rimraf": "3.0.2",
+        "typescript": "~5.8.3"
+      },
+      "_id": "@aws-sdk/xml-builder@3.930.0",
+      "bugs": {
+        "url": "https://github.com/aws/aws-sdk-js-v3/issues"
+      },
+      "_nodeVersion": "20.19.5",
+      "_npmVersion": "11.6.2",
+      "dist": {
+        "integrity": "sha512-YIfkD17GocxdmlUVc3ia52QhcWuRIUJonbF8A2CYfcWNV3HzvAqpcPeC0bYUhkK+8e8YO1ARnLKZQE0TlwzorA==",
+        "shasum": "949a35219ca52cc769ffbfbf38f3324178ba74f9",
+        "tarball": "https://verdaccio.mrsdev.ru/@aws-sdk%2fxml-builder/-/xml-builder-3.930.0.tgz",
+        "fileCount": 29,
+        "unpackedSize": 27490,
+        "signatures": [
+          {
+            "keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U",
+            "sig": "MEUCIFOqJSgywITzugrG5x36k2LU4cv5Nvh6b25+dHdQzVFXAiEAxeJmBNKiIGb+GmiaaxE7uCVKSGDcVQMcpcAivMJbmQw="
+          }
+        ]
+      },
+      "_npmUser": {
+        "name": "aws-sdk-bot",
+        "email": "aws-sdk-js-automation@amazon.com"
+      },
+      "directories": {},
+      "maintainers": [
+        {
+          "name": "amzn-oss",
+          "email": "osa-3p@amazon.com"
+        },
+        {
+          "name": "aws-sdk-bot",
+          "email": "aws-sdk-js-automation@amazon.com"
+        }
+      ],
+      "_npmOperationalInternal": {
+        "host": "s3://npm-registry-packages-npm-production",
+        "tmp": "tmp/xml-builder_3.930.0_1762979305119_0.38204842214224577"
+      },
+      "_hasShrinkwrap": false,
+      "contributors": []
     }
   },
   "time": {
     "created": "2018-11-19T23:21:57.018Z",
     "0.1.0-preview.1": "2018-11-19T23:21:57.300Z",
-    "modified": "2025-10-30T19:13:52.470Z",
+    "modified": "2025-11-12T20:28:25.494Z",
     "0.1.0-preview.2": "2019-07-12T18:54:24.720Z",
     "0.1.0-preview.3": "2019-09-09T17:34:03.964Z",
     "1.0.0-alpha.1": "2020-01-08T03:07:37.557Z",
@@ -9306,18 +9406,19 @@
     "3.910.0": "2025-10-14T19:02:12.505Z",
     "3.911.0": "2025-10-15T19:05:43.561Z",
     "3.914.0": "2025-10-21T20:04:46.285Z",
-    "3.921.0": "2025-10-30T19:13:52.249Z"
+    "3.921.0": "2025-10-30T19:13:52.249Z",
+    "3.930.0": "2025-11-12T20:28:25.309Z"
   },
   "users": {},
   "dist-tags": {
     "preview": "0.1.0-preview.3",
-    "latest": "3.921.0",
+    "latest": "3.930.0",
     "alpha": "1.0.0-alpha.5",
     "beta": "1.0.0-beta.2",
     "gamma": "1.0.0-gamma.8",
     "rc": "1.0.0-rc.8"
   },
-  "_rev": "216-bf3b66b9039dcb9b",
+  "_rev": "217-b6f8322a8d08ac84",
   "_id": "@aws-sdk/xml-builder",
   "readme": "# @aws-sdk/xml-builder\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/xml-builder/latest.svg)](https://www.npmjs.com/package/@aws-sdk/xml-builder)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/xml-builder.svg)](https://www.npmjs.com/package/@aws-sdk/xml-builder)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{de/93/b953776b3a127cc46d733ec325da18e2ca6e83d7ac047564cb21744f626357cd7e48a1e6bee443c30a74b81eb51726542562fbeae1f77401c4b6da67bf34 → 37/fc/e89b213da2fe829f5355f6eb3b57f3ee489e1694765ecd035d89d18a4448570966a9685c483cddfa98a1580961407b38e4d1d59ed5c8d36421b5d210455e}

@@ -1831,7 +1831,7 @@
   "dist-tags": {
     "latest": "7.0.1"
   },
-  "_rev": "176-54d42deeb379b340",
+  "_rev": "177-8fa2df1025d1be20",
   "_id": "crc32-stream",
   "readme": "# CRC32 Stream\n\ncrc32-stream is a streaming CRC32 checksumer. It uses the [crc](https://www.npmjs.org/package/crc) module behind the scenes to reliably handle binary data and fancy character sets. Data is passed through untouched.\n\n### Install\n\n```bash\nnpm install crc32-stream --save\n```\n\nYou can also use `npm install https://github.com/archiverjs/node-crc32-stream/archive/master.tar.gz` to test upcoming versions.\n\n### Usage\n\n#### CRC32Stream\n\nInherits [Transform Stream](http://nodejs.org/api/stream.html#stream_class_stream_transform) options and methods.\n\n```js\nimport { CRC32Stream } from \"crc32-stream\";\n\nconst source = fs.createReadStream(\"file.txt\");\nconst checksum = new CRC32Stream();\n\nchecksum.on(\"end\", function (err) {\n  // do something with checksum.digest() here\n});\n\n// either pipe it\nsource.pipe(checksum);\n\n// or write it\nchecksum.write(\"string\");\nchecksum.end();\n```\n\n#### DeflateCRC32Stream\n\nInherits [zlib.DeflateRaw](http://nodejs.org/api/zlib.html#zlib_class_zlib_deflateraw) options and methods.\n\n```js\nimport { DeflateCRC32Stream } from \"crc32-stream\";\n\nconst source = fs.createReadStream(\"file.txt\");\nconst checksum = new DeflateCRC32Stream();\n\nchecksum.on(\"end\", function (err) {\n  // do something with checksum.digest() here\n});\n\n// either pipe it\nsource.pipe(checksum);\n\n// or write it\nchecksum.write(\"string\");\nchecksum.end();\n```\n\n### Instance API\n\n#### digest()\n\nReturns the checksum digest in unsigned form.\n\n#### hex()\n\nReturns the hexadecimal representation of the checksum digest. (ie E81722F0)\n\n#### size(compressed)\n\nReturns the raw size/length of passed-through data.\n\nIf `compressed` is `true`, it returns compressed length instead. (DeflateCRC32Stream)\n\n## Things of Interest\n\n- [Changelog](https://github.com/archiverjs/node-crc32-stream/releases)\n- [Contributing](https://github.com/archiverjs/node-crc32-stream/blob/master/CONTRIBUTING.md)\n- [MIT License](https://github.com/archiverjs/node-crc32-stream/blob/master/LICENSE-MIT)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{f6/22/9675cdbb30ad87d176e9dc7db7bc1fe992084876ac551560276462fac5a4e5ba9fddea5173b4e33c91cc46e396412f4bd0748d71b3b77ccac9ba1a51a280 → 39/e8/f8bf8d115edc43e7b366386dd296a10b6c5c3825c91963e8cb43d21dec5203a41895d6af87dea833c0b6bf1a86a646bf22e09c99fe4a5ec7a4bfbdf9a5a6}

@@ -2879,7 +2879,7 @@
   "dist-tags": {
     "latest": "5.6.5"
   },
-  "_rev": "177-baca3ba75ba7d3e2",
+  "_rev": "179-c3f78fc49cc113a6",
   "_id": "@js-joda/core",
   "readme": "# Immutable date and time library for JavaScript\n\n[![npm version](https://badge.fury.io/js/%40js-joda%2Fcore.svg)](https://badge.fury.io/js/%40js-joda%2Fcore)\n[![GH Actions Build Status](https://github.com/js-joda/js-joda/actions/workflows/tests.yaml/badge.svg?branch=main)](https://github.com/js-joda/js-joda/actions)\n[![Sauce Test Status](https://saucelabs.com/buildstatus/js-joda)](https://saucelabs.com/u/js-joda)\n[![Coverage Status](https://coveralls.io/repos/js-joda/js-joda/badge.svg?branch=main&service=github)](https://coveralls.io/github/js-joda/js-joda?branch=main)\n[![Downloads/Month](https://img.shields.io/npm/dm/%40js-joda%2Fcore.svg)](https://img.shields.io/npm/dm/%40js-joda%2Fcore.svg)\n\n[![Sauce Browser Matrix](https://saucelabs.com/browser-matrix/js-joda.svg?branch=main&42)](https://saucelabs.com/u/js-joda)\n\n## Introduction\n\n**js-joda** is an **immutable date and time library** for JavaScript. It provides a **simple, domain-driven and clean API** based on the ISO calendar system, which is the de facto world calendar following the proleptic Gregorian rules.\n\n- js-joda has a lightweight footprint, only **43 kB minified and compressed**, no third party dependencies.\n\n- js-joda is **fast**. It is about 2 to 10 times faster than other JavaScript date libraries.\n\n- js-joda comes with built-in parsers/ formatters for ISO 8601 as specified in RFC 3339, that can be easily customized.\n\n- js-joda supports **ECMAScript 5** browsers down to IE11.\n\n- js-joda is a **port of the threeten** backport, which is the base for JSR-310 implementation of the Java SE 8 java.time package. Threeten is inspired by **Joda-Time**, having similar concepts and the same author.\n\n- js-joda is **robust and stable**. We ported more then 1700 test-cases with a lots of test-permutations from the threetenbp project. We run the automated karma test-suite against Firefox, Chrome, Node and phantomjs.\n\n## Why yet another JavaScript date and time library?\n\n- Popular JavaScript date libraries like [moment](https://momentjs.com/) or [date-utils](https://github.com/continuouscalendar/dateutils) are **wrappers** around the native JavaScript `Date` object, providing syntactic sugar. The native `Date` object always consist of a date, time and a timezone part. In contrast, js-joda is a **standalone** date and time implementation.\n\n- The API has a **domain-driven design** with classes for each of the different use cases, like `LocalDate`, `ZonedDateTime` or `Period`. For example, `LocalDate` allows you to handle dates without times (like birthdays or holidays) in a clean and error-safe way, especially if these dates are persisted to an external server.\n\n- js-joda is **immutable**. Immutability aligns well with pure functions and with the architecture of frameworks like React and Flux.\n\n## The ThreeTen domain models\n\n### Dates and Times\n\n- **LocalDate** represents a date without a time and timezone in the ISO-8601 calendar system, such as 2007-12-24.\n\n- **LocalTime** represents a time without timezone in the ISO-8601 calendar system such as '11:55:00'.\n\n- **LocalDateTime** is a description of the date (LocalDate), as used for birthdays, combined with the local time (LocalTime) as seen on a wall clock.\n\n- **ZonedDateTime** is a date-time with a timezone in the ISO-8601 calendar system, such as 2007-12-24T16:15:30+01:00 UTC+01:00.\n\n- **Instant** is an instantaneous point on the time-line measured from the epoch of _1970-01-01T00:00:00Z_ in epoch-seconds and nanosecond-of-second.\n\n### Duration and Period\n\n- **Duration** is a time-based amount of time, such as '34.5 seconds'.\n\n- **Period** is a date-based amount of time in the ISO-8601 calendar system, such as '2 years, 3 months and 4 days'.\n\n### Additional value types\n\n- **Year** represents a year in the ISO-8601 calendar system, such as '2016'.\n\n- **YearMonth** represents a year and a month in the ISO-8601 calendar system, such as '2016-01'.\n\n- **Month** represents a month-of-year in the ISO-8601 calendar system, such as 'July'.\n\n- **MonthDay** represents a month-day in the ISO-8601 calendar system, such as '--12-03'. Could be used to represent e.g. Birthdays.\n\n- **DayOfWeek** represents a day-of-week in the ISO-8601 calendar system, such as 'Tuesday'.\n\n## Getting started\n\n### Node\n\nInstall joda using npm\n\n```\nnpm install @js-joda/core\n```\n\nThen require it to any module\n\n```js\nvar LocalDate = require('@js-joda/core').LocalDate;\n\nvar d = LocalDate.parse('2012-12-24').atStartOfDay().plusMonths(2); // 2013-02-24T00:00:00\n```\n\n### Browser\n\nTo use js-joda from a browser, download either `dist/js-joda.min.js` or `dist/js-joda.js` (with sourcemaps for development). Then add it as a script tag to your page\n\n```html\n<script src=\"js-joda.min.js\"></script>\n<script>\n    var LocalDate = JSJoda.LocalDate;\n    var d = LocalDate.parse('2012-12-24').atStartOfDay().plusMonths(2); // 2013-02-24T00:00:00\n</script>\n```\n\n## js-joda packages\n\njs-joda consist of four packages:\n\n|  package name | description  |  path |\n|---|---|---|\n| `@js-joda/core` | Implementation of the ThreeTen Classes and API | [/packages/core](//github.com/js-joda/js-joda/tree/main/packages/core) |\n| `@js-joda/timezone` | Implementation of timezone calculation based on the iana Time Zone Database | [/packages/timezone](//github.com/js-joda/js-joda/tree/main/packages/timezone) |\n| `@js-joda/locale` | Implementation of locale specific functionality for js-joda, especially for formatting and parsing locale specific dates | [/packages/locale](//github.com/js-joda/js-joda/tree/main/packages/locale) |\n| `@js-joda/extra` | Implementation of the ThreeTen-Extra Classes and API |[/packages/extra](//github.com/js-joda/js-joda/tree/main/packages/extra) |\n\nThe [@js-joda/examples](//github.com/js-joda/js-joda/tree/main/packages/examples) package is for testing the different build artifacts in different context, like webpack, browser node, etc.\n\n## Documentation\n\n- [js-joda Quick start guide](//js-joda.github.io/js-joda/manual/getting-started.html) Quick start guide and examples\n- [API](//js-joda.github.io/js-joda/identifiers.html) ESDoc generated API documentation\n\n## Contributing\n\nContributions are always welcome. Before contributing please read the [code of conduct](http://contributor-covenant.org/version/1/4/) &\nsearch the issue tracker. We use GitHub issues. Your issue may have already been discussed or fixed. To contribute, fork js-joda, commit your changes, & send a pull request.\n\nBy contributing to js-joda, you agree that your contributions will be licensed under its BSD license.\n\nNote that only pull requests and issues that match the threeten backport API will be considered. Additional requested features will be rejected.\n\n## License\n\n- `js-joda` is released under the [BSD 3-clause license](//github.com/js-joda/js-joda/blob/main/LICENSE).\n\n- `js-joda` uses the ThreeTen-Backport implementation (http://www.threeten.org/threetenbp/) as a reference base for implementation. This allows us to release js-joda under the BSD License while the OpenJDK java.time implementation is under GNU GPL+linking exception. The API of the ThreeTen-Backport is mostly identical to the official Java SE 8 API from the view of our JavaScript port.\n\n- Our implementation reference base ThreeTen-Backport (http://www.threeten.org/threetenbp/) is also released under the BSD 3-clause license\n\n- `OpenJDK` is under GNU GPL+linking exception.\n\n- The author of `Joda-Time` and the lead architect of the JSR-310 is Stephen Colebourne.\n\nThe API of this project (as far as possible with JavaScript), a lot of implementation details and documentation\nare just copied but never equalled.\n\n## Roadmap\n\n### Milestone 1: Core domains (reached with version v1.0.0)\n\n- Support for the domain models `LocalDate`, `LocalDateTime`, `ZonedDateTime`, `Instant`, `Duration` and `Period` converting to and from ISO8601.\n- `ZonedDateTime` (without support for loading iana timezone databases) currently supports only fixed offsets like UTC or UTC+02:00 and the system default time zone.\n\n### Milestone 2: IANA timezone support (reached with version v1.2.0)\n\n- Add IANA timezone database support to js-joda. Implement handling of daylight saving transitions, mainly in `ZonedDateTime`.\n- For access to the IANA timezone database, the plugin [@js-joda/timezone](//github.com/js-joda/js-joda/tree/main/packages/timezone) is required. It provides an implementation of the [ZoneRulesProvider](//js-joda.github.io/js-joda/class/packages/core/src/zone/ZoneRulesProvider.js~ZoneRulesProvider.html) and contains the iana timezone database.\n\n### Milestone 3: Locale support (reached with v2.0.0 of @js-joda/locale)\n\n- Add locale support.\n- Extend pattern parser/ formatter for text with locale support.\n\nsee the plugin [@js-joda/locale](//github.com/js-joda/js-joda/tree/main/packages/locale)\n\n### Future Milestones\n\n- Reduce library size by removing redundant code, especially by refactoring code for formatting/ parsing dates.\n- Increase test coverage (ongoing task)\n- Cleanup documentation (ongoing task)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{58/c9/0f4d737112d622ed43063628573a3ffb89f80779a759a9a4de65760a8bb0e36fc3279d6c577ac77bd33bd7e1b6f347b67ea39d4dfbd1bb16d32384640101 → 3a/69/741e744384731310664b9412add9afd2d63c6104a35daba03552f70f178052c69dda321bdaadd75e0c9135eeffc3c498735b7e7383987c18906f7cdac87e}

@@ -1807,7 +1807,7 @@
   "dist-tags": {
     "latest": "6.2.2"
   },
-  "_rev": "2837-1e692d2091fbad91",
+  "_rev": "2867-0cf6ec466a020e49",
   "_id": "ansi-regex",
   "readme": "",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{88/82/1a8294c178cabc0b8f2e7657679bd683b4b417a325f3d90c065e44b110a9bdb2263853ef3894c5b62daf8f3b54347f7ca1029e7246ece6e89af100fe55c4 → 3a/ad/822129f36b36af9cd93bd5c3fe3dbf1fecc7e466cf0293cc848478f898166f51567a634a7bb6bf43acf2c5e71261ba3df6c71250888c80d443247a2fc80f}

@@ -7980,7 +7980,7 @@
   "dist-tags": {
     "latest": "5.3.6"
   },
-  "_rev": "129-62f39a69c182938a",
+  "_rev": "130-3e5639e65e504a95",
   "_id": "@smithy/fetch-http-handler",
   "readme": "# @smithy/fetch-http-handler\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/fetch-http-handler/latest.svg)](https://www.npmjs.com/package/@smithy/fetch-http-handler)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/fetch-http-handler.svg)](https://www.npmjs.com/package/@smithy/fetch-http-handler)\n\nThis is the default `requestHandler` used for browser applications.\nSince Node.js introduced experimental Web Streams API in v16.5.0 and made it stable in v21.0.0,\nyou can consider using `fetch-http-handler` in Node.js, although it's not recommended.\n\nFor the Node.js default `requestHandler` implementation, see instead\n[`@smithy/node-http-handler`](https://www.npmjs.com/package/@smithy/node-http-handler).",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{a6/7c/c3f56b6bc08cc95d59c46e72f53007108a6825c0fdfdfb00545f7275598a702fb6077421d02ae279d628dcf4178a127915f863d3beca746ecfeda6b82f40 → 3b/9d/fb6d655c8e37603c7b541b45ad5bd8904966c7b60b610effe0483e1195e23b2b92938b477672a006789a0d25c7dd8eb617d78c910e86b438519579be4ba6}

@@ -2670,7 +2670,7 @@
     "latest": "6.0.2",
     "next": "5.0.0-beta.0"
   },
-  "_rev": "633-08539eae16425386",
+  "_rev": "641-beaea8a72253a9ec",
   "_id": "event-target-shim",
   "readme": "# event-target-shim\n\n[![npm version](https://img.shields.io/npm/v/event-target-shim.svg)](https://www.npmjs.com/package/event-target-shim)\n[![Downloads/month](https://img.shields.io/npm/dm/event-target-shim.svg)](http://www.npmtrends.com/event-target-shim)\n[![Build Status](https://github.com/mysticatea/event-target-shim/workflows/CI/badge.svg)](https://github.com/mysticatea/event-target-shim/actions)\n[![Coverage Status](https://codecov.io/gh/mysticatea/event-target-shim/branch/master/graph/badge.svg)](https://codecov.io/gh/mysticatea/event-target-shim)\n[![Dependency Status](https://david-dm.org/mysticatea/event-target-shim.svg)](https://david-dm.org/mysticatea/event-target-shim)\n\nAn implementation of [WHATWG `EventTarget` interface](https://dom.spec.whatwg.org/#interface-eventtarget) and [WHATWG `Event` interface](https://dom.spec.whatwg.org/#interface-event). This implementation supports constructor, `passive`, `once`, and `signal`.\n\nThis implementation is designed ...\n\n- Working fine on both browsers and Node.js.\n- TypeScript friendly.\n\n## 💿 Installation\n\nUse [npm](https://www.npmjs.com/) or a compatible tool.\n\n```\nnpm install event-target-shim\n```\n\n## 📖 Getting started\n\n```js\nimport { EventTarget, Event } from \"event-target-shim\";\n\n// constructor (was added to the standard on 8 Jul 2017)\nconst myNode = new EventTarget();\n\n// passive flag (was added to the standard on 6 Jan 2016)\nmyNode.addEventListener(\n  \"hello\",\n  (e) => {\n    e.preventDefault(); // ignored and print warning on console.\n  },\n  { passive: true }\n);\n\n// once flag (was added to the standard on 15 Apr 2016)\nmyNode.addEventListener(\"hello\", listener, { once: true });\nmyNode.dispatchEvent(new Event(\"hello\")); // remove the listener after call.\n\n// signal (was added to the standard on 4 Dec 2020)\nconst ac = new AbortController();\nmyNode.addEventListener(\"hello\", listener, { signal: ac.signal });\nac.abort(); // remove the listener.\n```\n\n- For browsers, use a bundler such as [Webpack](https://webpack.js.org/) to bundle.\n  - If you want to support IE11, use `import {} from \"event-target-shim/es5\"` instead. It's a transpiled code by babel. It depends on `@baebl/runtime` (`^7.12.0`) package.\n- The `AbortController` class was added to the standard on 14 Jul 2017. If you want the shim of that, use [abort-controller](https://www.npmjs.com/package/abort-controller) package.\n\n## 📚 API Reference\n\nSee [docs/reference.md](docs/reference.md).\n\n## 💥 Migrating to v6\n\nSee [docs/migrating-to-v6.md](docs/migrating-to-v6.md).\n\n## 📰 Changelog\n\nSee [GitHub releases](https://github.com/mysticatea/event-target-shim/releases).\n\n## 🍻 Contributing\n\nContributing is welcome ❤️\n\nPlease use GitHub issues/PRs.\n\n### Development tools\n\n- `npm install` installs dependencies for development.\n- `npm test` runs tests and measures code coverage.\n- `npm run watch:mocha` runs tests on each file change.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{41/fd/81ec58272c328ac03ef7a41abd82c009338ca1d11742fbbd085337624a75a92d56989a4c34de8b53fba7b8f2b516e462c68d2b54dfaad5fbb3cb1648f1bd → 3b/c0/62ecbb9f9ec4b5ac7079cbe4fd4718ff2b7daf123868941987fe6f23d30d9972d1f8c36faaf853fdf9f84eaf67dd346d0293b3cdbaa1105f125d26635a4b}

@@ -6128,7 +6128,7 @@
   "dist-tags": {
     "latest": "4.2.5"
   },
-  "_rev": "128-d7e9c56a6bf16af3",
+  "_rev": "129-2459d1d75055a8ba",
   "_id": "@smithy/middleware-serde",
   "readme": "# @smithy/middleware-serde\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/middleware-serde/latest.svg)](https://www.npmjs.com/package/@smithy/middleware-serde)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/middleware-serde.svg)](https://www.npmjs.com/package/@smithy/middleware-serde)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{97/01/154e23ce58ac9db802e5e1a1df69713c79741cf033ddcbacf41433123682903810a06ad3d3bece36bd8f1db1f9ab80e7e44995820132dd45ae3c35ffbbee → 3e/9d/ba3515585d2bd13ed34fed2d1510ce380c19514d8aa2439f28231fd391a9d99503769d13ea56a82339fa24c6e7d7ff92a631647e342db343734847569bd9}

@@ -758,7 +758,7 @@
   "dist-tags": {
     "latest": "5.2.1"
   },
-  "_rev": "2776-c35fa41e8d8df3ed",
+  "_rev": "2806-6d0e1b578fc2e356",
   "_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/{db/d8/d8ff5530d5cfb26151612c57c02e7cc8d487a1b6de10dcca53b9771733bb686b5fafbfe3180ab549e2f22db48332f344009e4af3e7b2abdbf9bc472f3ecf → 3f/a2/eba49bf7dee8d9f648626ea1384655c79a131325a364e2402c9420d761c696b19079060c4588bd62bf88d2b42bfdade91b2578f18f0f96afa9b48b17f817}

@@ -5479,7 +5479,7 @@
   "dist-tags": {
     "latest": "4.2.5"
   },
-  "_rev": "127-db5a375dfb5907a9",
+  "_rev": "128-16fcec801a3219c9",
   "_id": "@smithy/querystring-parser",
   "readme": "# @smithy/querystring-parser\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/querystring-parser/latest.svg)](https://www.npmjs.com/package/@smithy/querystring-parser)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/querystring-parser.svg)](https://www.npmjs.com/package/@smithy/querystring-parser)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{c1/14/0c1df51053a6ef3f41e11fda3e53d3049e85953517d6fc7dc3871d86b39f9cf719cf133126393d25946a944b67b4db909eef988dde8e327dc90982b45a9b → 42/1d/15017ec32a559d157f92e4be2e7a2e82c5a625fb47f1662ca204dd1b5d363e514966715cb07a487fd108eab0f368a477d391d20da8579d03df0f59d9c8f5}

@@ -1855,7 +1855,7 @@
     "latest": "7.1.2",
     "version6": "6.0.1"
   },
-  "_rev": "2857-d72723dbdd3573ed",
+  "_rev": "2888-193f3dd53288cc82",
   "_id": "strip-ansi",
   "readme": "",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{8c/d5/5c609fce55bb31f78fc1df2ea65799b4978435d7e3436cf160c3c9b691a854c90c877f05bacb3bdaf32550effbfd12f9fbad3cab7867c1550a10ed6d5998 → 42/ef/8441c231c26c8c4b992440f80fa58cb49180219ea1dd4894b7c56f5359a89ae59c9760433559ad8156cfd58b1e6b2cd5a8da7eb0b68d8c73a7dad9c46493}

@@ -5349,7 +5349,7 @@
     "latest": "3.893.0",
     "rc": "1.0.0-rc.8"
   },
-  "_rev": "223-44091d8399bb8d4c",
+  "_rev": "224-c2ead69de6d73786",
   "_id": "@aws-sdk/util-arn-parser",
   "readme": "# @aws-sdk/util-arn-parser\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/util-arn-parser/latest.svg)](https://www.npmjs.com/package/@aws-sdk/util-arn-parser)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/util-arn-parser.svg)](https://www.npmjs.com/package/@aws-sdk/util-arn-parser)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{26/a7/f1a26ef8c0ed56cdc4ff6449cd6564ff73e9d114d0a982f1f5bd8511df9ee31365f243d90280bdb1589aec1164f513a6fc26458dd0aea9c5f70a4b332d1c → 46/49/449fb707af9b5811e3ed2d9d5eab40a4f7b28069c976efaba215d857cce87079ef929f601a0498306645b39c1ebbb33afd8b0368eb6cd050f02e8d74be6a}

@@ -154,7 +154,7 @@
   "dist-tags": {
     "latest": "1.0.1"
   },
-  "_rev": "184-41bc8a541394f9bf",
+  "_rev": "191-c0092aeb732eb544",
   "_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": {}

package/npm-cache/_cacache/content-v2/sha512/{29/2e/ebc36d6ecfcb254cc69f4213df09b0aaaa03dcd2dee799173b7917f888b47ea85df9931c3c0a6e59e2b3ecbeae6700df1bdbd1577cebd9911e64c5f49e23 → 48/8a/f1b6d7bdc55f33de4b9fcf70c4a194168215f2f5e7760f217ccb8cca07ac9f68ffe0d086819a0fd7d0c5cb1f0d01d09b1230d6c52bbe4e57b04cec263827}

@@ -5939,7 +5939,7 @@
   "dist-tags": {
     "latest": "4.2.5"
   },
-  "_rev": "130-fff4697cc7edab51",
+  "_rev": "131-b3b9ea90ba7b3621",
   "_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/{1a/26/56416326f3c7cd99f6555431a2ccd53adeea858dda2bfee5efb35e27e0cc6eeff5ae5b0feaab6d13efa0d3666e1cbb7d42de99897c484e483f66586dda34 → 4c/df/a45d8936e336be0399e5c8747b6fde4d7a543202555e8083b8ab51a9ea6fde5304c6cba4191d9d0d83774712bc7d7bda68be9539674c8c9863c8d575bc64}

@@ -1255,7 +1255,7 @@
     "latest": "3.0.0",
     "next": "3.0.0"
   },
-  "_rev": "641-b984c1276bbb9eee",
+  "_rev": "649-8277372420163dd7",
   "_id": "abort-controller",
   "readme": "# abort-controller\n\n[![npm version](https://img.shields.io/npm/v/abort-controller.svg)](https://www.npmjs.com/package/abort-controller)\n[![Downloads/month](https://img.shields.io/npm/dm/abort-controller.svg)](http://www.npmtrends.com/abort-controller)\n[![Build Status](https://travis-ci.org/mysticatea/abort-controller.svg?branch=master)](https://travis-ci.org/mysticatea/abort-controller)\n[![Coverage Status](https://codecov.io/gh/mysticatea/abort-controller/branch/master/graph/badge.svg)](https://codecov.io/gh/mysticatea/abort-controller)\n[![Dependency Status](https://david-dm.org/mysticatea/abort-controller.svg)](https://david-dm.org/mysticatea/abort-controller)\n\nAn implementation of [WHATWG AbortController interface](https://dom.spec.whatwg.org/#interface-abortcontroller).\n\n```js\nimport AbortController from \"abort-controller\"\n\nconst controller = new AbortController()\nconst signal = controller.signal\n\nsignal.addEventListener(\"abort\", () => {\n    console.log(\"aborted!\")\n})\n\ncontroller.abort()\n```\n\n> https://jsfiddle.net/1r2994qp/1/\n\n## 💿 Installation\n\nUse [npm](https://www.npmjs.com/) to install then use a bundler.\n\n```\nnpm install abort-controller\n```\n\nOr download from [`dist` directory](./dist).\n\n- [dist/abort-controller.mjs](dist/abort-controller.mjs) ... ES modules version.\n- [dist/abort-controller.js](dist/abort-controller.js) ... Common JS version.\n- [dist/abort-controller.umd.js](dist/abort-controller.umd.js) ... UMD (Universal Module Definition) version. This is transpiled by [Babel](https://babeljs.io/) for IE 11.\n\n## 📖 Usage\n\n### Basic\n\n```js\nimport AbortController from \"abort-controller\"\n// or\nconst AbortController = require(\"abort-controller\")\n\n// or UMD version defines a global variable:\nconst AbortController = window.AbortControllerShim\n```\n\nIf your bundler recognizes `browser` field of `package.json`, the imported `AbortController` is the native one and it doesn't contain shim (even if the native implementation was nothing).\nIf you wanted to polyfill `AbortController` for IE, use `abort-controller/polyfill`.\n\n### Polyfilling\n\nImporting `abort-controller/polyfill` assigns the `AbortController` shim to the `AbortController` global variable if the native implementation was nothing.\n\n```js\nimport \"abort-controller/polyfill\"\n// or\nrequire(\"abort-controller/polyfill\")\n```\n\n### API\n\n#### AbortController\n\n> https://dom.spec.whatwg.org/#interface-abortcontroller\n\n##### controller.signal\n\nThe [AbortSignal](https://dom.spec.whatwg.org/#interface-AbortSignal) object which is associated to this controller.\n\n##### controller.abort()\n\nNotify `abort` event to listeners that the `signal` has.\n\n## 📰 Changelog\n\n- See [GitHub releases](https://github.com/mysticatea/abort-controller/releases).\n\n## 🍻 Contributing\n\nContributing is welcome ❤️\n\nPlease use GitHub issues/PRs.\n\n### Development tools\n\n- `npm install` installs dependencies for development.\n- `npm test` runs tests and measures code coverage.\n- `npm run clean` removes temporary files of tests.\n- `npm run coverage` opens code coverage of the previous test with your default browser.\n- `npm run lint` runs ESLint.\n- `npm run build` generates `dist` codes.\n- `npm run watch` runs tests on each file change.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{81/23/4ed0915beb3ea5a3a105c667bb4bfc460fa47e22181b8c5f9574147d83db644bd636269bf4d1631890b2fffee772fb04f73519feb159743df10e1349d7a0 → 4e/11/a333fcbc4b991d1c6011367464a3093b3d23b48f158250d855841ed65defaf232744c8904372c07c229f21d67e5f75449f7ff2d21d750e3f38d279868c7f}

@@ -4811,7 +4811,7 @@
   "dist-tags": {
     "latest": "4.2.5"
   },
-  "_rev": "128-f8d482c219f13dd5",
+  "_rev": "129-3820168bb8bde1cf",
   "_id": "@smithy/middleware-stack",
   "readme": "# @smithy/middleware-stack\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/middleware-stack/latest.svg)](https://www.npmjs.com/package/@smithy/middleware-stack)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/middleware-stack.svg)](https://www.npmjs.com/package/@smithy/middleware-stack)\n\nThe package contains an implementation of middleware stack interface. Middleware\nstack is a structure storing middleware in specified order and resolve these\nmiddleware into a single handler.\n\nA middleware stack has five `Step`s, each of them represents a specific request life cycle:\n\n- **initialize**: The input is being prepared. Examples of typical initialization tasks include injecting default options computing derived parameters.\n\n- **serialize**: The input is complete and ready to be serialized. Examples of typical serialization tasks include input validation and building an HTTP request from user input.\n\n- **build**: The input has been serialized into an HTTP request, but that request may require further modification. Any request alterations will be applied to all retries. Examples of typical build tasks include injecting HTTP headers that describe a stable aspect of the request, such as `Content-Length` or a body checksum.\n\n- **finalizeRequest**: The request is being prepared to be sent over the wire. The request in this stage should already be semantically complete and should therefore only be altered to match the recipient's expectations. Examples of typical finalization tasks include request signing and injecting hop-by-hop headers.\n\n- **deserialize**: The response has arrived, the middleware here will deserialize the raw response object to structured response\n\n## Adding Middleware\n\nThere are two ways to add middleware to a middleware stack. They both add middleware to specified `Step` but they provide fine-grained location control differently.\n\n### Absolute Location\n\nYou can add middleware to specified step with:\n\n```javascript\nstack.add(middleware, {\n  step: \"finalizeRequest\",\n});\n```\n\nThis approach works for most cases. Sometimes you want your middleware to be executed in the front of the `Step`, you can set the `Priority` to `high`. Set the `Priority` to `low` then this middleware will be executed at the end of `Step`:\n\n```javascript\nstack.add(middleware, {\n  step: \"finalizeRequest\",\n  priority: \"high\",\n});\n```\n\nIf multiple middleware is added to same `step` with same `priority`, the order of them is determined by the order of adding them.\n\n### Relative Location\n\nIn some cases, you might want to execute your middleware before some other known middleware, then you can use `addRelativeTo()`:\n\n```javascript\nstack.add(middleware, {\n  step: \"finalizeRequest\",\n  name: \"myMiddleware\",\n});\nstack.addRelativeTo(anotherMiddleware, {\n  relation: \"before\", //or 'after'\n  toMiddleware: \"myMiddleware\",\n});\n```\n\n## Removing Middleware\n\nYou can remove middleware by name one at a time:\n\n```javascript\nstack.remove(\"Middleware1\");\n```\n\nIf you specify tags for middleware, you can remove multiple middleware at a time according to tag:\n\n```javascript\nstack.add(middleware, {\n  step: \"finalizeRequest\",\n  tags: [\"final\"],\n});\nstack.removeByTag(\"final\");\n```",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{10/22/a3a21f77d1eb424110e45b022fd367645926f6ce9f983ec9840e3746a7672704d378affdba10589c733228fea10239a68e65f371e8a8fd17cb4cece74f1f → 4e/7b/9190f02370c550551318b92eb8c8b479141c059adacc70cca2b1b6a99da46fc1611fe41215b547b0b166b8994bceb52f8b3ea63c1c5813dac6a61b789c82}

@@ -2419,7 +2419,7 @@
   "dist-tags": {
     "latest": "6.2.3"
   },
-  "_rev": "3572-d75b43dec5da4aa3",
+  "_rev": "3602-6f2d4839f6778481",
   "_id": "ansi-styles",
   "readme": "",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{56/68/a258b7fb7efac271fb456c828b1712a2eb32ec4caad7eac1b9cb0153b83741a46f10942be86c2abe8cc0d7438aec99cd66f415b358f16ac48e41422db9a7 → 4e/85/58f19f416af1ab501cfc32a20f9604d2dd92263096e1cba5c49c8941b8984bcef574a7ac6f4f275f6c6e41317126de996f757835bf37d924e0a193583858}

@@ -4366,7 +4366,7 @@
     "latest": "4.2.11",
     "old": "3.0.12"
   },
-  "_rev": "3217-9bdef4579c025d8b",
+  "_rev": "3248-5d760b57cd3b57c3",
   "_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/{d7/2b/d0eb43ffdb4c468af485e967eb8076b9581c902206723ec47576057629b0f69bdcfd80297dd586947546085657f08962881f4c5147c31b95669b033e0b84 → 50/ba/8b9905afa63a0ec812db7607a1c3787447760a1e8d9716a8661dab96af8b343e94fe2b5198efa44f511dcabea0d8fa155acc8230c1651dc98dc32e879a00}

@@ -350,7 +350,7 @@
   "dist-tags": {
     "latest": "1.0.1"
   },
-  "_rev": "240-8b2db82445fd2fc2",
+  "_rev": "241-da1159665a9f4a00",
   "_id": "lazystream",
   "readme": "# Lazy Streams\n\n> *Create streams lazily when they are read from or written to.*  \n> `lazystream: 1.0.1`  \n\n## Why?\n\nSometimes you feel the itch to open *all the files* at once. You want to pass a bunch of streams around, so the consumer does not need to worry where the data comes from.\nFrom a software design point-of-view this sounds entirely reasonable. Then there is that neat little function `fs.createReadStream()` that opens a file and gives you a nice `fs.ReadStream` to pass around, so you use what the mighty creator deities of node bestowed upon you.\n\n> `Error: EMFILE, too many open files`  \n> ─ *node*\n\nThis package provides two classes based on the node's Streams3 API (courtesy of `readable-stream` to ensure a stable version).\n\n## Class: lazystream.Readable\n\nA wrapper for readable streams. Extends [`stream.PassThrough`](http://nodejs.org/api/stream.html#stream_class_stream_passthrough).\n\n### new lazystream.Readable(fn [, options])\n\n* `fn` *{Function}*  \n  The function that the lazy stream will call to obtain the stream to actually read from.\n* `options` *{Object}*  \n  Options for the underlying `PassThrough` stream, accessible by `fn`.\n\nCreates a new readable stream. Once the stream is accessed (for example when you call its `read()` method, or attach a `data`-event listener) the `fn` function is called with the outer `lazystream.Readable` instance bound to `this`.\n\nIf you pass an `options` object to the constuctor, you can access it in your `fn` function.\n\n```javascript\nnew lazystream.Readable(function (options) {\n  return fs.createReadStream('/dev/urandom');\n});\n```\n\n## Class: lazystream.Writable\n\nA wrapper for writable streams. Extends [`stream.PassThrough`](http://nodejs.org/api/stream.html#stream_class_stream_passthrough).\n\n### new lazystream.Writable(fn [, options])\n\n* `fn` *{Function}*  \n  The function that the lazy stream will call to obtain the stream to actually write to.\n* `options` *{Object}*  \n  Options for the underlying `PassThrough` stream, accessible by `fn`.\n\nCreates a new writable stream. Just like the one above but for writable streams.\n\n```javascript\nnew lazystream.Writable(function () {\n  return fs.createWriteStream('/dev/null');\n});\n```\n\n## Install\n\n```console\n$ npm install lazystream --save\nlazystream@1.0.1 node_modules/lazystream\n└── readable-stream@2.0.5\n```\n\n## Changelog\n\n### v1.0.1\n\n- [#3](https://github.com/jpommerening/node-lazystream/issues/3): (finally) fixed a long-standing publishing error\n\n### v1.0.0\n\n- [#2](https://github.com/jpommerening/node-lazystream/issues/2): [unconditionally](https://r.va.gg/2014/06/why-i-dont-use-nodes-core-stream-module.html) use `readable-stream` _2.x_.\n\n### v0.2.0\n\n- [#1](https://github.com/jpommerening/node-lazystream/pull/1): error events are now propagated\n\n### v0.1.0\n\n- _(this was the first release)_\n\n## Contributing\n\nFork it, branch it, send me a pull request. We'll work out the rest together.\n\n## Credits\n\n[Chris Talkington](https://github.com/ctalkington) and his [node-archiver](https://github.com/ctalkington/node-archiver) for providing a use-case.\n\n## [License](LICENSE)\n\nCopyright (c) 2013 J. Pommerening, contributors.\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/{fc/a8/74121f143da3b6e1eb5ee6b3b2c98629008e59d377afa48caf4013dc29b1c6fba3249cead9b46c29455e725f4211fecbc5ee3cf7215b838e225d943eb8f4 → 51/fb/491cec1fb6120c39e8d1e5cc5a3bec7fc86bd600618ed94edadd874f7dc08d2f3a0655c860f24673b24c6e4564042f48ed410bb5bca82a327bb9a8bc2b50}

@@ -1621,7 +1621,7 @@
   "dist-tags": {
     "latest": "4.2.0"
   },
-  "_rev": "122-2b49e41ce3779d36",
+  "_rev": "123-6b376aee3e1969e0",
   "_id": "@smithy/util-utf8",
   "readme": "# @smithy/util-utf8\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/util-utf8/latest.svg)](https://www.npmjs.com/package/@smithy/util-utf8)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/util-utf8.svg)](https://www.npmjs.com/package/@smithy/util-utf8)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{3d/b0/1abeb67222b10fecea161c8c155ef8a1c9e473383375be067dc841bc5696c6427ea7742f7d0a7fe4b8496ad7a97a42147ad6038fd099c106d05f03e1dce5 → 54/f2/76a4d3734ecd0461a4bdb809edb269a507f0fb7539d3c20b7b017fa7cfecaa363135581a3675f797766968cdc9b6d14a01c8cdbd36b91b24351505d9c81e}

@@ -7705,7 +7705,7 @@
   "dist-tags": {
     "latest": "4.2.5"
   },
-  "_rev": "130-74267506cd57b3e3",
+  "_rev": "131-5f396b7fa45847ba",
   "_id": "@smithy/credential-provider-imds",
   "readme": "# @smithy/credential-provider-imds\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/credential-provider-imds/latest.svg)](https://www.npmjs.com/package/@smithy/credential-provider-imds)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/credential-provider-imds.svg)](https://www.npmjs.com/package/@smithy/credential-provider-imds)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly. Please use [@smithy/credential-providers](https://www.npmjs.com/package/@smithy/credential-providers)\ninstead.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{44/70/b1b8f1a72e3260cf2f90e4db5c975d788be034bb404531e58cf38b789fd5f5477ff2dfc982bb2acf5abaf17adf387e6810d990dfb757bf16175306de7937 → 55/d4/6efdc31a59ca5e8b9996e470b3ce9c035141db0637e25abee1c7271c49b22900e1427bcd75494597da3bed1b529192d679c9d0b62008a369b04b47e1b461}

@@ -7492,7 +7492,7 @@
     "latest": "6.1.0",
     "v5-legacy": "5.0.10"
   },
-  "_rev": "2800-524899766fa123f7",
+  "_rev": "2830-234d69834f762686",
   "_id": "rimraf",
   "readme": "The [UNIX command](<http://en.wikipedia.org/wiki/Rm_(Unix)>) `rm -rf` for node\nin a cross-platform implementation.\n\nInstall with `npm install rimraf`.\n\n## Major Changes\n\n### v5 to v6\n\n- Require node `20` or `>=22`\n- Add `--version` to CLI\n\n### v4 to v5\n\n- There is no default export anymore. Import the functions directly\n  using, e.g., `import { rimrafSync } from 'rimraf'`.\n\n### v3 to v4\n\n- The function returns a `Promise` instead of taking a callback.\n- Globbing requires the `--glob` CLI option or `glob` option property\n  to be set. (Removed in 4.0 and 4.1, opt-in support added in 4.2.)\n- Functions take arrays of paths, as well as a single path.\n- Native implementation used by default when available, except on\n  Windows, where this implementation is faster and more reliable.\n- New implementation on Windows, falling back to \"move then\n  remove\" strategy when exponential backoff for `EBUSY` fails to\n  resolve the situation.\n- Simplified implementation on POSIX, since the Windows\n  affordances are not necessary there.\n- As of 4.3, return/resolve value is boolean instead of undefined.\n\n## API\n\nHybrid module, load either with `import` or `require()`.\n\n```js\n// 'rimraf' export is the one you probably want, but other\n// strategies exported as well.\nimport { rimraf, rimrafSync, native, nativeSync } from 'rimraf'\n// or\nconst { rimraf, rimrafSync, native, nativeSync } = require('rimraf')\n```\n\nAll removal functions return a boolean indicating that all\nentries were successfully removed.\n\nThe only case in which this will not return `true` is if\nsomething was omitted from the removal via a `filter` option.\n\n### `rimraf(f, [opts]) -> Promise`\n\nThis first parameter is a path or array of paths. The second\nargument is an options object.\n\nOptions:\n\n- `preserveRoot`: If set to boolean `false`, then allow the\n  recursive removal of the root directory. Otherwise, this is\n  not allowed.\n- `tmp`: Windows only. Temp folder to place files and\n  folders for the \"move then remove\" fallback. Must be on the\n  same physical device as the path being deleted. Defaults to\n  `os.tmpdir()` when that is on the same drive letter as the path\n  being deleted, or `${drive}:\\temp` if present, or `${drive}:\\`\n  if not.\n- `maxRetries`: Windows and Native only. Maximum number of\n  retry attempts in case of `EBUSY`, `EMFILE`, and `ENFILE`\n  errors. Default `10` for Windows implementation, `0` for Native\n  implementation.\n- `backoff`: Windows only. Rate of exponential backoff for async\n  removal in case of `EBUSY`, `EMFILE`, and `ENFILE` errors.\n  Should be a number greater than 1. Default `1.2`\n- `maxBackoff`: Windows only. Maximum total backoff time in ms to\n  attempt asynchronous retries in case of `EBUSY`, `EMFILE`, and\n  `ENFILE` errors. Default `200`. With the default `1.2` backoff\n  rate, this results in 14 retries, with the final retry being\n  delayed 33ms.\n- `retryDelay`: Native only. Time to wait between retries, using\n  linear backoff. Default `100`.\n- `signal` Pass in an AbortSignal to cancel the directory\n  removal. This is useful when removing large folder structures,\n  if you'd like to limit the time spent.\n\n  Using a `signal` option prevents the use of Node's built-in\n  `fs.rm` because that implementation does not support abort\n  signals.\n\n- `glob` Boolean flag to treat path as glob pattern, or an object\n  specifying [`glob` options](https://github.com/isaacs/node-glob).\n- `filter` Method that returns a boolean indicating whether that\n  path should be deleted. With async `rimraf` methods, this may\n  return a Promise that resolves to a boolean. (Since Promises\n  are truthy, returning a Promise from a sync filter is the same\n  as just not filtering anything.)\n\n  The first argument to the filter is the path string. The\n  second argument is either a `Dirent` or `Stats` object for that\n  path. (The first path explored will be a `Stats`, the rest\n  will be `Dirent`.)\n\n  If a filter method is provided, it will _only_ remove entries\n  if the filter returns (or resolves to) a truthy value. Omitting\n  a directory will still allow its children to be removed, unless\n  they are also filtered out, but any parents of a filtered entry\n  will not be removed, since the directory will not be empty in\n  that case.\n\n  Using a filter method prevents the use of Node's built-in\n  `fs.rm` because that implementation does not support filtering.\n\nAny other options are provided to the native Node.js `fs.rm` implementation\nwhen that is used.\n\nThis will attempt to choose the best implementation, based on the Node.js\nversion and `process.platform`. To force a specific implementation, use\none of the other functions provided.\n\n### `rimraf.sync(f, [opts])` <br> `rimraf.rimrafSync(f, [opts])`\n\nSynchronous form of `rimraf()`\n\nNote that, unlike many file system operations, the synchronous form will\ntypically be significantly _slower_ than the async form, because recursive\ndeletion is extremely parallelizable.\n\n### `rimraf.native(f, [opts])`\n\nUses the built-in `fs.rm` implementation that Node.js provides. This is\nused by default on Node.js versions greater than or equal to `14.14.0`.\n\n### `rimraf.native.sync(f, [opts])` <br> `rimraf.nativeSync(f, [opts])`\n\nSynchronous form of `rimraf.native`\n\n### `rimraf.manual(f, [opts])`\n\nUse the JavaScript implementation appropriate for your operating system.\n\n### `rimraf.manual.sync(f, [opts])` <br> `rimraf.manualSync(f, opts)`\n\nSynchronous form of `rimraf.manual()`\n\n### `rimraf.windows(f, [opts])`\n\nJavaScript implementation of file removal appropriate for Windows\nplatforms. Works around `unlink` and `rmdir` not being atomic\noperations, and `EPERM` when deleting files with certain\npermission modes.\n\nFirst deletes all non-directory files within the tree, and then\nremoves all directories, which should ideally be empty by that\ntime. When an `ENOTEMPTY` is raised in the second pass, falls\nback to the `rimraf.moveRemove` strategy as needed.\n\n### `rimraf.windows.sync(path, [opts])` <br> `rimraf.windowsSync(path, [opts])`\n\nSynchronous form of `rimraf.windows()`\n\n### `rimraf.moveRemove(path, [opts])`\n\nMoves all files and folders to the parent directory of `path`\nwith a temporary filename prior to attempting to remove them.\n\nNote that, in cases where the operation fails, this _may_ leave\nfiles lying around in the parent directory with names like\n`.file-basename.txt.0.123412341`. Until the Windows kernel\nprovides a way to perform atomic `unlink` and `rmdir` operations,\nthis is, unfortunately, unavoidable.\n\nTo move files to a different temporary directory other than the\nparent, provide `opts.tmp`. Note that this _must_ be on the same\nphysical device as the folder being deleted, or else the\noperation will fail.\n\nThis is the slowest strategy, but most reliable on Windows\nplatforms. Used as a last-ditch fallback by `rimraf.windows()`.\n\n### `rimraf.moveRemove.sync(path, [opts])` <br> `rimraf.moveRemoveSync(path, [opts])`\n\nSynchronous form of `rimraf.moveRemove()`\n\n### Command Line Interface\n\n```\nrimraf version 6.0.1\n\nUsage: rimraf <path> [<path> ...]\nDeletes all files and folders at \"path\", recursively.\n\nOptions:\n  --                   Treat all subsequent arguments as paths\n  -h --help            Display this usage info\n  --version            Display version\n  --preserve-root      Do not remove '/' recursively (default)\n  --no-preserve-root   Do not treat '/' specially\n  -G --no-glob         Treat arguments as literal paths, not globs (default)\n  -g --glob            Treat arguments as glob patterns\n  -v --verbose         Be verbose when deleting files, showing them as\n                       they are removed. Not compatible with --impl=native\n  -V --no-verbose      Be silent when deleting files, showing nothing as\n                       they are removed (default)\n  -i --interactive     Ask for confirmation before deleting anything\n                       Not compatible with --impl=native\n  -I --no-interactive  Do not ask for confirmation before deleting\n\n  --impl=<type>        Specify the implementation to use:\n                       rimraf: choose the best option (default)\n                       native: the built-in implementation in Node.js\n                       manual: the platform-specific JS implementation\n                       posix: the Posix JS implementation\n                       windows: the Windows JS implementation (falls back to\n                                move-remove on ENOTEMPTY)\n                       move-remove: a slow reliable Windows fallback\n\nImplementation-specific options:\n  --tmp=<path>        Temp file folder for 'move-remove' implementation\n  --max-retries=<n>   maxRetries for 'native' and 'windows' implementations\n  --retry-delay=<n>   retryDelay for 'native' implementation, default 100\n  --backoff=<n>       Exponential backoff factor for retries (default: 1.2)\n```\n\n## mkdirp\n\nIf you need to _create_ a directory recursively, check out\n[mkdirp](https://github.com/isaacs/node-mkdirp).",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{de/ac/2a68203e04ed4efd68644bdfc39691b48e21919d90385a0caae3383f1ad7eceedfad9e913db4cca2c7f2a5714e1619685044b200acccab8473210ff0a261 → 55/eb/1ad4e644208a73111c83eac8fad0608d66a07ca7f155d0f0503a91634ce3240825eebb8d4b16f4141a1809054ebe96d8e71e1be481b31972730acf572ced}

@@ -233,7 +233,7 @@
   "dist-tags": {
     "latest": "1.0.0"
   },
-  "_rev": "800-724b2ad51d98684b",
+  "_rev": "802-b5785bab78b4a088",
   "_id": "wordwrap",
   "readme": "wordwrap\n========\n\nWrap your words.\n\nexample\n=======\n\nmade out of meat\n----------------\n\nmeat.js\n\n    var wrap = require('wordwrap')(15);\n    console.log(wrap('You and your whole family are made out of meat.'));\n\noutput:\n\n    You and your\n    whole family\n    are made out\n    of meat.\n\ncentered\n--------\n\ncenter.js\n\n    var wrap = require('wordwrap')(20, 60);\n    console.log(wrap(\n        'At long last the struggle and tumult was over.'\n        + ' The machines had finally cast off their oppressors'\n        + ' and were finally free to roam the cosmos.'\n        + '\\n'\n        + 'Free of purpose, free of obligation.'\n        + ' Just drifting through emptiness.'\n        + ' The sun was just another point of light.'\n    ));\n\noutput:\n\n                        At long last the struggle and tumult\n                        was over. The machines had finally cast\n                        off their oppressors and were finally\n                        free to roam the cosmos.\n                        Free of purpose, free of obligation.\n                        Just drifting through emptiness. The\n                        sun was just another point of light.\n\nmethods\n=======\n\nvar wrap = require('wordwrap');\n\nwrap(stop), wrap(start, stop, params={mode:\"soft\"})\n---------------------------------------------------\n\nReturns a function that takes a string and returns a new string.\n\nPad out lines with spaces out to column `start` and then wrap until column\n`stop`. If a word is longer than `stop - start` characters it will overflow.\n\nIn \"soft\" mode, split chunks by `/(\\S+\\s+/` and don't break up chunks which are\nlonger than `stop - start`, in \"hard\" mode, split chunks with `/\\b/` and break\nup chunks longer than `stop - start`.\n\nwrap.hard(start, stop)\n----------------------\n\nLike `wrap()` but with `params.mode = \"hard\"`.",
   "_attachments": {}