mrs-toolbox-cli 9.0.2 → 9.0.4

package/npm-cache/_cacache/content-v2/sha512/{2f/10/b9dbc83d1b4a6583d11cf47a86353cdcace01c7ccc2803df5bf18d4e650ec28a104743bc704c468721492a9a4dfb540b17fa569ddbae301f1b81b61d14ad → 31/d0/2bee5f3fe062bc9cbc0bfdb5a4a564db04e053330be249ef75bf0e28d93d4148a0d38f2b6888fe312f01a93abdadeacbbc194b8b4c964b48ee1e565d0cac}

@@ -505,7 +505,7 @@
   "dist-tags": {
     "latest": "4.0.0"
   },
-  "_rev": "3146-1dd0f6f25b38474b",
+  "_rev": "3151-407a70845a22b486",
   "_id": "path-key",
   "readme": "# path-key\n\n> Get the [PATH](https://en.wikipedia.org/wiki/PATH_(variable)) environment variable key cross-platform\n\nIt's usually `PATH` but on Windows it can be any casing like `Path`...\n\n## Install\n\n```\n$ npm install path-key\n```\n\n## Usage\n\n```js\nimport pathKey from 'path-key';\n\nconst key = pathKey();\n//=> 'PATH'\n\nconst PATH = process.env[key];\n//=> '/usr/local/bin:/usr/bin:/bin'\n```\n\n## API\n\n### pathKey(options?)\n\n#### options\n\nType: `object`\n\n##### env\n\nType: `object`\\\nDefault: [`process.env`](https://nodejs.org/api/process.html#process_process_env)\n\nUse a custom environment variables object.\n\n#### platform\n\nType: `string`\\\nDefault: [`process.platform`](https://nodejs.org/api/process.html#process_process_platform)\n\nGet the PATH key for a specific platform.\n\n---\n\n<div align=\"center\">\n\t<b>\n\t\t<a href=\"https://tidelift.com/subscription/pkg/npm-path-key?utm_source=npm-path-key&utm_medium=referral&utm_campaign=readme\">Get professional support for this package with a Tidelift subscription</a>\n\t</b>\n\t<br>\n\t<sub>\n\t\tTidelift helps make open source sustainable for maintainers while giving companies<br>assurances about security, maintenance, and licensing for their dependencies.\n\t</sub>\n</div>",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{cd/5a/0b87402629d38233ed36c05fa1eaa40224329e23e9109d1d36c1247bf8f867b0b316130d2ba7f3c757cda7b6a9a9da2a1be6d461a2616d38ad59f81a01a7 → 32/ea/a98d3a2f5a79f8ce4660c88c8607df0ab83fd6f458146c21bb8af5df3144da1bb5e1f49f625a2717694d65ecf8b55c385c6bc613bf10b2ab400f47a5cb89}

@@ -1621,7 +1621,7 @@
   "dist-tags": {
     "latest": "4.2.0"
   },
-  "_rev": "168-3fed830d53c11dad",
+  "_rev": "172-f990dfb7e717cd67",
   "_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/{d7/f4/4ec893a0e0301cc70904e34297cfb2be49b827fb1fa5d827b8b427462ee3ad88be37eb45400d2afdc5b021a0613a178ef371d7aad4731b9c4228bd2949dd → 34/42/040bffab5e3fad69921bbd8f99259d579e12e636f33348f50ba4e6105e041ff9cfab91c61d7edc13279fff6a27500493b04298a931bd847da948d6e5cedc}

@@ -4687,7 +4687,7 @@
   "dist-tags": {
     "latest": "2.23.0"
   },
-  "_rev": "631-c3d5f2c9eb1f6e4c",
+  "_rev": "635-bca94b20e60abb75",
   "_id": "streamx",
   "readme": "# streamx\n\nAn iteration of the Node.js core streams with a series of improvements.\n\n```\nnpm install streamx\n```\n\n[![Build Status](https://github.com/streamxorg/streamx/workflows/Build%20Status/badge.svg)](https://github.com/streamxorg/streamx/actions?query=workflow%3A%22Build+Status%22)\n\n## Main improvements from Node.js core stream\n\n#### Proper lifecycle support.\n\nStreams have an `_open` function that is called before any read/write operation and a `_destroy`\nfunction that is always run as the last part of the stream.\n\nThis makes it easy to maintain state.\n\n#### Easy error handling\n\nFully integrates a `.destroy()` function. When called the stream will wait for any\npending operation to finish and call the stream destroy logic.\n\nClose is *always* the last event emitted and `destroy` is always run.\n\n#### `pipe()` error handles\n\n`pipe` accepts a callback that is called when the pipeline is fully drained.\nIt also error handles the streams provided and destroys both streams if either\nof them fail.\n\n#### All streams are both binary and object mode streams\n\nA `map` function can be provided to map your input data into buffers\nor other formats. To indicate how much buffer space each data item takes\nan `byteLength` function can be provided as well.\n\nThis removes the need for two modes of streams.\n\n#### Simplicity\n\nThis is a full rewrite, all contained in one file.\n\nLots of stream methods are simplified based on how I and devs I work with actually use streams in the wild.\n\n#### Backwards compat\n\nstreamx aims to be compatible with Node.js streams whenever it is reasonable to do so.\n\nThis means that streamx streams behave a lot like Node.js streams from the outside but still provides the\nimprovements above.\n\n#### Smaller browser footprint\n\nstreamx has a much smaller footprint when compiled for the browser:\n\n```\n$ for x in stream{,x}; do echo $x: $(browserify -r $x | wc -c) bytes; done\nstream: 173844 bytes\nstreamx: 46943 bytes\n```\n\nWith optimizations turned on, the difference is even more stark:\n\n```\n$ for x in stream{,x}; do echo $x: $(browserify -r $x -p tinyify | wc -c) bytes; done\nstream: 62649 bytes\nstreamx: 8460 bytes\n$ for x in stream{,x}; do echo $x: $(browserify -r $x -p tinyify | gzip | wc -c) \"bytes (gzipped)\"; done\nstream: 18053 bytes (gzipped)\nstreamx: 2806 bytes (gzipped)\n```\n\n#### AbortSignal support\n\nTo make it easier to integrate streams in a `async/await` flow, all streams support a `signal` option\nthat accepts a [`AbortSignal`](https://developer.mozilla.org/en-US/docs/Web/API/AbortSignal) to as an\nalternative means to `.destroy` streams.\n\n## Usage\n\n``` js\nconst { Readable } = require('streamx')\n\nconst rs = new Readable({\n  read (cb) {\n    this.push('Cool data')\n    cb(null)\n  }\n})\n\nrs.on('data', data => console.log('data:', data))\n```\n\n## API\n\nThis streamx package contains 4 streams similar to Node.js core.\n\n## Readable Stream\n\n#### `rs = new stream.Readable([options])`\n\nCreate a new readable stream.\n\nOptions include:\n\n```\n{\n  highWaterMark: 16384, // max buffer size in bytes\n  map: (data) => data, // optional function to map input data\n  byteLength: (data) => size, // optional function that calculates the byte size of input data\n  signal: abortController.signal, // optional AbortSignal that triggers `.destroy` when on `abort`\n  eagerOpen: false // eagerly open the stream\n}\n```\n\nIn addition you can pass the `open`, `read`, and `destroy` functions as shorthands in\nthe constructor instead of overwrite the methods below.\n\nThe default byteLength function returns the byte length of buffers and `1024`\nfor any other object. This means the buffer will contain around 16 non buffers\nor buffers worth 16kb when full if the defaults are used.\n\nIf you set highWaterMark to `0` then all read ahead buffering on the stream\nis disabled and it will only call `_read` when a user reads rather than ahead of time.\n\n#### `rs._read(cb)`\n\nThis function is called when the stream wants you to push new data.\nOverwrite this and add your own read logic.\nYou should call the callback when you are fully done with the read.\n\nCan also be set using `options.read` in the constructor.\n\nNote that this function differs from Node.js streams in that it takes\nthe \"read finished\" callback.\n\n#### `drained = rs.push(data)`\n\nPush new data to the stream. Returns true if the buffer is not full\nand you should push more data if you can.\n\nIf you call `rs.push(null)` you signal to the stream that no more\ndata will be pushed and that you want to end the stream.\n\n#### `data = rs.read()`\n\nRead a piece of data from the stream buffer. If the buffer is currently empty\n`null` will be returned and you should wait for `readable` to be emitted before\ntrying again. If the stream has been ended it will also return `null`.\n\nNote that this method differs from Node.js streams in that it does not accept\nan optional amounts of bytes to consume.\n\n#### `rs.unshift(data)`\n\nAdd a piece of data to the front of the buffer. Use this if you read too much\ndata using the `rs.read()` function.\n\n#### `rs._open(cb)`\n\nThis function is called once before the first read is issued. Use this function\nto implement your own open logic.\n\nCan also be set using `options.open` in the constructor.\n\n#### `rs._destroy(cb)`\n\nThis function is called just before the stream is fully destroyed. You should\nuse this to implement whatever teardown logic you need. The final part of the\nstream life cycle is always to call destroy itself so this function will always\nbe called wheather or not the stream ends gracefully or forcefully.\n\nCan also be set using `options.destroy` in the constructor.\n\nNote that the `_destroy` might be called without the open function being called\nin case no read was ever performed on the stream.\n\n#### `rs._predestroy()`\n\nA simple hook that is called as soon as the first `stream.destroy()` call is invoked.\n\nUse this in case you need to cancel pending reads (if possible) instead of waiting for them to finish.\n\nCan also be set using `options.predestroy` in the constructor.\n\n#### `rs.destroy([error])`\n\nForcefully destroy the stream. Will call `_destroy` as soon as all pending reads have finished.\nOnce the stream is fully destroyed `close` will be emitted.\n\nIf you pass an error this error will be emitted just before `close` is, signifying a reason\nas to why this stream was destroyed.\n\n#### `rs.pause()`\n\nPauses the stream. You will only need to call this if you want to pause a resumed stream.\n\nReturns this stream instance.\n\n#### `rs.resume()`\n\nWill start reading data from the stream as fast as possible.\n\nIf you do not call this, you need to use the `read()` method to read data or the `pipe()` method to\npipe the stream somewhere else or the `data` handler.\n\nIf none of these option are used the stream will stay paused.\n\nReturns this stream instance.\n\n#### `bool = Readable.isPaused(rs)`\n\nReturns `true` if the stream is paused, else `false`.\n\n#### `writableStream = rs.pipe(writableStream, [callback])`\n\nEfficently pipe the readable stream to a writable stream (can be Node.js core stream or a stream from this package).\nIf you provide a callback the callback is called when the pipeline has fully finished with an optional error in case\nit failed.\n\nTo cancel the pipeline destroy either of the streams.\n\n#### `rs.on('readable')`\n\nEmitted when data is pushed to the stream if the buffer was previously empty.\n\n#### `rs.on('data', data)`\n\nEmitted when data is being read from the stream. If you attach a data handler you are implicitly resuming the stream.\n\n#### `rs.on('end')`\n\nEmitted when the readable stream has ended and no data is left in it's buffer.\n\n#### `rs.on('close')`\n\nEmitted when the readable stream has fully closed (i.e. it's destroy function has completed)\n\n#### `rs.on('error', err)`\n\nEmitted if any of the stream operations fail with an error. `close` is always emitted right after this.\n\n#### `rs.on('piping', dest)`\n\nEmitted when the readable stream is pipeing to a destination.\n\n#### `rs.destroyed`\n\nBoolean property indicating wheather or not this stream has been destroyed.\n\n#### `bool = Readable.isBackpressured(rs)`\n\nStatic method to check if a readable stream is currently under backpressure.\n\n#### `stream = Readable.from(arrayOrBufferOrStringOrAsyncIterator)`\n\nStatic method to turn an array or buffer or string or AsyncIterator into a readable stream.\n\n## Writable Stream\n\n#### `ws = new stream.Writable([options])`\n\nCreate a new writable stream.\n\nOptions include:\n\n```\n{\n  highWaterMark: 16384, // max buffer size in bytes\n  map: (data) => data, // optional function to map input data\n  byteLength: (data) => size, // optional function that calculates the byte size of input data\n  signal: abortController.signal // optional AbortSignal that triggers `.destroy` when on `abort`\n}\n```\n\nIn addition you can pass the `open`, `write`, `final`, and `destroy` functions as shorthands in\nthe constructor instead of overwrite the methods below.\n\nThe default byteLength function returns the byte length of buffers and `1024`\nfor any other object. This means the buffer will contain around 16 non buffers\nor buffers worth 16kb when full if the defaults are used.\n\n#### `ws._open(cb)`\n\nThis function is called once before the first write is issued. Use this function\nto implement your own open logic.\n\nCan also be set using `options.open` in the constructor.\n\n#### `ws._destroy(cb)`\n\nThis function is called just before the stream is fully destroyed. You should\nuse this to implement whatever teardown logic you need. The final part of the\nstream life cycle is always to call destroy itself so this function will always\nbe called wheather or not the stream ends gracefully or forcefully.\n\nCan also be set using `options.destroy` in the constructor.\n\nNote that the `_destroy` might be called without the open function being called\nin case no write was ever performed on the stream.\n\n#### `ws._predestroy()`\n\nA simple hook that is called as soon as the first `stream.destroy()` call is invoked.\n\nUse this in case you need to cancel pending writes (if possible) instead of waiting for them to finish.\n\nCan also be set using `options.predestroy` in the constructor.\n\n#### `ws.destroy([error])`\n\nForcefully destroy the stream. Will call `_destroy` as soon as all pending reads have finished.\nOnce the stream is fully destroyed `close` will be emitted.\n\nIf you pass an error this error will be emitted just before `close` is, signifying a reason\nas to why this stream was destroyed.\n\n#### `drained = ws.write(data)`\n\nWrite a piece of data to the stream. Returns `true` if the stream buffer is not full and you\nshould keep writing to it if you can. If `false` is returned the stream will emit `drain`\nonce it's buffer is fully drained.\n\n#### `ws._write(data, callback)`\n\nThis function is called when the stream want to write some data. Use this to implement your own\nwrite logic. When done call the callback and the stream will call it again if more data exists in the buffer.\n\nCan also be set using `options.write` in the constructor.\n\n#### `ws._writev(batch, callback)`\n\nSimilar to `_write` but passes an array of all data in the current write buffer instead of the oldest one.\nUseful if the destination you are writing the data to supports batching.\n\nCan also be set using `options.writev` in the constructor.\n\n#### `ws.end()`\n\nGracefully end the writable stream. Call this when you no longer want to write to the stream.\n\nOnce all writes have been fully drained `finish` will be emitted.\n\nReturns this stream instance.\n\n#### `ws._final(callback)`\n\nThis function is called just before `finish` is emitted, i.e. when all writes have flushed but `ws.end()`\nhave been called. Use this to implement any logic that should happen after all writes but before finish.\n\nCan also be set using `options.final` in the constructor.\n\n#### `ws.on('finish')`\n\nEmitted when the stream has been ended and all writes have been drained.\n\n#### `ws.on('close')`\n\nEmitted when the readable stream has fully closed (i.e. it's destroy function has completed)\n\n#### `ws.on('error', err)`\n\nEmitted if any of the stream operations fail with an error. `close` is always emitted right after this.\n\n#### `ws.on('pipe', src)`\n\nEmitted when a readable stream is being piped to the writable one.\n\n#### `ws.destroyed`\n\nBoolean property indicating wheather or not this stream has been destroyed.\n\n#### `bool = Writable.isBackpressured(ws)`\n\nStatic method to check if a writable stream is currently under backpressure.\n\n#### `bool = await Writable.drained(ws)`\n\nStatic helper to wait for a stream to drain the currently queued writes.\nReturns true if they were drained and false otherwise if the stream was destroyed.\n\n## Duplex Stream\n\n#### `s = new stream.Duplex([options])`\n\nA duplex stream is a stream that is both readable and writable.\n\nSince JS does not support multiple inheritance it inherits directly from Readable\nbut implements the Writable API as well.\n\nIf you want to provide only a map function for the readable side use `mapReadable` instead.\nIf you want to provide only a byteLength function for the readable side use `byteLengthReadable` instead.\n\nSame goes for the writable side but using `mapWritable` and `byteLengthWritable` instead.\n\n## Transform Stream\n\nA Transform stream is a duplex stream with an `._transform` template method that allows to\nasynchronously map the input to a different output.\n\nThe transform stream overrides the `_write` and `_read` operations of `Readable` and `Writable` but\nstill allows the setting of these options in the constructor. Usually it is unnecessary to pass\nin `read` or `write`/`writev` or to override the corresponding `._read`, `._write` or `._writev` operation.\n\n#### `ts = new stream.Transform([options])`\n\nA transform stream is a duplex stream that maps the data written to it and emits that as readable data.\n\nHas the same options as a duplex stream except you can provide a `transform` function also.\n\n#### `ts._transform(data, callback)`\n\nTransform the incoming data. Call `callback(null, mappedData)` or use `ts.push(mappedData)` to\nreturn data to the readable side of the stream.\n\nPer default the transform function just remits the incoming data making it act as a pass-through stream.\n\n## Pipeline\n\n`pipeline` allows to stream form a readable through a set of duplex streams to a writable entry.\n\n```js\nconst { pipeline, Readable, Transform, Writable } = require('streamx')\nconst lastStream = pipeline(\n  Readable.from([1, 2, 3]),\n  new Transform({\n    transform (from, cb) {\n      this.push(from.toString())\n      cb()\n    }\n  }),\n  new Writable({\n    write (data, cb) {\n      console.log(data)\n      cb()\n    }\n  })\n  error => {\n    // Callback once write has finished\n  }\n)\n```\n\n#### `lastStream = stream.pipeline(...streams, [done])`\n\nPipe all streams together and return the last stream piped to.\nWhen the last stream finishes the pipeline ended succesfully.\n\nIf any of the streams error, whether they are Node.js core streams\nor streamx streams, all streams in the pipeline are shutdown.\n\nOptionally you can pass a done callback to know when the pipeline is done.\n\n#### `promise = stream.pipelinePromise(...streams)`\n\nSame as normal pipeline except instead of returning the last stream it returns\na promise representing the done callback. Note you should error handle this\npromise if you use this version.\n\n## Helpers\n\n#### `bool = isStream(stream)`\n\n#### `bool = isStreamx(stream)`\n\n#### `err = getStreamError(stream, [options])`\n\nReturns `null` if the stream has no errors.\n\n## Utilities\n\nStreamx aims to be minimal and stable. It therefore only contains a minimal set of utilities.\nTo help discover of other modules that help you build streamx apps, we link some useful utilities here\n\n* [stream-composer](https://github.com/mafintosh/stream-composer) - Compose streams like Node's `stream.compose` and the `duplexify` and `pumpify` modules.\n* [teex](https://github.com/mafintosh/teex) - Clone a readable stream into multiple new readable instances.\n\n## Contributing\n\nIf you want to help contribute to streamx a good way to start is to help writing more test\ncases, compatibility tests, documentation, or performance benchmarks.\n\nIf in doubt open an issue :)\n\n## License\n\nMIT",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{f3/82/59d3d67cf9be90dc4746341e1da6d83f473acfc1e885e5ef7e25842ae182f3441cf9f8eefde923dc624b4ed4f0a105162396ddaba1e56dcd4354ba411be5 → 35/37/a185c99755512fd79de47a6e80ed27ca7f2dbce279c7bba606fcbe782bf8386f35e03ef895c91e5702c5dd8cbc14372d03263666b0c3f80af3c4e7c00a76}

@@ -19015,7 +19015,7 @@
     "gamma": "1.0.0-gamma.8",
     "rc": "1.0.0-rc.10"
   },
-  "_rev": "283-ae94ae700e4c5489",
+  "_rev": "287-aa232238c2105310",
   "_id": "@aws-sdk/middleware-location-constraint",
   "readme": "# @aws-sdk/middleware-location-constraint\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/middleware-location-constraint/latest.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-location-constraint)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/middleware-location-constraint.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-location-constraint)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{60/df/9b826f37992a402e7aa3241b5d738e49d99d57c26f54bc6bd9cf665eb9eab669044fb71ec26e57f63d2d580f6c8eeebd0ce09ddcfa337267fbf3dfe58099 → 37/0d/662e9cef43b637476ab1c9168ce5a3a75da53fc7f95f1fde544300cc34bccd6ea7d7fd92ac5588a774ffaa06f624dfcdb0748a6ee25d8f5a1ce3bd4bdce7}

@@ -20491,7 +20491,7 @@
     "gamma": "1.0.0-gamma.8",
     "rc": "1.0.0-rc.10"
   },
-  "_rev": "278-54e70d3f42fb6739",
+  "_rev": "282-f64e31de140ed5e0",
   "_id": "@aws-sdk/middleware-expect-continue",
   "readme": "# @aws-sdk/middleware-expect-continue\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/middleware-expect-continue/latest.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-expect-continue)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/middleware-expect-continue.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-expect-continue)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{02/fa/0a3c89aae4f1df2471398808d5062769db2993e55ccf266f21601be1c6708a7df91152c6261023bfdac5adc77b1bed086ec87948fed4cc9e6b48da182c8e → 3a/7c/19802ed1278f86499896a712aa7390a7cb5ba523c760821cb34ce299b2ebb7d8c336d06355318dedf4c2f98477262d092e921a57ca4020834bc6b3f40c76}

@@ -553,7 +553,7 @@
   "dist-tags": {
     "latest": "1.2.3"
   },
-  "_rev": "622-50781807c6a6a8c1",
+  "_rev": "626-3f83a531e515174d",
   "_id": "text-decoder",
   "readme": "# text-decoder\n\nStreaming text decoder that preserves multibyte Unicode characters.\n\n```\nnpm i text-decoder\n```\n\n## Usage\n\n``` js\nconst TextDecoder = require('text-decoder')\n\nconst td = new TextDecoder()\n\ntd.push(Buffer.of(0xf0, 0x9f, 0x92)) // returns ''\ntd.push(Buffer.of(0xa9)) // returns '💩'\n```\n\n## API\n\n#### `const td = new TextDecoder([encoding])`\n\nCreate a text decoder. `encoding` defaults to `utf8`.\n\n#### `const string = td.push(data)`\n\nPush either a `Buffer` or a `string` to the text decoder. Returns the decoded string, buffering any partial data.\n\n#### `const string = td.end([data])`\n\nEnd the decoder, optionally pushing a final piece of data. Returns the decoded string.\n\n## License\n\nApache-2.0",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{44/30/4b4c4a358e13ff13db0c6b4a88ba2d0de5d9530716d4a39676c86811e119e13e6440c7fbf385ea4b107792d0cc9fc52db279fe95f0c3ecf9e790e8b823e0 → 3c/80/edfd935ca565c620af35184369122711fad61e192e53b93f6e17a2e54afab4291c053f8810c685c6fc40d81c3e17e6ee5a12f21ce0c5501c4e223c7259e7}

@@ -1691,7 +1691,7 @@
   "dist-tags": {
     "latest": "4.2.1"
   },
-  "_rev": "166-eb361bc2526ea243",
+  "_rev": "170-50beb79356711f83",
   "_id": "@smithy/chunked-blob-reader-native",
   "readme": "# @smithy/chunked-blob-reader-native\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/chunked-blob-reader-native/latest.svg)](https://www.npmjs.com/package/@smithy/chunked-blob-reader-native)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/chunked-blob-reader-native.svg)](https://www.npmjs.com/package/@smithy/chunked-blob-reader-native)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{44/d5/2962c16b678aa12f35f0cb6eb91f174d50daed6859c82a4c45704b5460b2ff01bb87b3ff03d2559cd448a92dd70b71e3109504f13b53b0c8798f42a5a614 → 3d/83/1bd437069cadaeae8b133bb2369e35f874f92771e1246966dcc72239c43be79057336d06029085bac20f46d9ebdc72965ba001c6990aed081cc7b4afd17d}

@@ -16391,7 +16391,7 @@
   "dist-tags": {
     "latest": "3.970.0"
   },
-  "_rev": "167-249efe5d6ef91f8e",
+  "_rev": "171-7af67ccfdb4b33a1",
   "_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/{b2/fe/026a8bb601ffa479ca6f0699e6416b8d83c4708493e609597c8edfad7375ec7c757b60b1dede9515ae66a627ff53aa0f4c06def4e5e81d6410eefc44f1b1 → 3d/c5/b37613e14cbee554e4d806f7198f3116743a43ecc3d62724c7342d7a949b9283d22b2944d8b6c81e3cc77bc844338df7eb40f29ef5857cd45a14ff67a5e0}

@@ -111584,7 +111584,7 @@
     "ts5.9": "19.2.8",
     "ts6.0": "19.2.8"
   },
-  "_rev": "13052-8334289012c5d311",
+  "_rev": "13057-3070f27ffb9b891e",
   "_id": "@types/react",
   "readme": "[object Object]",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{00/7f/329fcc4689cb138d1794abf439bb9f1631a9252bc2850c8d7cdc1a83fdf0b462ba872b6b083cf63a8d19da53c624bbed66be2dc311cfb9bf1304ba6e66ab → 40/b9/7b51da6a22ea3e325c500d12fa6df19f7d735f7bfeaeb3e11ee8329d064cf3874a7c840d4ef7c754dab4fc33300ab5492b9db9a93aace50470dbe3587636}

@@ -7262,7 +7262,7 @@
     "latest": "4.1.1",
     "v3-legacy": "3.4.3"
   },
-  "_rev": "937-6b4698eb6c0eaa72",
+  "_rev": "942-84e7bdd2ca2a0510",
   "_id": "jackspeak",
   "readme": "# jackspeak\n\nA very strict and proper argument parser.\n\nValidate string, boolean, and number options, from the command\nline and the environment.\n\nCall the `jack` method with a config object, and then chain\nmethods off of it.\n\nAt the end, call the `.parse()` method, and you'll get an object\nwith `positionals` and `values` members.\n\nAny unrecognized configs or invalid values will throw an error.\n\nAs long as you define configs using object literals, types will\nbe properly inferred and TypeScript will know what kinds of\nthings you got.\n\nIf you give it a prefix for environment variables, then defaults\nwill be read from the environment, and parsed values written back\nto it, so you can easily pass configs through to child processes.\n\nAutomatically generates a `usage`/`help` banner by calling the\n`.usage()` method.\n\nUnless otherwise noted, all methods return the object itself.\n\n## USAGE\n\n```js\nimport { jack } from 'jackspeak'\n// this works too:\n// const { jack } = require('jackspeak')\n\nconst { positionals, values } = jack({ envPrefix: 'FOO' })\n  .flag({\n    asdf: { description: 'sets the asfd flag', short: 'a', default: true },\n    'no-asdf': { description: 'unsets the asdf flag', short: 'A' },\n    foo: { description: 'another boolean', short: 'f' },\n  })\n  .optList({\n    'ip-addrs': {\n      description: 'addresses to ip things',\n      delim: ',', // defaults to '\\n'\n      default: ['127.0.0.1'],\n    },\n  })\n  .parse([\n    'some',\n    'positional',\n    '--ip-addrs',\n    '192.168.0.1',\n    '--ip-addrs',\n    '1.1.1.1',\n    'args',\n    '--foo', // sets the foo flag\n    '-A', // short for --no-asdf, sets asdf flag to false\n  ])\n\nconsole.log(process.env.FOO_ASDF) // '0'\nconsole.log(process.env.FOO_FOO) // '1'\nconsole.log(values) // {\n//   'ip-addrs': ['192.168.0.1', '1.1.1.1'],\n//   foo: true,\n//   asdf: false,\n// }\nconsole.log(process.env.FOO_IP_ADDRS) // '192.168.0.1,1.1.1.1'\nconsole.log(positionals) // ['some', 'positional', 'args']\n```\n\n## `jack(options: JackOptions = {}) => Jack`\n\nReturns a `Jack` object that can be used to chain and add\nfield definitions. The other methods (apart from `validate()`,\n`parse()`, and `usage()` obviously) return the same Jack object,\nupdated with the new types, so they can be chained together as\nshown in the code examples.\n\nOptions:\n\n- `allowPositionals` Defaults to true. Set to `false` to not\n  allow any positional arguments.\n\n- `envPrefix` Set to a string to write configs to and read\n  configs from the environment. For example, if set to `MY_APP`\n  then the `foo-bar` config will default based on the value of\n  `env.MY_APP_FOO_BAR` and will write back to that when parsed.\n\n  Boolean values are written as `'1'` and `'0'`, and will be\n  treated as `true` if they're `'1'` or false otherwise.\n\n  Number values are written with their `toString()`\n  representation.\n\n  Strings are just strings.\n\n  Any value with `multiple: true` will be represented in the\n  environment split by a delimiter, which defaults to `\\n`.\n\n- `env` The place to read/write environment variables. Defaults\n  to `process.env`.\n\n- `usage` A short usage string to print at the top of the help\n  banner.\n\n- `stopAtPositional` Boolean, default false. Stop parsing opts\n  and flags at the first positional argument. This is useful if\n  you want to pass certain options to subcommands, like some\n  programs do, so you can stop parsing and pass the positionals\n  to the subcommand to parse.\n\n- `stopAtPositionalTest` Conditional `stopAtPositional`. Provide\n  a function that takes a positional argument string and returns\n  boolean. If it returns `true`, then parsing will stop. Useful\n  when _some_ subcommands should parse the rest of the command\n  line options, and others should not.\n\n### `Jack.heading(text: string, level?: 1 | 2 | 3 | 4 | 5 | 6)`\n\nDefine a short string heading, used in the `usage()` output.\n\nIndentation of the heading and subsequent description/config\nusage entries (up until the next heading) is set by the heading\nlevel.\n\nIf the first usage item defined is a heading, it is always\ntreated as level 1, regardless of the argument provided.\n\nHeadings level 1 and 2 will have a line of padding underneath\nthem. Headings level 3 through 6 will not.\n\n### `Jack.description(text: string, { pre?: boolean } = {})`\n\nDefine a long string description, used in the `usage()` output.\n\nIf the `pre` option is set to `true`, then whitespace will not be\nnormalized. However, if any line is too long for the width\nallotted, it will still be wrapped.\n\n## Option Definitions\n\nConfigs are defined by calling the appropriate field definition\nmethod with an object where the keys are the long option name,\nand the value defines the config.\n\nOptions:\n\n- `type` Only needed for the `addFields` method, as the others\n  set it implicitly. Can be `'string'`, `'boolean'`, or\n  `'number'`.\n- `multiple` Only needed for the `addFields` method, as the\n  others set it implicitly. Set to `true` to define an array\n  type. This means that it can be set on the CLI multiple times,\n  set as an array in the `values`\n  and it is represented in the environment as a delimited string.\n- `short` A one-character shorthand for the option.\n- `description` Some words to describe what this option is and\n  why you'd set it.\n- `hint` (Only relevant for non-boolean types) The thing to show\n  in the usage output, like `--option=<hint>`\n- `validate` A function that returns false (or throws) if an\n  option value is invalid.\n- `validOptions` An array of strings or numbers that define the\n  valid values that can be set. This is not allowed on `boolean`\n  (flag) options. May be used along with a `validate()` method.\n- `default` A default value for the field. Note that this may be\n  overridden by an environment variable, if present.\n\n### `Jack.flag({ [option: string]: definition, ... })`\n\nDefine one or more boolean fields.\n\nBoolean options may be set to `false` by using a\n`--no-${optionName}` argument, which will be implicitly created\nif it's not defined to be something else.\n\nIf a boolean option named `no-${optionName}` with the same\n`multiple` setting is in the configuration, then that will be\ntreated as a negating flag.\n\n### `Jack.flagList({ [option: string]: definition, ... })`\n\nDefine one or more boolean array fields.\n\n### `Jack.num({ [option: string]: definition, ... })`\n\nDefine one or more number fields. These will be set in the\nenvironment as a stringified number, and included in the `values`\nobject as a number.\n\n### `Jack.numList({ [option: string]: definition, ... })`\n\nDefine one or more number list fields. These will be set in the\nenvironment as a delimited set of stringified numbers, and\nincluded in the `values` as a number array.\n\n### `Jack.opt({ [option: string]: definition, ... })`\n\nDefine one or more string option fields.\n\n### `Jack.optList({ [option: string]: definition, ... })`\n\nDefine one or more string list fields.\n\n### `Jack.addFields({ [option: string]: definition, ... })`\n\nDefine one or more fields of any type. Note that `type` and\n`multiple` must be set explicitly on each definition when using\nthis method.\n\n## Informative Getters\n\nOnce you've defined several fields with the various methods\ndescribed above, you can get at the definitions and such with\nthese methods.\n\nThis are primarily just informative, but can be useful in some\nadvanced scenarios, such as providing \"Did you mean?\" type\nsuggestions when someone misspells an option name.\n\n### `Jack.definitions`\n\nThe set of config field definitions in no particular order. This\nis a data object suitable to passing to `util.parseArgs`, but\nwith the addition of `short` and `description` fields, where\nappropriate.\n\n### `Jack.jackOptions`\n\nThe options passed into the initial `jack()` function (or `new\nJack()` constructor).\n\n### `Jack.shorts`\n\nThe `{ <short>: <long> }` name record for all short options\ndefined.\n\n### `Jack.usageFields`\n\nThe array of fields that are used to generate `Jack.usage()` and\n`Jack.usageMarkdown()` content.\n\n## Actions\n\nUse these methods on a Jack object that's already had its config\nfields defined.\n\n### `Jack.parse(args: string[] = process.argv): { positionals: string[], values: OptionsResults }`\n\nParse the arguments list, write to the environment if `envPrefix`\nis set, and returned the parsed values and remaining positional\narguments.\n\n### `Jack.validate(o: any): asserts o is OptionsResults`\n\nThrows an error if the object provided is not a valid result set,\nfor the configurations defined thusfar.\n\n### `Jack.usage(): string`\n\nReturns the compiled `usage` string, with all option descriptions\nand heading/description text, wrapped to the appropriate width\nfor the terminal.\n\n### `Jack.setConfigValues(options: OptionsResults, src?: string)`\n\nValidate the `options` argument, and set the default value for\neach field that appears in the options.\n\nValues provided will be overridden by environment variables or\ncommand line arguments.\n\n### `Jack.usageMarkdown(): string`\n\nReturns the compiled `usage` string, with all option descriptions\nand heading/description text, but as markdown instead of\nformatted for a terminal, for generating HTML documentation for\nyour CLI.\n\n## Some Example Code\n\nAlso see [the examples\nfolder](https://github.com/isaacs/jackspeak/tree/master/examples)\n\n```js\nimport { jack } from 'jackspeak'\n\nconst j = jack({\n  // Optional\n  // This will be auto-generated from the descriptions if not supplied\n  // top level usage line, printed by -h\n  // will be auto-generated if not specified\n  usage: 'foo [options] <files>',\n})\n  .heading('The best Foo that ever Fooed')\n  .description(\n    `\n    Executes all the files and interprets their output as\n    TAP formatted test result data.\n\n    To parse TAP data from stdin, specify \"-\" as a filename.\n  `,\n  )\n\n  // flags don't take a value, they're boolean on or off, and can be\n  // turned off by prefixing with `--no-`\n  // so this adds support for -b to mean --bail, or -B to mean --no-bail\n  .flag({\n    flag: {\n      // specify a short value if you like.  this must be a single char\n      short: 'f',\n      // description is optional as well.\n      description: `Make the flags wave`,\n      // default value for flags is 'false', unless you change it\n      default: true,\n    },\n    'no-flag': {\n      // you can can always negate a flag with `--no-flag`\n      // specifying a negate option will let you define a short\n      // single-char option for negation.\n      short: 'F',\n      description: `Do not wave the flags`,\n    },\n  })\n\n  // Options that take a value are specified with `opt()`\n  .opt({\n    reporter: {\n      short: 'R',\n      description: 'the style of report to display',\n    },\n  })\n\n  // if you want a number, say so, and jackspeak will enforce it\n  .num({\n    jobs: {\n      short: 'j',\n      description: 'how many jobs to run in parallel',\n      default: 1,\n    },\n  })\n\n  // A list is an option that can be specified multiple times,\n  // to expand into an array of all the settings.  Normal opts\n  // will just give you the last value specified.\n  .optList({\n    'node-arg': {},\n  })\n\n  // a flagList is an array of booleans, so `-ddd` is [true, true, true]\n  // count the `true` values to treat it as a counter.\n  .flagList({\n    debug: { short: 'd' },\n  })\n\n  // opts take a value, and is set to the string in the results\n  // you can combine multiple short-form flags together, but\n  // an opt will end the combine chain, posix-style.  So,\n  // -bofilename would be like --bail --output-file=filename\n  .opt({\n    'output-file': {\n      short: 'o',\n      // optional: make it -o<file> in the help output insead of -o<value>\n      hint: 'file',\n      description: `Send the raw output to the specified file.`,\n    },\n  })\n\n// now we can parse argv like this:\nconst { values, positionals } = j.parse(process.argv)\n\n// or decide to show the usage banner\nconsole.log(j.usage())\n\n// or validate an object config we got from somewhere else\ntry {\n  j.validate(someConfig)\n} catch (er) {\n  console.error('someConfig is not valid!', er)\n}\n```\n\n## Name\n\nThe inspiration for this module is [yargs](http://npm.im/yargs), which\nis pirate talk themed. Yargs has all the features, and is infinitely\nflexible. \"Jackspeak\" is the slang of the royal navy. This module\ndoes not have all the features. It is declarative and rigid by design.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{e1/09/d463962d1436ffddc42c0141d19b46807d2a68292d4feea97378ada426e5e183bb8eb5c06589d6625ea899e6cdadb1a9981fbbe96f71a55b3ef4d9cbfda8 → 40/ed/8f91eae4e1bdbe9ccf3d33b20fb6751ed71d5df9fcc6d3d4becae3a8d9f4fdee16f3917d46b13a9f2cef9ae2d1e315f238cf935bd046446ff34028cefc42}

@@ -1172,7 +1172,7 @@
   "dist-tags": {
     "latest": "3.3.0"
   },
-  "_rev": "2933-94b404fe05f94877",
+  "_rev": "2938-ca026cadb9078fd2",
   "_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/{5f/34/96d8a02ed2ef7059605bd4e689181fe60c6b1c07c7666135d40a1a5ebb63121468ee162dbd0c6e342a190a5597e059b9faf15d1860fd8cfec6974c10e6e9 → 41/21/208e11bd27985a22e6125e7f19eec7b81bcb3b7bd137d7d5b9100fdf80cfe2a79085d17deffc9f7cab0d49c3778ef6bd9e3fc50ec05619eb44a91c3d9aae}

@@ -1209,7 +1209,7 @@
   "dist-tags": {
     "latest": "5.2.0"
   },
-  "_rev": "297-e3c8f1644ddb5eb2",
+  "_rev": "302-12c5d39b0b05d799",
   "_id": "@aws-crypto/supports-web-crypto",
   "readme": "# @aws-crypto/supports-web-crypto\n\nFunctions to check web crypto support for browsers.\n\n## Usage\n\n```\nimport {supportsWebCrypto} from '@aws-crypto/supports-web-crypto';\n\nif (supportsWebCrypto(window)) {\n  // window.crypto.subtle.encrypt will exist\n}\n\n```\n\n## supportsWebCrypto\n\nUsed to make sure `window.crypto.subtle` exists and implements crypto functions\nas well as a cryptographic secure random source exists.\n\n## supportsSecureRandom\n\nUsed to make sure that a cryptographic secure random source exists.\nDoes not check for `window.crypto.subtle`.\n\n## supportsSubtleCrypto\n\n## supportsZeroByteGCM\n\n## Test\n\n`npm test`",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{6f/44/2452f5f60d8538859b6fcfee66c1a80db5ef705073e622e56f060c6bbff847bab0b6f43ef3fc1784b3a247250815789e106dd97b601604fead26173ada32 → 43/18/2b1a2132e28be9c82eebf3e87a9e19f327af601208db8c68e0063e04676e1def8d92033f95c7d8446a7767d725874426ade33e7c3d61eb3032daf1e76468}

@@ -26300,7 +26300,7 @@
   "dist-tags": {
     "latest": "3.971.0"
   },
-  "_rev": "278-d91e9a7f81aff42b",
+  "_rev": "282-6b2371990351695a",
   "_id": "@aws-sdk/middleware-flexible-checksums",
   "readme": "# @aws-sdk/middleware-flexible-checksums\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/middleware-flexible-checksums/latest.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-flexible-checksums)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/middleware-flexible-checksums.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-flexible-checksums)\n\nThis package provides AWS SDK for JavaScript middleware that applies a checksum\nof the request body as a header.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{d7/d8/22be519aac5185f7671513ab21f6ca295be6653b5234589217a835efe811b354e4c9ed3a1a00f3eb6c10a36bc6bfe90e086262072deb3b5a71c4b1d15171 → 43/99/8b6eed725e790ad83b307e8f045e8f995b66f966ba2276faa8b18707328822ad321405bd84c2e610fa973ef55d2e8f77c4f6de73b5f5c1c482f1d8d7d013}

@@ -6734,7 +6734,7 @@
   "dist-tags": {
     "latest": "2.13.1"
   },
-  "_rev": "573-24a430b6d41430bf",
+  "_rev": "577-f32d302a93c3cf99",
   "_id": "bowser",
   "readme": "## Bowser\nA small, fast and rich-API browser/platform/engine detector for both browser and node.\n- **Small.** Use plain ES5-version which is ~4.8kB gzipped.\n- **Optimized.** Use only those parsers you need — it doesn't do useless work.\n- **Multi-platform.** It's browser- and node-ready, so you can use it in any environment.\n\nDon't hesitate to support the project on Github or [OpenCollective](https://opencollective.com/bowser) if you like it ❤️ Also, contributors are always welcome!\n\n[![Financial Contributors on Open Collective](https://opencollective.com/bowser/all/badge.svg?label=financial+contributors)](https://opencollective.com/bowser) [![Build Status](https://travis-ci.org/lancedikson/bowser.svg?branch=master)](https://travis-ci.org/lancedikson/bowser/)  [![Greenkeeper badge](https://badges.greenkeeper.io/lancedikson/bowser.svg)](https://greenkeeper.io/)  [![Coverage Status](https://coveralls.io/repos/github/lancedikson/bowser/badge.svg?branch=master)](https://coveralls.io/github/lancedikson/bowser?branch=master) ![Downloads](https://img.shields.io/npm/dm/bowser)\n\n# Contents\n- [Overview](#overview)\n- [Use cases](#use-cases)\n\n# Overview\n\nThe library is made to help to detect what browser your user has and gives you a convenient API to filter the users somehow depending on their browsers. Check it out on this page: https://bowser-js.github.io/bowser-online/.\n\n### ⚠️ Version 2.0 breaking changes ⚠️\n\nVersion 2.0 has drastically changed the API. All available methods are on the [docs page](https://bowser-js.github.io/bowser/docs/).\n\n_For legacy code, check out the [1.x](https://github.com/lancedikson/bowser/tree/v1.x) branch and install it through `npm install bowser@1.9.4`._\n\n# Use cases\n\nFirst of all, require the library. This is a UMD Module, so it will work for AMD, TypeScript, ES6, and CommonJS module systems.\n\n```javascript\nconst Bowser = require(\"bowser\"); // CommonJS\n\nimport * as Bowser from \"bowser\"; // TypeScript\n\nimport Bowser from \"bowser\"; // ES6 (and TypeScript with --esModuleInterop enabled)\n```\n\nBy default, the exported version is the *ES5 transpiled version*, which **do not** include any polyfills.\n\nIn case you don't use your own `babel-polyfill` you may need to have pre-built bundle with all needed polyfills.\nSo, for you it's suitable to require bowser like this: `require('bowser/bundled')`.\nAs the result, you get a ES5 version of bowser with `babel-polyfill` bundled together.\n\nYou may need to use the source files, so they will be available in the package as well.\n\n## Browser props detection\n\nOften we need to pick users' browser properties such as the name, the version, the rendering engine and so on. Here is an example how to do it with Bowser:\n\n```javascript\nconst browser = Bowser.getParser(window.navigator.userAgent);\n\nconsole.log(`The current browser name is \"${browser.getBrowserName()}\"`);\n// The current browser name is \"Internet Explorer\"\n```\n\nor\n\n```javascript\nconst browser = Bowser.getParser(window.navigator.userAgent);\nconsole.log(browser.getBrowser());\n\n// outputs\n{\n  name: \"Internet Explorer\"\n  version: \"11.0\"\n}\n```\n\nor\n\n```javascript\nconsole.log(Bowser.parse(window.navigator.userAgent));\n\n// outputs\n{\n  browser: {\n    name: \"Internet Explorer\"\n    version: \"11.0\"\n  },\n  os: {\n    name: \"Windows\"\n    version: \"NT 6.3\"\n    versionName: \"8.1\"\n  },\n  platform: {\n    type: \"desktop\"\n  },\n  engine: {\n    name: \"Trident\"\n    version: \"7.0\"\n  }\n}\n```\n\n\n## Filtering browsers\n\nYou could want to filter some particular browsers to provide any special support for them or make any workarounds.\nIt could look like this:\n\n```javascript\nconst browser = Bowser.getParser(window.navigator.userAgent);\nconst isValidBrowser = browser.satisfies({\n  // declare browsers per OS\n  windows: {\n    \"internet explorer\": \">10\",\n  },\n  macos: {\n    safari: \">10.1\"\n  },\n\n  // per platform (mobile, desktop or tablet)\n  mobile: {\n    safari: '>=9',\n    'android browser': '>3.10'\n  },\n\n  // or in general\n  chrome: \"~20.1.1432\",\n  firefox: \">31\",\n  opera: \">=22\",\n\n  // also supports equality operator\n  chrome: \"=20.1.1432\", // will match particular build only\n\n  // and loose-equality operator\n  chrome: \"~20\",        // will match any 20.* sub-version\n  chrome: \"~20.1\"       // will match any 20.1.* sub-version (20.1.19 as well as 20.1.12.42-alpha.1)\n});\n```\n\nSettings for any particular OS or platform has more priority and redefines settings of standalone browsers.\nThus, you can define OS or platform specific rules and they will have more priority in the end.\n\nMore of API and possibilities you will find in the `docs` folder.\n\n### Browser names for `.satisfies()`\n\nBy default you are supposed to use the full browser name for `.satisfies`.\nBut, there's a short way to define a browser using short aliases. The full\nlist of aliases can be found in [the file](src/constants.js).\n\n## Similar Projects\n* [Kong](https://github.com/BigBadBleuCheese/Kong) - A C# port of Bowser.\n\n## Contributors\n\n### Code Contributors\n\nThis project exists thanks to all the people who contribute. [[Contribute](.github/CONTRIBUTING.md)].\n<a href=\"https://github.com/lancedikson/bowser/graphs/contributors\"><img src=\"https://opencollective.com/bowser/contributors.svg?width=890&button=false\" /></a>\n\n### Financial Contributors\n\nBecome a financial contributor and help us sustain our community. [[Contribute](https://opencollective.com/bowser/contribute)]\n\n#### Individuals\n\n<a href=\"https://opencollective.com/bowser\"><img src=\"https://opencollective.com/bowser/individuals.svg?width=890\"></a>\n\n#### Organizations\n\nSupport this project with your organization. Your logo will show up here with a link to your website. [[Contribute](https://opencollective.com/bowser/contribute)]\n\n<a href=\"https://opencollective.com/bowser/organization/0/website\"><img src=\"https://opencollective.com/bowser/organization/0/avatar.svg\"></a>\n<a href=\"https://opencollective.com/bowser/organization/1/website\"><img src=\"https://opencollective.com/bowser/organization/1/avatar.svg\"></a>\n<a href=\"https://opencollective.com/bowser/organization/2/website\"><img src=\"https://opencollective.com/bowser/organization/2/avatar.svg\"></a>\n<a href=\"https://opencollective.com/bowser/organization/3/website\"><img src=\"https://opencollective.com/bowser/organization/3/avatar.svg\"></a>\n<a href=\"https://opencollective.com/bowser/organization/4/website\"><img src=\"https://opencollective.com/bowser/organization/4/avatar.svg\"></a>\n<a href=\"https://opencollective.com/bowser/organization/5/website\"><img src=\"https://opencollective.com/bowser/organization/5/avatar.svg\"></a>\n<a href=\"https://opencollective.com/bowser/organization/6/website\"><img src=\"https://opencollective.com/bowser/organization/6/avatar.svg\"></a>\n<a href=\"https://opencollective.com/bowser/organization/7/website\"><img src=\"https://opencollective.com/bowser/organization/7/avatar.svg\"></a>\n<a href=\"https://opencollective.com/bowser/organization/8/website\"><img src=\"https://opencollective.com/bowser/organization/8/avatar.svg\"></a>\n<a href=\"https://opencollective.com/bowser/organization/9/website\"><img src=\"https://opencollective.com/bowser/organization/9/avatar.svg\"></a>\n\n## License\nLicensed as MIT. All rights not explicitly granted in the MIT license are reserved. See the included LICENSE file for more details.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{a9/c2/4ed9c33684b97667665fb08e8ee2c9bdd81439fec11aeb793d4dddc41ea63c2c411828001d340806f5b99cce2e55d01048e51f956164b2c8356aab0f8483 → 46/41/532352385ed5281b7078f4cf4cce8f7bb86cacbdbd31dca41089633ef54b75d2042a3cca936a246b9e7c20873e8078ab4da7898d3ac6680c21c3c3ed194f}

@@ -7424,7 +7424,7 @@
   "dist-tags": {
     "latest": "4.3.8"
   },
-  "_rev": "175-0a7736e4eeb87470",
+  "_rev": "179-76ae2d426fcf8a37",
   "_id": "@smithy/node-config-provider",
   "readme": "# @smithy/node-config-provider\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/node-config-provider/latest.svg)](https://www.npmjs.com/package/@smithy/node-config-provider)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/node-config-provider.svg)](https://www.npmjs.com/package/@smithy/node-config-provider)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{b6/4f/c4429080b80228fd252b5679cfd0467fcbeb5e730e6257f88e9b9fca695adb5aed6e22ca6ac4e61ef4d169a4b5cefa144e398cbbb7073377ea2f35039ce8 → 47/f8/85cd995cf3f1dbe43902bf0eb2db64123d05e1cd1477ef6689b93639b9fb0dc5853f7c140a2685c7bdf0799d5a0b890d573aab0a12c2b8f536a03f034ad3}

@@ -1805,7 +1805,7 @@
   "dist-tags": {
     "latest": "4.3.0"
   },
-  "_rev": "167-6656acb3434e4b63",
+  "_rev": "171-ba72dcc3e1239e9c",
   "_id": "@smithy/util-base64",
   "readme": "# @smithy/util-base64\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/util-base64/latest.svg)](https://www.npmjs.com/package/@smithy/util-base64)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/util-base64.svg)](https://www.npmjs.com/package/@smithy/util-base64)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{e4/89/76b9f6fea1e6fa9cffd3b86d23c2c55341f937823af9de2440b2ede61388184da2b35c709f46e6ce10cad3f73d7107686c405eb26996bdc723fd7f875a79 → 48/c8/d9aa1b7f009a45174f9520d4c718b7b9d48120bf401be5df65a9c9b5d9037c36119a3d0fdd78c57448ca8881f1a6921d9b7e60ef3b58c9c27fa3633d6de5}

@@ -6131,7 +6131,7 @@
   "dist-tags": {
     "latest": "4.2.8"
   },
-  "_rev": "174-57968f2e2270ba3a",
+  "_rev": "178-75b104ae5486d11f",
   "_id": "@smithy/eventstream-serde-browser",
   "readme": "# @smithy/eventstream-serde-browser\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/eventstream-serde-browser/latest.svg)](https://www.npmjs.com/package/@smithy/eventstream-serde-browser)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/eventstream-serde-browser.svg)](https://www.npmjs.com/package/@smithy/eventstream-serde-browser)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{e7/28/aaaa26e975e86fb4169ee727ea69a8a0a89a5b752f2083e4dbe3f911c27fbe352926770f941330a835245ac2bb16903316451e9cf1274b975630c6c65d7e → 48/dc/2dd19fd34ee2c03db022d9daa71f182308573dc838e8432661567dcb57c67873b4cf782c3c6a5b30de81e6d424cb43e251b0a0d00a9fd2046629974d2762}

@@ -1189,7 +1189,7 @@
   "dist-tags": {
     "latest": "2.1.2"
   },
-  "_rev": "738-444952406eb42cbe",
+  "_rev": "742-66aac619f9cf3da1",
   "_id": "strnum",
   "readme": "# strnum\nParse string into Number based on configuration\n\n## Users\n\n<a href=\"https://github.com/aws-amplify\" target=\"_blank\"><img src=\"https://avatars.githubusercontent.com/u/41077760?s=100&v=4\"></a>\n<a href=\"https://github.com/astrapay\" target=\"_blank\"><img src=\"https://avatars.githubusercontent.com/u/90901882?s=100&v=4\"></a>\n<a href=\"https://github.com/process-analytics\" target=\"_blank\"><img src=\"https://avatars.githubusercontent.com/u/60110287?s=100&v=4\"></a>\n<a href=\"https://github.com/NaturalIntelligence\" target=\"_blank\"><img src=\"https://avatars.githubusercontent.com/u/16322633?s=100&v=4\"></a>\nMany React Native projects and plugins\n\n## Usage\n\n```bash\nnpm install strnum\n```\n```js\nconst toNumber = require(\"strnum\");\n\ntoNumber(undefined) // undefined\ntoNumber(null)) //null\ntoNumber(\"\")) // \"\"\ntoNumber(\"string\"); //\"string\")\ntoNumber(\"12,12\"); //\"12,12\")\ntoNumber(\"12 12\"); //\"12 12\")\ntoNumber(\"12-12\"); //\"12-12\")\ntoNumber(\"12.12.12\"); //\"12.12.12\")\ntoNumber(\"0x2f\"); //47)\ntoNumber(\"-0x2f\"); //-47)\ntoNumber(\"0x2f\", { hex :  true}); //47)\ntoNumber(\"-0x2f\", { hex :  true}); //-47)\ntoNumber(\"0x2f\", { hex :  false}); //\"0x2f\")\ntoNumber(\"-0x2f\", { hex :  false}); //\"-0x2f\")\ntoNumber(\"06\"); //6)\ntoNumber(\"06\", { leadingZeros :  true}); //6)\ntoNumber(\"06\", { leadingZeros :  false}); //\"06\")\n\ntoNumber(\"006\"); //6)\ntoNumber(\"006\", { leadingZeros :  true}); //6)\ntoNumber(\"006\", { leadingZeros :  false}); //\"006\")\ntoNumber(\"0.0\"); //0)\ntoNumber(\"00.00\"); //0)\ntoNumber(\"0.06\"); //0.06)\ntoNumber(\"00.6\"); //0.6)\ntoNumber(\".006\"); //0.006)\ntoNumber(\"6.0\"); //6)\ntoNumber(\"06.0\"); //6)\n\ntoNumber(\"0.0\",  { leadingZeros :  false}); //0)\ntoNumber(\"00.00\",  { leadingZeros :  false}); //\"00.00\")\ntoNumber(\"0.06\",  { leadingZeros :  false}); //0.06)\ntoNumber(\"00.6\",  { leadingZeros :  false}); //\"00.6\")\ntoNumber(\".006\", { leadingZeros :  false}); //0.006)\ntoNumber(\"6.0\"  ,  { leadingZeros :  false}); //6)\ntoNumber(\"06.0\"  ,  { leadingZeros :  false}); //\"06.0\")\ntoNumber(\"-06\"); //-6)\ntoNumber(\"-06\", { leadingZeros :  true}); //-6)\ntoNumber(\"-06\", { leadingZeros :  false}); //\"-06\")\n\ntoNumber(\"-0.0\"); //-0)\ntoNumber(\"-00.00\"); //-0)\ntoNumber(\"-0.06\"); //-0.06)\ntoNumber(\"-00.6\"); //-0.6)\ntoNumber(\"-.006\"); //-0.006)\ntoNumber(\"-6.0\"); //-6)\ntoNumber(\"-06.0\"); //-6)\n\ntoNumber(\"-0.0\"   ,  { leadingZeros :  false}); //-0)\ntoNumber(\"-00.00\",  { leadingZeros :  false}); //\"-00.00\")\ntoNumber(\"-0.06\",  { leadingZeros :  false}); //-0.06)\ntoNumber(\"-00.6\",  { leadingZeros :  false}); //\"-00.6\")\ntoNumber(\"-.006\",  {leadingZeros :  false}); //-0.006)\ntoNumber(\"-6.0\"  ,  { leadingZeros :  false}); //-6)\ntoNumber(\"-06.0\"  ,  { leadingZeros :  false}); //\"-06.0\")\ntoNumber(\"420926189200190257681175017717\")  ; //4.209261892001902e+29)\ntoNumber(\"000000000000000000000000017717\"  ,  { leadingZeros :  false}); //\"000000000000000000000000017717\")\ntoNumber(\"000000000000000000000000017717\"  ,  { leadingZeros :  true}); //17717)\ntoNumber(\"01.0e2\"  ,  { leadingZeros :  false}); //\"01.0e2\")\ntoNumber(\"-01.0e2\"  ,  { leadingZeros :  false}); //\"-01.0e2\")\ntoNumber(\"01.0e2\") ; //100)\ntoNumber(\"-01.0e2\") ; //-100)\ntoNumber(\"1.0e2\") ; //100)\n\ntoNumber(\"-1.0e2\") ; //-100)\ntoNumber(\"1.0e-2\"); //0.01)\n\ntoNumber(\"+1212121212\"); // 1212121212\ntoNumber(\"+1212121212\", { skipLike: /\\+[0-9]{10}/} )); //\"+1212121212\"\n```\n\nSupported Options\n```js\nhex: true,          //when hexadecimal string should be parsed\nleadingZeros: true, //when number with leading zeros like 08 should be parsed. 0.0 is not impacted\neNotation: true,    //when number with eNotation or number parsed in eNotation should be considered\nskipLike: /regex/   //when string should not be parsed when it matches the specified regular expression\n```\n\n\n# Try out our other work\n\nWishIn - You need it if negative thoughts take over all the time <br>\n<a href=\"https://play.google.com/store/apps/details?id=com.solothought.wishin\"> <img src=\"https://solothought.com/products/assets/images/wishin/YouTubeThumbnail.png\" width=\"500px\"/> </a>",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{3c/f2/2ef4768434b10389b10b7d802736863b3e9072f539d72f10748699bccca224502d57d4a90d64100905c2c36f2a7a07b89104a56ed2844594a7b18ff2a01c → 48/f5/0df715731af3ebbc2fb8dac56dc76ab66921d1fe789ca85b7b0f30e5225ddd5d64a9190beaea0923d3a11cd19bdc61db161c02afbe378832e9024ede99fe}

@@ -385,7 +385,7 @@
   "dist-tags": {
     "latest": "1.3.2"
   },
-  "_rev": "621-07644aa6b44cdede",
+  "_rev": "625-68b3b07d34b5239c",
   "_id": "fast-fifo",
   "readme": "# fast-fifo\n\nA fast fifo implementation similar to the one powering nextTick in Node.js core\n\n```\nnpm install fast-fifo\n```\n\nUses a linked list of growing fixed sized arrays to implement the FIFO to avoid\nallocating a wrapper object for each item.\n\n## Usage\n\n``` js\nconst FIFO = require('fast-fifo')\n\nconst q = new FIFO()\n\nq.push('hello')\nq.push('world')\n\nq.shift() // returns hello\nq.shift() // returns world\n```\n\n## API\n\n#### `q = new FIFO()`\n\nCreate a new FIFO.\n\n#### `q.push(value)`\n\nPush a value to the FIFO. `value` can be anything other than undefined.\n\n#### `value = q.shift()`\n\nReturn the oldest value from the FIFO.\n\n#### `q.clear()`\n\nRemove all values from the FIFO.\n\n#### `bool = q.isEmpty()`\n\nReturns `true` if the FIFO is empty and false otherwise.\n\n#### `value = q.peek()`\n\nReturn the oldest value from the FIFO without shifting it out.\n\n#### `len = q.length`\n\nGet the number of entries remaining in the FIFO.\n\n## Benchmarks\n\nIncluded in bench.js is a simple benchmark that benchmarks this against a simple\nlinked list based FIFO.\n\nOn my machine the benchmark looks like this:\n\n```\nfifo bulk push and shift: 2881.508ms\nfifo individual push and shift: 3248.437ms\nfast-fifo bulk push and shift: 1606.972ms\nfast-fifo individual push and shift: 1328.064ms\nfifo bulk push and shift: 3266.902ms\nfifo individual push and shift: 3320.944ms\nfast-fifo bulk push and shift: 1858.307ms\nfast-fifo individual push and shift: 1516.983ms\n```\n\nYMMV\n\n## License\n\nMIT",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{3a/c6/6b4e37ebd53ec1194a9ee3da8b7da475281e08cbfe69cb2af2509d9c9880f082d3fda0639e6ce8fe3dcfa73b0cc83959a576106c1d8107733397fd8a84ce → 4f/72/c28c3e89ee1c400bf8f4e768eb53f043679f26beb6cc44fd2198c4cf1255899e866abff2dac9b6e43c015f85cac4c28dced73dafbd4e55a4d2a052985353}

@@ -1807,7 +1807,7 @@
   "dist-tags": {
     "latest": "6.2.2"
   },
-  "_rev": "3620-628fe4d85eb2232d",
+  "_rev": "3628-be871ead0957713e",
   "_id": "ansi-regex",
   "readme": "",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{f8/93/e1202098c9d1cdcec4336db1d023f5f03c874e098abd17ad14dc9caefea3650166fd1e6933afd15abfb9c3426bcfade9eaa150271123de1896030419a856 → 50/f1/15e82bd9ce4a5d675b7b66796a8c2206316839ef32df637cab84d5f61333bf96d893fb658483be8acc5bc755d7c6b6206bf283ebfbd56de00afc420dd1ae}

@@ -5851,7 +5851,7 @@
   "dist-tags": {
     "latest": "4.2.8"
   },
-  "_rev": "191-493b1d2be3d9d783",
+  "_rev": "196-058f43c9c97b91b5",
   "_id": "@smithy/abort-controller",
   "readme": "# @smithy/abort-controller\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/abort-controller/latest.svg)](https://www.npmjs.com/package/@smithy/abort-controller)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/abort-controller.svg)](https://www.npmjs.com/package/@smithy/abort-controller)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{23/e1/1d913002425115bfbf50ad572772d7a07597a6ce65e8792ba4769f75dd73b9b998f5f8091aecb714e0a314b8130b973e362d9b0a4c2394dd5bd1f7bd594d → 50/fb/d28c2c33c92c2f3c61546028548caacfa17eb7981a404705a79becd6d0ea11852c07a882ccaea433118dae9d374435e6a7d693a607a4ca0f93c9c9dffc56}

@@ -154,7 +154,7 @@
   "dist-tags": {
     "latest": "1.0.1"
   },
-  "_rev": "321-8a37d5c84d0ba8e7",
+  "_rev": "325-7d74ba9b435aed5a",
   "_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/{b1/1d/05330f3f626abb086cf99532d42ab48e8623ef3a5dccec9984b2e6503f0a4deb9fa074ee8809574e99b2509ce100ce8c819efc9bffe7bd6cd9fa634297e1 → 51/a8/ca657308cdb7bac5ceb9a869d5a18bc62574d7800e6777a6aa26d00aafc79d5a062754289ab381b7e9f7ea2f280d0f87c0d916f4855b460f648c2155c085}

@@ -35723,7 +35723,7 @@
   "dist-tags": {
     "latest": "3.971.0"
   },
-  "_rev": "313-08443214f7f4de75",
+  "_rev": "317-34064415466063e9",
   "_id": "@aws-sdk/token-providers",
   "readme": "# @aws-sdk/token-providers\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/token-providers/latest.svg)](https://www.npmjs.com/package/@aws-sdk/token-providers)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/token-providers.svg)](https://www.npmjs.com/package/@aws-sdk/token-providers)\n\nA collection of all token providers. The token providers should be used when the authorization\ntype is going to be token based. For example, the `bearer` authorization type set using\n[httpBearerAuth trait][http-bearer-auth-trait] in Smithy.\n\n## Static Token Provider\n\n```ts\nimport { fromStatic } from \"@aws-sdk/token-providers\";\n\nconst token = { token: \"TOKEN\" };\nconst staticTokenProvider = fromStatic(token);\n\nconst staticToken = await staticTokenProvider(); // returns { token: \"TOKEN\" }\n```\n\n## SSO Token Provider\n\n```ts\nimport { fromSso } from \"@aws-sdk/token-providers\";\n\n// returns token from SSO token cache or ssoOidc.createToken() call.\nconst ssoToken = await fromSso();\n```\n\n## Env Token Provider with Signing Name\n\n```ts\nimport { fromEnvSigningName } from \"@aws-sdk/token-providers\";\n\n// returns token from environment, where token's key is based on signing name.\nconst envSigningNameToken = await fromEnvSigningName({ signingName: \"signing name\" });\n```\n\n## Token Provider Chain\n\n```ts\nimport { nodeProvider } from \"@aws-sdk/token-providers\";\n\n// returns token from default providers.\nconst token = await nodeProvider();\n```\n\n[http-bearer-auth-trait]: https://smithy.io/2.0/spec/authentication-traits.html#smithy-api-httpbearerauth-trait\n\n---\n\n### Development\n\nThis package contains a minimal copy of the SSO OIDC client, instead of relying on the full client, which\nwould cause a circular dependency.\n\nWhen regenerating the bundled version of the SSO OIDC client, run the esbuild.js script and then make the following changes:\n\n- Remove any dependency of the generated client on the credential chain such that it would create\n  a circular dependency back to this package. Because we only need the `CreateTokenCommand`, the client, and this command's\n  associated `Exception`s, it is possible to remove auth dependencies.\n- Ensure all required packages are declared in the `package.json` of token-providers.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{22/5b/6ee456f8bc7ff43a81f1504413b31f38a8b0cf5dbbe251d9d5eedd2da08ef5a3ece114907c4a73b3e4449f4c24a361e8a8ca2ef60c264a5597734d224b4b → 53/53/f9c094d84c19c5ae744e3798b5137a8c08a07e954b581005f7afafb78980bf73a1b90bf333118dac8d5f7e9c66d1a988ff8736c871f5b3a6116f2c69560e}

@@ -7766,7 +7766,7 @@
     "latest": "6.1.2",
     "v5-legacy": "5.0.10"
   },
-  "_rev": "3548-8b3fae9852ebbecd",
+  "_rev": "3553-18ff4fc2cd053ff3",
   "_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/{da/d5/369251ff95220cc7e02e98b0ceba60b9c8b692bc64a11de234e739a47312bd318273851fc5903bee769f0aef354f4eb43d9ad98a63230fb87c16f1f745a4 → 54/08/c24e02336279db2bf31c34c1e8427ca7585435c94cff382c65a0a4c5fd7e3d7e65e8345872603ed8a944a0d9bd662c98b3934133001680e11823a0c6736b}

@@ -350,7 +350,7 @@
   "dist-tags": {
     "latest": "1.0.1"
   },
-  "_rev": "278-4a8107bbcb1ab102",
+  "_rev": "282-615b902b7460cfb4",
   "_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/{c2/a7/be32aa4edb3790ef316ccdb0a53ba469e5312e5379c0d5325718ba3b722c2f21f387f05d4db43547ce8f1202f033ce167efe1453f6cb56b728a908c62401 → 54/17/55a2cd3b0ea81bf971863e876a0871f6d8efc3ffb5db207050fe37199fdf0d2c0ef04d7c14cd2595b490bf820906663034b5ac57bcf9ab7822f7667c4187}

@@ -226,7 +226,7 @@
   "dist-tags": {
     "latest": "1.0.1"
   },
-  "_rev": "841-8257d7c19f2bd451",
+  "_rev": "846-2c62f751cd86116c",
   "_id": "package-json-from-dist",
   "readme": "# package-json-from-dist\n\nSometimes you want to load the `package.json` into your\nTypeScript program, and it's tempting to just `import\n'../package.json'`, since that seems to work.\n\nHowever, this requires `tsc` to make an entire copy of your\n`package.json` file into the `dist` folder, which is a problem if\nyou're using something like\n[tshy](https://github.com/isaacs/tshy), which uses the\n`package.json` file in dist for another purpose. Even when that\ndoes work, it's asking the module system to do a bunch of extra\nfs system calls, just to load a version number or something. (See\n[this issue](https://github.com/isaacs/tshy/issues/61).)\n\nThis module helps by just finding the package.json file\nappropriately, and reading and parsing it in the most normal\nfashion.\n\n## Caveats\n\nThis _only_ works if your code builds into a target folder called\n`dist`, which is in the root of the package. It also requires\nthat you do not have a folder named `node_modules` anywhere\nwithin your dev environment, or else it'll get the wrong answers\nthere. (But, at least, that'll be in dev, so you're pretty likely\nto notice.)\n\nIf you build to some other location, then you'll need a different\napproach. (Feel free to fork this module and make it your own, or\njust put the code right inline, there's not much of it.)\n\n## USAGE\n\n```js\n// src/index.ts\nimport {\n  findPackageJson,\n  loadPackageJson,\n} from 'package-json-from-dist'\n\nconst pj = findPackageJson(import.meta.url)\nconsole.log(`package.json found at ${pj}`)\n\nconst pkg = loadPackageJson(import.meta.url)\nconsole.log(`Hello from ${pkg.name}@${pkg.version}`)\n```\n\nIf your module is not directly in the `./src` folder, then you need\nto specify the path that you would expect to find the\n`package.json` when it's _not_ built to the `dist` folder.\n\n```js\n// src/components/something.ts\nimport {\n  findPackageJson,\n  loadPackageJson,\n} from 'package-json-from-dist'\n\nconst pj = findPackageJson(import.meta.url, '../../package.json')\nconsole.log(`package.json found at ${pj}`)\n\nconst pkg = loadPackageJson(import.meta.url, '../../package.json')\nconsole.log(`Hello from ${pkg.name}@${pkg.version}`)\n```\n\nWhen running from CommmonJS, use `__filename` instead of\n`import.meta.url`.\n\n```js\n// src/index.cts\nimport {\n  findPackageJson,\n  loadPackageJson,\n} from 'package-json-from-dist'\n\nconst pj = findPackageJson(__filename)\nconsole.log(`package.json found at ${pj}`)\n\nconst pkg = loadPackageJson(__filename)\nconsole.log(`Hello from ${pkg.name}@${pkg.version}`)\n```\n\nSince [tshy](https://github.com/isaacs/tshy) builds _both_\nCommonJS and ESM by default, you may find that you need a\nCommonJS override and some `//@ts-ignore` magic to make it work.\n\n`src/pkg.ts`:\n\n```js\nimport {\n  findPackageJson,\n  loadPackageJson,\n} from 'package-json-from-dist'\n//@ts-ignore\nexport const pkg = loadPackageJson(import.meta.url)\n//@ts-ignore\nexport const pj = findPackageJson(import.meta.url)\n```\n\n`src/pkg-cjs.cts`:\n\n```js\nimport {\n  findPackageJson,\n  loadPackageJson,\n} from 'package-json-from-dist'\nexport const pkg = loadPackageJson(__filename)\nexport const pj = findPackageJson(__filename)\n```",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{0c/0a/9d6970f80058a83f90549fb1a3e05d5c878050ecd7569760fb28cff2bf8d8b0ece161e8147ef98e678f1d83c14d0895cef7551bb29824160198c02b60f81 → 56/ee/1cb9d348d7172b92127ff34557df8acd53ca0dd963bbaba9fb1686836f0684d033ee0645b69d72bdaf6b0c0e3206a87b1cb9b306efdf376fe321f0871d4a}

@@ -5995,7 +5995,7 @@
   "dist-tags": {
     "latest": "4.2.8"
   },
-  "_rev": "191-199b0909ecbf8307",
+  "_rev": "195-667919e71da5283a",
   "_id": "@smithy/property-provider",
   "readme": "# @smithy/property-provider\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/property-provider/latest.svg)](https://www.npmjs.com/package/@smithy/property-provider)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/property-provider.svg)](https://www.npmjs.com/package/@smithy/property-provider)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{fd/4e/6175e2f232f528ff1edcf73cab0e98b7ff9335cb438701af3e9770f3b305bda5e284176c8a8f37e299a7704d880e36439224d26dd334a1eb3b57ec1e2ca4 → 5c/43/48b82ce75f2410501e2c7826e45c3be31975d56b72f9731a33456e68683e6a3c7c76df53a99f5a9a5762a147bd5cb1b34ccaa7de5a8471a1e027713488d2}

@@ -5897,7 +5897,7 @@
   "dist-tags": {
     "latest": "4.2.8"
   },
-  "_rev": "175-b95a718a910e80c2",
+  "_rev": "179-2b6f4562cea3e3db",
   "_id": "@smithy/util-retry",
   "readme": "# @smithy/util-retry\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/util-retry/latest.svg)](https://www.npmjs.com/package/@smithy/util-retry)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/util-retry.svg)](https://www.npmjs.com/package/@smithy/util-retry)\n\nThis package provides shared utilities for retries.\n\n## Usage\n\n### Default\n\nBy default, each client already has a default retry strategy. The default retry count is 3, and\nonly retryable errors will be retried.\n\n[AWS Documentation: Retry behavior](https://docs.aws.amazon.com/sdkref/latest/guide/feature-retry-behavior.html).\n\n```js\nimport { S3Client } from \"@aws-sdk/client-s3\";\n\nconst client = new S3Client({}); // default retry strategy included.\n```\n\n### MaxAttempts\n\nIf you want to change the number of attempts, you can provide `maxAttempts` configuration during client creation.\n\n```js\nimport { S3Client } from \"@aws-sdk/client-s3\";\n\nconst client = new S3Client({ maxAttempts: 4 });\n```\n\nThis is recommended because the `StandardRetryStrategy` includes backoff calculation,\ndeciding whether an error should be retried, and a retry token counter.\n\n### MaxAttempts and BackoffComputation\n\nIf you want to change the number of attempts and use a custom delay\ncomputation, you can use the `ConfiguredRetryStrategy` from `@smithy/util-retry`.\n\n```js\nimport { S3Client } from \"@aws-sdk/client-s3\";\nimport { ConfiguredRetryStrategy } from \"@smithy/util-retry\";\n\nconst client = new S3Client({\n  retryStrategy: new ConfiguredRetryStrategy(\n    4, // max attempts.\n    (attempt: number) => 100 + attempt * 1000 // backoff function.\n  ),\n});\n```\n\nThis example sets the backoff at 100ms plus 1s per attempt.\n\n### MaxAttempts and RetryStrategy\n\nIf you provide both `maxAttempts` and `retryStrategy`, the `retryStrategy` will\nget precedence as it's more specific.\n\n```js\nimport { S3Client } from \"@aws-sdk/client-s3\";\nimport { ConfiguredRetryStrategy } from \"@smithy/util-retry\";\n\nconst client = new S3Client({\n  maxAttempts: 2, // ignored.\n  retryStrategy: new ConfiguredRetryStrategy(\n    4, // used.\n    (attempt: number) => 100 + attempt * 1000 // backoff function.\n  ),\n});\n```\n\n### Further customization\n\nYou can implement the `RetryStrategyV2` interface.\n\nSource: https://github.com/smithy-lang/smithy-typescript/blob/main/packages/types/src/retry.ts\nAPI Docs: https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-smithy-types/Interface/RetryStrategyV2/",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{dc/7e/f5f5935de2e350a46a69b30f7b726cbedc404ae88d9a0c13eb60560b5bf9a929ec83b2ccc432b2ba9eb3288dc548bd78a0d62fc5a636af1cf707a9fa18a0 → 5d/4d/e9d28a7547a5883cc999ae1711ae0199326a77dbf0a00b364653dca888af2edb4588847c9e9076a70347e94dbaf2c92f2bf89016a6beffc4f83a5a405246}

@@ -7605,7 +7605,7 @@
   "dist-tags": {
     "latest": "4.4.6"
   },
-  "_rev": "184-9f7fc8f71f36de90",
+  "_rev": "188-0ab84cad5f16bb4d",
   "_id": "@smithy/config-resolver",
   "readme": "# @smithy/config-resolver\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/config-resolver/latest.svg)](https://www.npmjs.com/package/@smithy/config-resolver)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/config-resolver.svg)](https://www.npmjs.com/package/@smithy/config-resolver)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{c6/12/2cfe4e375436050ba7366b0e6e743698a229e0e223c65bcd5d88f0d295f20978e7a6463781807a820f397afdf46300ee51e9116564f5521ff938655d67b2 → 5e/87/fe89c2f6c818f3a1a22097cc97b7ef248ce37ee650d6a9567678f68f74d6f11b7fcca8504f17c038adca382c4d4fcb3da0eafd4504362a6ae27a41ef6211}

@@ -1470,7 +1470,7 @@
   "dist-tags": {
     "latest": "1.5.1"
   },
-  "_rev": "2649-a0eabca225ebc1b9",
+  "_rev": "2653-34f4ad16f6689410",
   "_id": "base64-js",
   "readme": "base64-js\n=========\n\n`base64-js` does basic base64 encoding/decoding in pure JS.\n\n[![build status](https://secure.travis-ci.org/beatgammit/base64-js.png)](http://travis-ci.org/beatgammit/base64-js)\n\nMany browsers already have base64 encoding/decoding functionality, but it is for text data, not all-purpose binary data.\n\nSometimes encoding/decoding binary data in the browser is useful, and that is what this module does.\n\n## install\n\nWith [npm](https://npmjs.org) do:\n\n`npm install base64-js` and `var base64js = require('base64-js')`\n\nFor use in web browsers do:\n\n`<script src=\"base64js.min.js\"></script>`\n\n[Get supported base64-js with the Tidelift Subscription](https://tidelift.com/subscription/pkg/npm-base64-js?utm_source=npm-base64-js&utm_medium=referral&utm_campaign=readme)\n\n## methods\n\n`base64js` has three exposed functions, `byteLength`, `toByteArray` and `fromByteArray`, which both take a single argument.\n\n* `byteLength` - Takes a base64 string and returns length of byte array\n* `toByteArray` - Takes a base64 string and returns a byte array\n* `fromByteArray` - Takes a byte array and returns a base64 string\n\n## license\n\nMIT",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{2c/84/8bef202dc482d57dcf4312889ee4e013367b8f1e60c68d57863be5726842cc866bdcff80974c4052b17f27ca370cb44a5e021195d1409d6b599f09ecb341 → 5f/be/7aaa304b21e3c82de0b4c59dde05f0ece854f28e44386dd7220eebfe501c7ff77d9f75a562ec96b60128c41bfbbfa14a05c36dd5d81605d8119f1a764bd6}

@@ -5294,7 +5294,7 @@
   "dist-tags": {
     "latest": "3.2.8"
   },
-  "_rev": "167-3663ee08c992c1c6",
+  "_rev": "171-08ffea3385d19953",
   "_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/{2a/f0/2d57030d0b407f7da65bc1c1f720c9aa3a1cf1768b8653e31e13a8b63f10f9beb0f4e8f9493e50a32a9d8f7de9a0ac92737b88319add775600f2b00bdd1b → 61/89/f4e6dcef6d8049cb443eadd5cd7141551f2b99fbfbc5e51eb8a0f0e4f41ed9b8c70c950653b3f6a351e1ac4bb286ab1d5fc2eb2df63f439b370b66474da0}

@@ -15233,7 +15233,7 @@
   "dist-tags": {
     "latest": "3.20.7"
   },
-  "_rev": "189-9ea217306213dddf",
+  "_rev": "193-f8b9897209f93785",
   "_id": "@smithy/core",
   "readme": "# @smithy/core\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/core/latest.svg)](https://www.npmjs.com/package/@smithy/core)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/core.svg)](https://www.npmjs.com/package/@smithy/core)\n\n> An internal package. You probably shouldn't use this package, at least directly.\n\nThis package provides common or core functionality for generic Smithy clients.\n\nYou do not need to explicitly install this package, since it will be installed during code generation if used.\n\n## Development of `@smithy/core` submodules\n\nCore submodules are organized for distribution via the `package.json` `exports` field.\n\n`exports` is supported by default by the latest Node.js, webpack, and esbuild. For react-native, it can be\nenabled via instructions found at [reactnative.dev/blog](https://reactnative.dev/blog/2023/06/21/package-exports-support), but we also provide a compatibility redirect.\n\nThink of `@smithy/core` as a mono-package within the monorepo.\nIt preserves the benefits of modularization, for example to optimize Node.js initialization speed,\nwhile making it easier to have a consistent version of core dependencies, reducing package sprawl when\ninstalling a Smithy runtime client.\n\n### Guide for submodules\n\n- Each `index.ts` file corresponding to the pattern `./src/submodules/<MODULE_NAME>/index.ts` will be\n  published as a separate `dist-cjs` bundled submodule index using the `Inliner.js` build script.\n- create a folder as `./src/submodules/<SUBMODULE>` including an `index.ts` file and a `README.md` file.\n  - The linter will throw an error on missing submodule metadata in `package.json` and the various `tsconfig.json` files, but it will automatically fix them if possible.\n- a submodule is equivalent to a standalone `@smithy/<pkg>` package in that importing it in Node.js will resolve a separate bundle.\n- submodules may not relatively import files from other submodules. Instead, directly use the `@scope/pkg/submodule` name as the import.\n  - The linter will check for this and throw an error.\n- To the extent possible, correctly declaring submodule metadata is validated by the linter in `@smithy/core`.\n  The linter runs during `yarn build` and also as `yarn lint`.\n\n### When should I create an `@smithy/core/submodule` vs. `@smithy/new-package`?\n\nKeep in mind that the core package is installed by all downstream clients.\n\nIf the component functionality is upstream of multiple clients, it is\na good candidate for a core submodule. For example, if `middleware-retry` had been written\nafter the support for submodules was added, it would have been a submodule.\n\nIf the component's functionality is downstream of a client (rare), or only expected to be used by a very small\nsubset of clients, it could be written as a standalone package.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{51/0f/7b7912a8d22beb575df89156801789d8c8ad483edcc206c87207687e92e514b70b2903961de62ee098e27b2a4d0440b5b1b5a2dbe5a3a08364fec744ea1e → 63/2a/267c2eee4d04cb7412fe874be429160b7e746d943f1a332329084d11681abc7c16855c054223397f959ede0703758ecf1e21088bb665aa9907875027aad0}

@@ -1961,7 +1961,7 @@
     "latest": "4.1.0",
     "next": "3.0.1"
   },
-  "_rev": "2078-30b90ecf8458fc52",
+  "_rev": "2083-2debf28b35a7bc01",
   "_id": "signal-exit",
   "readme": "# signal-exit\n\nWhen you want to fire an event no matter how a process exits:\n\n- reaching the end of execution.\n- explicitly having `process.exit(code)` called.\n- having `process.kill(pid, sig)` called.\n- receiving a fatal signal from outside the process\n\nUse `signal-exit`.\n\n```js\n// Hybrid module, either works\nimport { onExit } from 'signal-exit'\n// or:\n// const { onExit } = require('signal-exit')\n\nonExit((code, signal) => {\n  console.log('process exited!', code, signal)\n})\n```\n\n## API\n\n`remove = onExit((code, signal) => {}, options)`\n\nThe return value of the function is a function that will remove\nthe handler.\n\nNote that the function _only_ fires for signals if the signal\nwould cause the process to exit. That is, there are no other\nlisteners, and it is a fatal signal.\n\nIf the global `process` object is not suitable for this purpose\n(ie, it's unset, or doesn't have an `emit` method, etc.) then the\n`onExit` function is a no-op that returns a no-op `remove` method.\n\n### Options\n\n- `alwaysLast`: Run this handler after any other signal or exit\n  handlers. This causes `process.emit` to be monkeypatched.\n\n### Capturing Signal Exits\n\nIf the handler returns an exact boolean `true`, and the exit is a\ndue to signal, then the signal will be considered handled, and\nwill _not_ trigger a synthetic `process.kill(process.pid,\nsignal)` after firing the `onExit` handlers.\n\nIn this case, it your responsibility as the caller to exit with a\nsignal (for example, by calling `process.kill()`) if you wish to\npreserve the same exit status that would otherwise have occurred.\nIf you do not, then the process will likely exit gracefully with\nstatus 0 at some point, assuming that no other terminating signal\nor other exit trigger occurs.\n\nPrior to calling handlers, the `onExit` machinery is unloaded, so\nany subsequent exits or signals will not be handled, even if the\nsignal is captured and the exit is thus prevented.\n\nNote that numeric code exits may indicate that the process is\nalready committed to exiting, for example due to a fatal\nexception or unhandled promise rejection, and so there is no way to\nprevent it safely.\n\n### Browser Fallback\n\nThe `'signal-exit/browser'` module is the same fallback shim that\njust doesn't do anything, but presents the same function\ninterface.\n\nPatches welcome to add something that hooks onto\n`window.onbeforeunload` or similar, but it might just not be a\nthing that makes sense there.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{3c/7a/bf68eba13cbc668d5e2e5c0a4732f5b1d9015acdfecea3b8db01ef8e69c8cd9d94b504595e5702f7bd9a4b124a20be16455829b475d7a320da68a41129fe → 65/88/4cfe752e4e320e9642b639fe5fe5d4ec6428ac113bbfdad7e546e47f8cb91a14795c29893f1e3ccb05ad00162e8a508c627e8ffd7d2d87fd5a75f17c7dc3}

@@ -6561,7 +6561,7 @@
     "latest": "7.0.1",
     "canary": "0.15.0-1"
   },
-  "_rev": "252-1cbca83b3b0642b8",
+  "_rev": "256-119a0da3f44b028d",
   "_id": "archiver",
   "readme": "# Archiver\n\nA streaming interface for archive generation\n\nVisit the [API documentation](https://www.archiverjs.com/) for a list of all methods available.\n\n## Install\n\n```bash\nnpm install archiver --save\n```\n\n## Quick Start\n\n```js\n// require modules\nconst fs = require('fs');\nconst archiver = require('archiver');\n\n// create a file to stream archive data to.\nconst output = fs.createWriteStream(__dirname + '/example.zip');\nconst archive = archiver('zip', {\n  zlib: { level: 9 } // Sets the compression level.\n});\n\n// listen for all archive data to be written\n// 'close' event is fired only when a file descriptor is involved\noutput.on('close', function() {\n  console.log(archive.pointer() + ' total bytes');\n  console.log('archiver has been finalized and the output file descriptor has closed.');\n});\n\n// This event is fired when the data source is drained no matter what was the data source.\n// It is not part of this library but rather from the NodeJS Stream API.\n// @see: https://nodejs.org/api/stream.html#stream_event_end\noutput.on('end', function() {\n  console.log('Data has been drained');\n});\n\n// good practice to catch warnings (ie stat failures and other non-blocking errors)\narchive.on('warning', function(err) {\n  if (err.code === 'ENOENT') {\n    // log warning\n  } else {\n    // throw error\n    throw err;\n  }\n});\n\n// good practice to catch this error explicitly\narchive.on('error', function(err) {\n  throw err;\n});\n\n// pipe archive data to the file\narchive.pipe(output);\n\n// append a file from stream\nconst file1 = __dirname + '/file1.txt';\narchive.append(fs.createReadStream(file1), { name: 'file1.txt' });\n\n// append a file from string\narchive.append('string cheese!', { name: 'file2.txt' });\n\n// append a file from buffer\nconst buffer3 = Buffer.from('buff it!');\narchive.append(buffer3, { name: 'file3.txt' });\n\n// append a file\narchive.file('file1.txt', { name: 'file4.txt' });\n\n// append files from a sub-directory and naming it `new-subdir` within the archive\narchive.directory('subdir/', 'new-subdir');\n\n// append files from a sub-directory, putting its contents at the root of archive\narchive.directory('subdir/', false);\n\n// append files from a glob pattern\narchive.glob('file*.txt', {cwd:__dirname});\n\n// finalize the archive (ie we are done appending files but streams have to finish yet)\n// 'close', 'end' or 'finish' may be fired right after calling this method so register to them beforehand\narchive.finalize();\n```\n\n## Formats\n\nArchiver ships with out of the box support for TAR and ZIP archives.\n\nYou can register additional formats with `registerFormat`.\n\nYou can check if format already exists before to register a new one with `isRegisteredFormat`.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{5a/26/c18227e6b5fd78c54f79378100c5f47c2e0e9c5d2bd9f39044118f5f189a4da7b017d2ce251369c2a84d6c1822fde4cb0d04ee2866c573b342d06675daae → 65/e8/424b65f31640cb9e8bd88c725ad834f1b4b564ffcd1dc2857251dcdfb7654e9dbb6cb68d4534b599ab7071a0b12df6b9ed210ea20cb2df98158c9c4c9b8d}

@@ -7074,7 +7074,7 @@
   "dist-tags": {
     "latest": "4.2.9"
   },
-  "_rev": "178-6bf65905cdab7ff0",
+  "_rev": "182-9baf92c430bcbf75",
   "_id": "@smithy/hash-blob-browser",
   "readme": "# @smithy/sha256-blob-browser\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/hash-blob-browser/latest.svg)](https://www.npmjs.com/package/@smithy/hash-blob-browser)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/hash-blob-browser.svg)](https://www.npmjs.com/package/@smithy/hash-blob-browser)\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/e5/56d2518062d7befc86ba62887ab0ec46546a63b0044dc778ce1bc42bb77b18a524c0044fae8973b042ab91748366e0bd943795bf382a46ccb93e8784b25d → 6a/17/3de4aebf9c75466ac208ff77399e30658689356f66e329df6fede3a22a03e326b60106feea85fd2ec57d4e1f38d3fbd7cad94b9e1231ebaef14035ca3e1f}

@@ -5731,7 +5731,7 @@
   "dist-tags": {
     "latest": "4.2.8"
   },
-  "_rev": "175-892827d20fa56601",
+  "_rev": "179-b07c439a0d858245",
   "_id": "@smithy/url-parser",
   "readme": "# @smithy/url-parser\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/url-parser/latest.svg)](https://www.npmjs.com/package/@smithy/url-parser)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/url-parser.svg)](https://www.npmjs.com/package/@smithy/url-parser)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}