mrs-toolbox-cli 9.1.11 → 9.1.12

package/npm-cache/_cacache/content-v2/sha512/{ac/1f/07962c87faa8b298fe4f340875a1b07417ba8d3ab7a78398e80882002e9a6cb51be12657d23754f05af6bc63634fcbfbe5623c8ee8255fc3d767f79eaa16 → 6e/c9/ed356fa82d23e538355032d418e43ccbb43aed847fa29981a9a71d39f647637c50bc497f0656e6b27ed2234bee467a9c291aecdb2eea0ec288fe592aaae9}

@@ -5943,7 +5943,7 @@
   "dist-tags": {
     "latest": "4.2.10"
   },
-  "_rev": "218-a89c2f9fb050572f",
+  "_rev": "229-7129d48f6718d8f1",
   "_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": {}

package/npm-cache/_cacache/content-v2/sha512/{6c/19/79dc95a694d2e243069bca4a7ed9ad2531c26c07a6cdfa8912bf7f2cbb263e769d554d399dfc3e1c40bf760128c326b847bb61c19955eda5e450a0ebe46c → 6f/91/6f997df860e7ca851be0d454ea4cd1a9c03126e80babcaf8533110ff21132871e56052fd338e99f751c203be62e5a1c91c9a5d8a1ad058d28c6eeadd731c}

@@ -270,7 +270,7 @@
   "dist-tags": {
     "latest": "0.3.0"
   },
-  "_rev": "649-d1f25ea5ffdecf9b",
+  "_rev": "671-eaba8532279dbf24",
   "_id": "eastasianwidth",
   "readme": "# East Asian Width\n\nGet [East Asian Width](http://www.unicode.org/reports/tr11/) from a character.\n\n'F'(Fullwidth), 'H'(Halfwidth), 'W'(Wide), 'Na'(Narrow), 'A'(Ambiguous) or 'N'(Natural).\n\nOriginal Code is [東アジアの文字幅 (East Asian Width) の判定 - 中途](http://d.hatena.ne.jp/takenspc/20111126#1322252878).\n\n## Install\n\n    $ npm install eastasianwidth\n\n## Usage\n\n    var eaw = require('eastasianwidth');\n    console.log(eaw.eastAsianWidth('￦')) // 'F'\n    console.log(eaw.eastAsianWidth('｡')) // 'H'\n    console.log(eaw.eastAsianWidth('뀀')) // 'W'\n    console.log(eaw.eastAsianWidth('a')) // 'Na'\n    console.log(eaw.eastAsianWidth('①')) // 'A'\n    console.log(eaw.eastAsianWidth('ف')) // 'N'\n\n    console.log(eaw.characterLength('￦')) // 2\n    console.log(eaw.characterLength('｡')) // 1\n    console.log(eaw.characterLength('뀀')) // 2\n    console.log(eaw.characterLength('a')) // 1\n    console.log(eaw.characterLength('①')) // 2\n    console.log(eaw.characterLength('ف')) // 1\n\n    console.log(eaw.length('あいうえお')) // 10\n    console.log(eaw.length('abcdefg')) // 7\n    console.log(eaw.length('￠￦｡ￜㄅ뀀¢⟭a⊙①بف')) // 19",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{59/e4/6f700ec7f383ecc9e370b49bde79560acfa103b9618cf40ccf519b4179711a7e3572233b2f3c692d43d299c66594768688207e736e632f5ec76d4fcccfe6 → 70/27/267d463cf70c3da0cad68c3e7b6bf799f453ac2c8fad71ded5085599ed0db9b730e541a640d9c3c4f168bd1ede8a1e41a32dd9be0adad7070e2c73b4dee6}

@@ -7888,7 +7888,7 @@
     "latest": "6.1.3",
     "v5-legacy": "5.0.10"
   },
-  "_rev": "4022-8c64223d573a54c3",
+  "_rev": "4068-8567c56cc31b3571",
   "_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> [!CAUTION]\n>\n> ## Please Be Safe, this tool deletes and moves stuff, by design\n>\n> The _intended purpose_ of this tool is to remove files and\n> directories from the filesystem, aggressively and recursively\n> removing all items that it can find under a given target.\n>\n> It goes without saying that you _must not pass untrusted input\n> to this function or CLI tool_, just as you would not to the\n> `rm(1)` command or the `unlink(2)` function. It is very\n> challenging to guarantee that _any_ user input will be safe to\n> remove recursively in this way.\n>\n> Furthermore, note that if you allow untrusted parties to\n> provide arguments to the `rimraf` command line tool, they may\n> also specify the `--tmp=<dir>` folder used by the\n> `--impl=move-remove` strategy, which can move files to an\n> arbitrary place on disk.\n>\n> Because the intended purpose of this tool is the permanent\n> destruction of filesystem entries, any security reports that\n> rely on untrusted input being passed to the function or command\n> line tool will be rejected.\n>\n> **It is your responsibility as a user to never pass untrusted\n> user input to this module, or your system can be destroyed or\n> compromised.**\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/{ad/2e/a7d905511fa20b379b675746d8f6b65192a1713eef26fc45c528a10945ee7d2cdf1a0007ff5dcc9915969d665d5cb8991d5cf3b8df4681dc766bacb49270 → 76/b7/d1654a2b305cd2ab791401b328877388fc60e6a44ffafd01300af0d5b3397882de7c243796be3bf63378327a2cb0f762e2901437cbf3b39d5a81c62832ff}

@@ -2419,7 +2419,7 @@
   "dist-tags": {
     "latest": "6.2.3"
   },
-  "_rev": "4822-8086d5018ba6b84b",
+  "_rev": "4868-15d39367a5aa65b3",
   "_id": "ansi-styles",
   "readme": "",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{37/d6/e13e20a479f0105bfebc0ee4c46f3be1f508645ff63b94e1a069735368c292db2f6f1cd3e992462a704969478069c9b812afc0dcc3877a2e9d9b86d6bbdc → 77/c1/b5e98ef0b012f0fc827f34a024c1eb76d2fc4a34af2bb0d33eb0cec412f701504906effae56876b276543fc7e1c57ab35ab26ccf33bdfce01daec12bd698}

@@ -3753,7 +3753,7 @@
   "dist-tags": {
     "latest": "2.0.2"
   },
-  "_rev": "1109-6399930b2c9e910d",
+  "_rev": "1137-d8db9b100798ab92",
   "_id": "path-scurry",
   "readme": "# path-scurry\n\nExtremely high performant utility for building tools that read\nthe file system, minimizing filesystem and path string munging\noperations to the greatest degree possible.\n\n## Ugh, yet another file traversal thing on npm?\n\nYes. None of the existing ones gave me exactly what I wanted.\n\n## Well what is it you wanted?\n\nWhile working on [glob](http://npm.im/glob), I found that I\nneeded a module to very efficiently manage the traversal over a\nfolder tree, such that:\n\n1. No `readdir()` or `stat()` would ever be called on the same\n   file or directory more than one time.\n2. No `readdir()` calls would be made if we can be reasonably\n   sure that the path is not a directory. (Ie, a previous\n   `readdir()` or `stat()` covered the path, and\n   `ent.isDirectory()` is false.)\n3. `path.resolve()`, `dirname()`, `basename()`, and other\n   string-parsing/munging operations are be minimized. This means\n   it has to track \"provisional\" child nodes that may not exist\n   (and if we find that they _don't_ exist, store that\n   information as well, so we don't have to ever check again).\n4. The API is not limited to use as a stream/iterator/etc. There\n   are many cases where an API like node's `fs` is preferrable.\n5. It's more important to prevent excess syscalls than to be up\n   to date, but it should be smart enough to know what it\n   _doesn't_ know, and go get it seamlessly when requested.\n6. Do not blow up the JS heap allocation if operating on a\n   directory with a huge number of entries.\n7. Handle all the weird aspects of Windows paths, like UNC paths\n   and drive letters and wrongway slashes, so that the consumer\n   can return canonical platform-specific paths without having to\n   parse or join or do any error-prone string munging.\n\n## PERFORMANCE\n\nJavaScript people throw around the word \"blazing\" a lot. I hope\nthat this module doesn't blaze anyone. But it does go very fast,\nin the cases it's optimized for, if used properly.\n\nPathScurry provides ample opportunities to get extremely good\nperformance, as well as several options to trade performance for\nconvenience.\n\nBenchmarks can be run by executing `npm run bench`.\n\nAs is always the case, doing more means going slower, doing less\nmeans going faster, and there are trade offs between speed and\nmemory usage.\n\nPathScurry makes heavy use of [LRUCache](http://npm.im/lru-cache)\nto efficiently cache whatever it can, and `Path` objects remain\nin the graph for the lifetime of the walker, so repeated calls\nwith a single PathScurry object will be extremely fast. However,\nadding items to a cold cache means \"doing more\", so in those\ncases, we pay a price. Nothing is free, but every effort has been\nmade to reduce costs wherever possible.\n\nAlso, note that a \"cache as long as possible\" approach means that\nchanges to the filesystem may not be reflected in the results of\nrepeated PathScurry operations.\n\nFor resolving string paths, `PathScurry` ranges from 5-50 times\nfaster than `path.resolve` on repeated resolutions, but around\n100 to 1000 times _slower_ on the first resolution. If your\nprogram is spending a lot of time resolving the _same_ paths\nrepeatedly (like, thousands or millions of times), then this can\nbe beneficial. But both implementations are pretty fast, and\nspeeding up an infrequent operation from 4µs to 400ns is not\ngoing to move the needle on your app's performance.\n\nFor walking file system directory trees, a lot depends on how\noften a given PathScurry object will be used, and also on the\nwalk method used.\n\nWith default settings on a folder tree of 100,000 items,\nconsisting of around a 10-to-1 ratio of normal files to\ndirectories, PathScurry performs comparably to\n[@nodelib/fs.walk](http://npm.im/@nodelib/fs.walk), which is the\nfastest and most reliable file system walker I could find. As far\nas I can tell, it's almost impossible to go much faster in a\nNode.js program, just based on how fast you can push syscalls out\nto the fs thread pool.\n\nOn my machine, that is about 1000-1200 completed walks per second\nfor async or stream walks, and around 500-600 walks per second\nsynchronously.\n\nIn the warm cache state, PathScurry's performance increases\naround 4x for async `for await` iteration, 10-15x faster for\nstreams and synchronous `for of` iteration, and anywhere from 30x\nto 80x faster for the rest.\n\n```\n# walk 100,000 fs entries, 10/1 file/dir ratio\n# operations / ms\n New PathScurry object  |  Reuse PathScurry object\n     stream:  1112.589  |  13974.917\nsync stream:   492.718  |  15028.343\n async walk:  1095.648  |  32706.395\n  sync walk:   527.632  |  46129.772\n async iter:  1288.821  |   5045.510\n  sync iter:   498.496  |  17920.746\n```\n\nA hand-rolled walk calling `entry.readdir()` and recursing\nthrough the entries can benefit even more from caching, with\ngreater flexibility and without the overhead of streams or\ngenerators.\n\nThe cold cache state is still limited by the costs of file system\noperations, but with a warm cache, the only bottleneck is CPU\nspeed and VM optimizations. Of course, in that case, some care\nmust be taken to ensure that you don't lose performance as a\nresult of silly mistakes, like calling `readdir()` on entries\nthat you know are not directories.\n\n```\n# manual recursive iteration functions\n      cold cache  |  warm cache\nasync:  1164.901  |  17923.320\n   cb:  1101.127  |  40999.344\nzalgo:  1082.240  |  66689.936\n sync:   526.935  |  87097.591\n```\n\nIn this case, the speed improves by around 10-20x in the async\ncase, 40x in the case of using `entry.readdirCB` with protections\nagainst synchronous callbacks, and 50-100x with callback\ndeferrals disabled, and _several hundred times faster_ for\nsynchronous iteration.\n\nIf you can think of a case that is not covered in these\nbenchmarks, or an implementation that performs significantly\nbetter than PathScurry, please [let me\nknow](https://github.com/isaacs/path-scurry/issues).\n\n## USAGE\n\n```ts\n// hybrid module, load with either method\nimport { PathScurry, Path } from 'path-scurry'\n// or:\nconst { PathScurry, Path } = require('path-scurry')\n\n// very simple example, say we want to find and\n// delete all the .DS_Store files in a given path\n// note that the API is very similar to just a\n// naive walk with fs.readdir()\nimport { unlink } from 'fs/promises'\n\n// easy way, iterate over the directory and do the thing\nconst pw = new PathScurry(process.cwd())\nfor await (const entry of pw) {\n  if (entry.isFile() && entry.name === '.DS_Store') {\n    unlink(entry.fullpath())\n  }\n}\n\n// here it is as a manual recursive method\nconst walk = async (entry: Path) => {\n  const promises: Promise<any> = []\n  // readdir doesn't throw on non-directories, it just doesn't\n  // return any entries, to save stack trace costs.\n  // Items are returned in arbitrary unsorted order\n  for (const child of await pw.readdir(entry)) {\n    // each child is a Path object\n    if (child.name === '.DS_Store' && child.isFile()) {\n      // could also do pw.resolve(entry, child.name),\n      // just like fs.readdir walking, but .fullpath is\n      // a *slightly* more efficient shorthand.\n      promises.push(unlink(child.fullpath()))\n    } else if (child.isDirectory()) {\n      promises.push(walk(child))\n    }\n  }\n  return Promise.all(promises)\n}\n\nwalk(pw.cwd).then(() => {\n  console.log('all .DS_Store files removed')\n})\n\nconst pw2 = new PathScurry('/a/b/c') // pw2.cwd is the Path for /a/b/c\nconst relativeDir = pw2.cwd.resolve('../x') // Path entry for '/a/b/x'\nconst relative2 = pw2.cwd.resolve('/a/b/d/../x') // same path, same entry\nassert.equal(relativeDir, relative2)\n```\n\n## API\n\n[Full TypeDoc API](https://isaacs.github.io/path-scurry)\n\nThere are platform-specific classes exported, but for the most\npart, the default `PathScurry` and `Path` exports are what you\nmost likely need, unless you are testing behavior for other\nplatforms.\n\nIntended public API is documented here, but the full\ndocumentation does include internal types, which should not be\naccessed directly.\n\n### Interface `PathScurryOpts`\n\nThe type of the `options` argument passed to the `PathScurry`\nconstructor.\n\n- `nocase`: Boolean indicating that file names should be compared\n  case-insensitively. Defaults to `true` on darwin and win32\n  implementations, `false` elsewhere.\n\n  **Warning** Performing case-insensitive matching on a\n  case-sensitive filesystem will result in occasionally very\n  bizarre behavior. Performing case-sensitive matching on a\n  case-insensitive filesystem may negatively impact performance.\n\n- `childrenCacheSize`: Number of child entries to cache, in order\n  to speed up `resolve()` and `readdir()` calls. Defaults to\n  `16 * 1024` (ie, `16384`).\n\n  Setting it to a higher value will run the risk of JS heap\n  allocation errors on large directory trees. Setting it to `256`\n  or smaller will significantly reduce the construction time and\n  data consumption overhead, but with the downside of operations\n  being slower on large directory trees. Setting it to `0` will\n  mean that effectively no operations are cached, and this module\n  will be roughly the same speed as `fs` for file system\n  operations, and _much_ slower than `path.resolve()` for\n  repeated path resolution.\n\n- `fs` An object that will be used to override the default `fs`\n  methods. Any methods that are not overridden will use Node's\n  built-in implementations.\n\n  - lstatSync\n  - readdir (callback `withFileTypes` Dirent variant, used for\n    readdirCB and most walks)\n  - readdirSync\n  - readlinkSync\n  - realpathSync\n  - promises: Object containing the following async methods:\n    - lstat\n    - readdir (Dirent variant only)\n    - readlink\n    - realpath\n\n### Interface `WalkOptions`\n\nThe options object that may be passed to all walk methods.\n\n- `withFileTypes`: Boolean, default true. Indicates that `Path`\n  objects should be returned. Set to `false` to get string paths\n  instead.\n- `follow`: Boolean, default false. Attempt to read directory\n  entries from symbolic links. Otherwise, only actual directories\n  are traversed. Regardless of this setting, a given target path\n  will only ever be walked once, meaning that a symbolic link to\n  a previously traversed directory will never be followed.\n\n  Setting this imposes a slight performance penalty, because\n  `readlink` must be called on all symbolic links encountered, in\n  order to avoid infinite cycles.\n\n- `filter`: Function `(entry: Path) => boolean`. If provided,\n  will prevent the inclusion of any entry for which it returns a\n  falsey value. This will not prevent directories from being\n  traversed if they do not pass the filter, though it will\n  prevent the directories themselves from being included in the\n  results. By default, if no filter is provided, then all entries\n  are included in the results.\n- `walkFilter`: Function `(entry: Path) => boolean`. If provided,\n  will prevent the traversal of any directory (or in the case of\n  `follow:true` symbolic links to directories) for which the\n  function returns false. This will not prevent the directories\n  themselves from being included in the result set. Use `filter`\n  for that.\n\nNote that TypeScript return types will only be inferred properly\nfrom static analysis if the `withFileTypes` option is omitted, or\na constant `true` or `false` value.\n\n### Class `PathScurry`\n\nThe main interface. Defaults to an appropriate class based on the\ncurrent platform.\n\nUse `PathScurryWin32`, `PathScurryDarwin`, or `PathScurryPosix`\nif implementation-specific behavior is desired.\n\nAll walk methods may be called with a `WalkOptions` argument to\nwalk over the object's current working directory with the\nsupplied options.\n\n#### `async pw.walk(entry?: string | Path | WalkOptions, opts?: WalkOptions)`\n\nWalk the directory tree according to the options provided,\nresolving to an array of all entries found.\n\n#### `pw.walkSync(entry?: string | Path | WalkOptions, opts?: WalkOptions)`\n\nWalk the directory tree according to the options provided,\nreturning an array of all entries found.\n\n#### `pw.iterate(entry?: string | Path | WalkOptions, opts?: WalkOptions)`\n\nIterate over the directory asynchronously, for use with `for\nawait of`. This is also the default async iterator method.\n\n#### `pw.iterateSync(entry?: string | Path | WalkOptions, opts?: WalkOptions)`\n\nIterate over the directory synchronously, for use with `for of`.\nThis is also the default sync iterator method.\n\n#### `pw.stream(entry?: string | Path | WalkOptions, opts?: WalkOptions)`\n\nReturn a [Minipass](http://npm.im/minipass) stream that emits\neach entry or path string in the walk. Results are made available\nasynchronously.\n\n#### `pw.streamSync(entry?: string | Path | WalkOptions, opts?: WalkOptions)`\n\nReturn a [Minipass](http://npm.im/minipass) stream that emits\neach entry or path string in the walk. Results are made available\nsynchronously, meaning that the walk will complete in a single\ntick if the stream is fully consumed.\n\n#### `pw.cwd`\n\nPath object representing the current working directory for the\nPathScurry.\n\n#### `pw.chdir(path: string)`\n\nSet the new effective current working directory for the scurry\nobject, so that `path.relative()` and `path.relativePosix()`\nreturn values relative to the new cwd path.\n\n#### `pw.depth(path?: Path | string): number`\n\nReturn the depth of the specified path (or the PathScurry cwd)\nwithin the directory tree.\n\nRoot entries have a depth of `0`.\n\n#### `pw.resolve(...paths: string[])`\n\nCaching `path.resolve()`.\n\nSignificantly faster than `path.resolve()` if called repeatedly\nwith the same paths. Significantly slower otherwise, as it builds\nout the cached Path entries.\n\nTo get a `Path` object resolved from the `PathScurry`, use\n`pw.cwd.resolve(path)`. Note that `Path.resolve` only takes a\nsingle string argument, not multiple.\n\n#### `pw.resolvePosix(...paths: string[])`\n\nCaching `path.resolve()`, but always using posix style paths.\n\nThis is identical to `pw.resolve(...paths)` on posix systems (ie,\neverywhere except Windows).\n\nOn Windows, it returns the full absolute UNC path using `/`\nseparators. Ie, instead of `'C:\\\\foo\\\\bar`, it would return\n`//?/C:/foo/bar`.\n\n#### `pw.relative(path: string | Path): string`\n\nReturn the relative path from the PathWalker cwd to the supplied\npath string or entry.\n\nIf the nearest common ancestor is the root, then an absolute path\nis returned.\n\n#### `pw.relativePosix(path: string | Path): string`\n\nReturn the relative path from the PathWalker cwd to the supplied\npath string or entry, using `/` path separators.\n\nIf the nearest common ancestor is the root, then an absolute path\nis returned.\n\nOn posix platforms (ie, all platforms except Windows), this is\nidentical to `pw.relative(path)`.\n\nOn Windows systems, it returns the resulting string as a\n`/`-delimited path. If an absolute path is returned (because the\ntarget does not share a common ancestor with `pw.cwd`), then a\nfull absolute UNC path will be returned. Ie, instead of\n`'C:\\\\foo\\\\bar`, it would return `//?/C:/foo/bar`.\n\n#### `pw.basename(path: string | Path): string`\n\nReturn the basename of the provided string or Path.\n\n#### `pw.dirname(path: string | Path): string`\n\nReturn the parent directory of the supplied string or Path.\n\n#### `async pw.readdir(dir = pw.cwd, opts = { withFileTypes: true })`\n\nRead the directory and resolve to an array of strings if\n`withFileTypes` is explicitly set to `false` or Path objects\notherwise.\n\nCan be called as `pw.readdir({ withFileTypes: boolean })` as\nwell.\n\nReturns `[]` if no entries are found, or if any error occurs.\n\nNote that TypeScript return types will only be inferred properly\nfrom static analysis if the `withFileTypes` option is omitted, or\na constant `true` or `false` value.\n\n#### `pw.readdirSync(dir = pw.cwd, opts = { withFileTypes: true })`\n\nSynchronous `pw.readdir()`\n\n#### `async pw.readlink(link = pw.cwd, opts = { withFileTypes: false })`\n\nCall `fs.readlink` on the supplied string or Path object, and\nreturn the result.\n\nCan be called as `pw.readlink({ withFileTypes: boolean })` as\nwell.\n\nReturns `undefined` if any error occurs (for example, if the\nargument is not a symbolic link), or a `Path` object if\n`withFileTypes` is explicitly set to `true`, or a string\notherwise.\n\nNote that TypeScript return types will only be inferred properly\nfrom static analysis if the `withFileTypes` option is omitted, or\na constant `true` or `false` value.\n\n#### `pw.readlinkSync(link = pw.cwd, opts = { withFileTypes: false })`\n\nSynchronous `pw.readlink()`\n\n#### `async pw.lstat(entry = pw.cwd)`\n\nCall `fs.lstat` on the supplied string or Path object, and fill\nin as much information as possible, returning the updated `Path`\nobject.\n\nReturns `undefined` if the entry does not exist, or if any error\nis encountered.\n\nNote that some `Stats` data (such as `ino`, `dev`, and `mode`)\nwill not be supplied. For those things, you'll need to call\n`fs.lstat` yourself.\n\n#### `pw.lstatSync(entry = pw.cwd)`\n\nSynchronous `pw.lstat()`\n\n#### `pw.realpath(entry = pw.cwd, opts = { withFileTypes: false })`\n\nCall `fs.realpath` on the supplied string or Path object, and\nreturn the realpath if available.\n\nReturns `undefined` if any error occurs.\n\nMay be called as `pw.realpath({ withFileTypes: boolean })` to run\non `pw.cwd`.\n\n#### `pw.realpathSync(entry = pw.cwd, opts = { withFileTypes: false })`\n\nSynchronous `pw.realpath()`\n\n### Class `Path` implements [fs.Dirent](https://nodejs.org/docs/latest/api/fs.html#class-fsdirent)\n\nObject representing a given path on the filesystem, which may or\nmay not exist.\n\nNote that the actual class in use will be either `PathWin32` or\n`PathPosix`, depending on the implementation of `PathScurry` in\nuse. They differ in the separators used to split and join path\nstrings, and the handling of root paths.\n\nIn `PathPosix` implementations, paths are split and joined using\nthe `'/'` character, and `'/'` is the only root path ever in use.\n\nIn `PathWin32` implementations, paths are split using either\n`'/'` or `'\\\\'` and joined using `'\\\\'`, and multiple roots may\nbe in use based on the drives and UNC paths encountered. UNC\npaths such as `//?/C:/` that identify a drive letter, will be\ntreated as an alias for the same root entry as their associated\ndrive letter (in this case `'C:\\\\'`).\n\n#### `path.name`\n\nName of this file system entry.\n\n**Important**: _always_ test the path name against any test\nstring using the `isNamed` method, and not by directly comparing\nthis string. Otherwise, unicode path strings that the system sees\nas identical will not be properly treated as the same path,\nleading to incorrect behavior and possible security issues.\n\n#### `path.isNamed(name: string): boolean`\n\nReturn true if the path is a match for the given path name. This\nhandles case sensitivity and unicode normalization.\n\nNote: even on case-sensitive systems, it is **not** safe to test\nthe equality of the `.name` property to determine whether a given\npathname matches, due to unicode normalization mismatches.\n\nAlways use this method instead of testing the `path.name`\nproperty directly.\n\n#### `path.isCWD`\n\nSet to true if this `Path` object is the current working\ndirectory of the `PathScurry` collection that contains it.\n\n#### `path.getType()`\n\nReturns the type of the Path object, `'File'`, `'Directory'`,\netc.\n\n#### `path.isType(t: type)`\n\nReturns true if `is{t}()` returns true.\n\nFor example, `path.isType('Directory')` is equivalent to\n`path.isDirectory()`.\n\n#### `path.depth()`\n\nReturn the depth of the Path entry within the directory tree.\nRoot paths have a depth of `0`.\n\n#### `path.fullpath()`\n\nThe fully resolved path to the entry.\n\n#### `path.fullpathPosix()`\n\nThe fully resolved path to the entry, using `/` separators.\n\nOn posix systems, this is identical to `path.fullpath()`. On\nwindows, this will return a fully resolved absolute UNC path\nusing `/` separators. Eg, instead of `'C:\\\\foo\\\\bar'`, it will\nreturn `'//?/C:/foo/bar'`.\n\n#### `path.isFile()`, `path.isDirectory()`, etc.\n\nSame as the identical `fs.Dirent.isX()` methods.\n\n#### `path.isUnknown()`\n\nReturns true if the path's type is unknown. Always returns true\nwhen the path is known to not exist.\n\n#### `path.resolve(p: string)`\n\nReturn a `Path` object associated with the provided path string\nas resolved from the current Path object.\n\n#### `path.relative(): string`\n\nReturn the relative path from the PathWalker cwd to the supplied\npath string or entry.\n\nIf the nearest common ancestor is the root, then an absolute path\nis returned.\n\n#### `path.relativePosix(): string`\n\nReturn the relative path from the PathWalker cwd to the supplied\npath string or entry, using `/` path separators.\n\nIf the nearest common ancestor is the root, then an absolute path\nis returned.\n\nOn posix platforms (ie, all platforms except Windows), this is\nidentical to `pw.relative(path)`.\n\nOn Windows systems, it returns the resulting string as a\n`/`-delimited path. If an absolute path is returned (because the\ntarget does not share a common ancestor with `pw.cwd`), then a\nfull absolute UNC path will be returned. Ie, instead of\n`'C:\\\\foo\\\\bar`, it would return `//?/C:/foo/bar`.\n\n#### `async path.readdir()`\n\nReturn an array of `Path` objects found by reading the associated\npath entry.\n\nIf path is not a directory, or if any error occurs, returns `[]`,\nand marks all children as provisional and non-existent.\n\n#### `path.readdirSync()`\n\nSynchronous `path.readdir()`\n\n#### `async path.readlink()`\n\nReturn the `Path` object referenced by the `path` as a symbolic\nlink.\n\nIf the `path` is not a symbolic link, or any error occurs,\nreturns `undefined`.\n\n#### `path.readlinkSync()`\n\nSynchronous `path.readlink()`\n\n#### `async path.lstat()`\n\nCall `lstat` on the path object, and fill it in with details\ndetermined.\n\nIf path does not exist, or any other error occurs, returns\n`undefined`, and marks the path as \"unknown\" type.\n\n#### `path.lstatSync()`\n\nSynchronous `path.lstat()`\n\n#### `async path.realpath()`\n\nCall `realpath` on the path, and return a Path object\ncorresponding to the result, or `undefined` if any error occurs.\n\n#### `path.realpathSync()`\n\nSynchornous `path.realpath()`",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{06/0b/160991cae6b56a37ad820e72bae418dcf5a688e2cdb61fd884ee545ed4b82b12fe5453363f1e6f2176e85387ff16b5ffe4dd02763ad488aef6c9493ac667 → 78/5f/69713ca595ddf9bb9e89dfc7daeee080d3b2320bf9b12d858c2cd2f55f37dfc21fbcc80f7e4969f9fca67c2975233851f5bcf71142344fab2e7edd014131}

@@ -1331,7 +1331,7 @@
   "dist-tags": {
     "latest": "4.0.0"
   },
-  "_rev": "3465-133daa84a08aecdd",
+  "_rev": "3511-58a61f6ff13f4764",
   "_id": "isexe",
   "readme": "# isexe\n\nMinimal module to check if a file is executable, and a normal file.\n\nUses `fs.stat` and tests against the `PATHEXT` environment variable on\nWindows.\n\n## USAGE\n\n```js\n// default export is a minified version that doesn't need to\n// load more than one file. Load the 'isexe/raw' export if\n// you want the non-minified version for some reason.\nimport { isexe, sync } from 'isexe'\n// or require() works too\n// const { isexe } = require('isexe')\nisexe('some-file-name').then(\n  isExe => {\n    if (isExe) {\n      console.error('this thing can be run')\n    } else {\n      console.error('cannot be run')\n    }\n  },\n  err => {\n    console.error('probably file doesnt exist or something')\n  },\n)\n\n// same thing but synchronous, throws errors\nisExe = sync('some-file-name')\n\n// treat errors as just \"not executable\"\nconst isExe = await isexe('maybe-missing-file', { ignoreErrors: true })\nconst isExe = sync('maybe-missing-file', { ignoreErrors: true })\n```\n\n## API\n\n### `isexe(path, [options]) => Promise<boolean>`\n\nCheck if the path is executable.\n\nWill raise whatever errors may be raised by `fs.stat`, unless\n`options.ignoreErrors` is set to true.\n\n### `sync(path, [options]) => boolean`\n\nSame as `isexe` but returns the value and throws any errors raised.\n\n## Platform Specific Implementations\n\nIf for some reason you want to use the implementation for a\nspecific platform, you can do that.\n\n```js\nimport { win32, posix } from 'isexe'\nwin32.isexe(...)\nwin32.sync(...)\n// etc\n\n// or:\nimport { isexe, sync } from 'isexe/posix'\n```\n\nThe default exported implementation will be chosen based on\n`process.platform`.\n\n### Options\n\n```ts\nimport type IsexeOptions from 'isexe'\n```\n\n- `ignoreErrors` Treat all errors as \"no, this is not\n  executable\", but don't raise them.\n- `uid` Number to use as the user id on posix\n- `gid` Number to use as the group id on posix\n- `pathExt` List of path extensions to use instead of `PATHEXT`\n  environment variable on Windows.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{52/c2/3f64cd87b7af7d82f93bfd146a5723541f7e86f9aa2e9931e158f43110cebca7795646074c07a4956e4cf1ae90285801a355eac364a614a22ac9366eb0f8 → 7a/4f/5beca427ad94abebec737a4d699f517557640c0728f2d2a9eb51cd60fa920d7717cf2f533955f777d579a298c447e918fb519beb5948cc5cf75c18d31bf0}

@@ -17433,7 +17433,7 @@
   "dist-tags": {
     "latest": "4.2.39"
   },
-  "_rev": "244-d59938c271eef511",
+  "_rev": "255-618db3f917ff4c42",
   "_id": "@smithy/util-defaults-mode-node",
   "readme": "# @smithy/util-defaults-mode-node\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/util-defaults-mode-node/latest.svg)](https://www.npmjs.com/package/@smithy/util-defaults-mode-node)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/util-defaults-mode-node.svg)](https://www.npmjs.com/package/@smithy/util-defaults-mode-node)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{40/07/e0a81218a12ab5335b754798e05ab46eb61b2f1e740d749656c0a45507132b5db44690de6d85de48711a65752ae7621bac0bd7e69b1c690259f462812818 → 7b/04/5a41ae26dc6406b3e2116210b8faf9ffe0a0ab69cc731f0d7628186e91c9260bb8168c0dcb6b891a26d6f24d5c28d2f4bf6c051bb48c6fdea2b0360f4a03}

@@ -872,7 +872,7 @@
   "dist-tags": {
     "latest": "1.2.7"
   },
-  "_rev": "704-f794ec34a946a680",
+  "_rev": "720-fc1c46c56be7877a",
   "_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/{56/08/777d143f51080bd7ad988af78392159a08894261d96a48da7b8a20646f2b8345d6e77a8fbc53b326ce89e27e80827608c6648f80b7dd50465a51ba9d9d38 → 7d/eb/3d876a8fe8218a6da1e9e5759603ff18e12156ae8a6612bfc54c754c99c90524da349ae7e16db17f6878f3c2f1d28b1251ed14349e1c067bdfd92116dd77}

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

package/npm-cache/_cacache/content-v2/sha512/{40/5d/53fb67a168afd7335ea8689d0e6654058380d9d5163f7b7ccb6afd1cd7010688aeb05df9a9d68167b340caf2029fc6f80592a079c0023a271557c3ff8985 → 7e/79/ee9ed38678614247430b44afe909244e4f8abb6da78b71eefde30b2cb7a2493d1c0a7e217183b6b88ac32e9c50a354f13d9297da01256416c60797e8e85d}

@@ -9483,7 +9483,7 @@
     "legacy=2": "2.3.8",
     "legacy-3": "3.6.2"
   },
-  "_rev": "2518-2d937a608ab511d0",
+  "_rev": "2535-2b15024056391639",
   "_id": "readable-stream",
   "readme": "# readable-stream\n\n**_Node.js core streams for userland_**\n\n[![npm status](https://img.shields.io/npm/v/readable-stream.svg)](https://npm.im/readable-stream)\n[![node](https://img.shields.io/node/v/readable-stream.svg)](https://www.npmjs.org/package/readable-stream)\n[![Node.js Build](https://github.com/nodejs/readable-stream/workflows/Node.js/badge.svg)](https://github.com/nodejs/readable-stream/actions?query=workflow%3ANode.js)\n[![Browsers Build](https://github.com/nodejs/readable-stream/workflows/Browsers/badge.svg)](https://github.com/nodejs/readable-stream/actions?query=workflow%3ABrowsers)\n\n```bash\nnpm install readable-stream\n```\n\nThis package is a mirror of the streams implementations in Node.js 18.19.0.\n\nFull documentation may be found on the [Node.js website](https://nodejs.org/dist/v18.19.0/docs/api/stream.html).\n\nIf you want to guarantee a stable streams base, regardless of what version of\nNode you, or the users of your libraries are using, use **readable-stream** _only_ and avoid the _\"stream\"_ module in Node-core, for background see [this blogpost](http://r.va.gg/2014/06/why-i-dont-use-nodes-core-stream-module.html).\n\nAs of version 2.0.0 **readable-stream** uses semantic versioning.\n\n## Version 4.x.x\n\nv4.x.x of `readable-stream` is a cut from Node 18. This version supports Node 12, 14, 16 and 18, as well as evergreen browsers.\nThe breaking changes introduced by v4 are composed of the combined breaking changes in:\n* [Node v12](https://nodejs.org/en/blog/release/v12.0.0/)\n* [Node v13](https://nodejs.org/en/blog/release/v13.0.0/)\n* [Node v14](https://nodejs.org/en/blog/release/v14.0.0/)\n* [Node v15](https://nodejs.org/en/blog/release/v15.0.0/)\n* [Node v16](https://nodejs.org/en/blog/release/v16.0.0/)\n* [Node v17](https://nodejs.org/en/blog/release/v17.0.0/)\n* [Node v18](https://nodejs.org/en/blog/release/v18.0.0/)\n\nThis also includes _many_ new features.\n\n## Version 3.x.x\n\nv3.x.x of `readable-stream` is a cut from Node 10. This version supports Node 6, 8, and 10, as well as evergreen browsers, IE 11 and latest Safari. The breaking changes introduced by v3 are composed by the combined breaking changes in [Node v9](https://nodejs.org/en/blog/release/v9.0.0/) and [Node v10](https://nodejs.org/en/blog/release/v10.0.0/), as follows:\n\n1. Error codes: https://github.com/nodejs/node/pull/13310,\n   https://github.com/nodejs/node/pull/13291,\n   https://github.com/nodejs/node/pull/16589,\n   https://github.com/nodejs/node/pull/15042,\n   https://github.com/nodejs/node/pull/15665,\n   https://github.com/nodejs/readable-stream/pull/344\n2. 'readable' have precedence over flowing\n   https://github.com/nodejs/node/pull/18994\n3. make virtual methods errors consistent\n   https://github.com/nodejs/node/pull/18813\n4. updated streams error handling\n   https://github.com/nodejs/node/pull/18438\n5. writable.end should return this.\n   https://github.com/nodejs/node/pull/18780\n6. readable continues to read when push('')\n   https://github.com/nodejs/node/pull/18211\n7. add custom inspect to BufferList\n   https://github.com/nodejs/node/pull/17907\n8. always defer 'readable' with nextTick\n   https://github.com/nodejs/node/pull/17979\n\n## Version 2.x.x\n\nv2.x.x of `readable-stream` is a cut of the stream module from Node 8 (there have been no semver-major changes from Node 4 to 8). This version supports all Node.js versions from 0.8, as well as evergreen browsers and IE 10 & 11.\n\n# Usage\n\nYou can swap your `require('stream')` with `require('readable-stream')`\nwithout any changes, if you are just using one of the main classes and\nfunctions.\n\n```js\nconst {\n  Readable,\n  Writable,\n  Transform,\n  Duplex,\n  pipeline,\n  finished\n} = require('readable-stream')\n```\n\nNote that `require('stream')` will return `Stream`, while\n`require('readable-stream')` will return `Readable`. We discourage using\nwhatever is exported directly, but rather use one of the properties as\nshown in the example above.\n\n## Usage In Browsers\n\nYou will need a bundler like [`browserify`](https://github.com/browserify/browserify#readme), [`webpack`](https://webpack.js.org/), [`parcel`](https://github.com/parcel-bundler/parcel#readme) or similar. Polyfills are no longer required since version 4.2.0.\n\n# Streams Working Group\n\n`readable-stream` is maintained by the Streams Working Group, which\noversees the development and maintenance of the Streams API within\nNode.js. The responsibilities of the Streams Working Group include:\n\n- Addressing stream issues on the Node.js issue tracker.\n- Authoring and editing stream documentation within the Node.js project.\n- Reviewing changes to stream subclasses within the Node.js project.\n- Redirecting changes to streams from the Node.js project to this\n  project.\n- Assisting in the implementation of stream providers within Node.js.\n- Recommending versions of `readable-stream` to be included in Node.js.\n- Messaging about the future of streams to give the community advance\n  notice of changes.\n\n<a name=\"members\"></a>\n\n## Team Members\n\n- **Mathias Buus** ([@mafintosh](https://github.com/mafintosh)) &lt;mathiasbuus@gmail.com&gt;\n- **Matteo Collina** ([@mcollina](https://github.com/mcollina)) &lt;matteo.collina@gmail.com&gt;\n  - Release GPG key: 3ABC01543F22DD2239285CDD818674489FBC127E\n- **Robert Nagy** ([@ronag](https://github.com/ronag)) &lt;ronagy@icloud.com&gt;\n- **Vincent Weevers** ([@vweevers](https://github.com/vweevers)) &lt;mail@vincentweevers.nl&gt;",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{cc/40/3a756ce9e3587b285ad1c485d0ab9a3a83224a26fdfbec192f4664fa47cc96824fc0c7ce0461474b00fb0644f98447f76cb61722547e7942c9ccd54a661a → 7f/f2/05055dc94d326938973e3ffdf4b6bf1f839dde6387113e1448b69fa52bcda62651dda771c47a02c22998ad29444547ecfa70667e45fed612966649b3ed33}

@@ -4551,7 +4551,7 @@
     "latest": "7.0.6",
     "6x": "6.0.6"
   },
-  "_rev": "4180-b618abeb49f74b70",
+  "_rev": "4225-1375619c168a18a4",
   "_id": "cross-spawn",
   "readme": "",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{6c/d8/f7d05cdb4f810dcfdd54e22c5cb74e117fc38cdad278d5ccff18e84bd1bb04bfbb857b6aa3736c5fd17b7dcc8a87df638de1421932058dc81a597c2fbd64 → 81/2d/9729be8a74479cb149dc7ee80c5b8405330202fc4bb233e460c7a4af3f49e688836c94f27b27e477a95355fdd4100a5af203bcdf88ab3243846318fbf727}

@@ -14652,7 +14652,7 @@
   "dist-tags": {
     "latest": "3.972.6"
   },
-  "_rev": "339-ade91c455b61f83c",
+  "_rev": "350-223da79a8a8783e3",
   "_id": "@aws-sdk/middleware-recursion-detection",
   "readme": "# @aws-sdk/middleware-recursion-detection\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/middleware-recursion-detection/latest.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-recursion-detection)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/middleware-recursion-detection.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-recursion-detection)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{8d/f2/63c6b9905c8064595ec64ea93722d27e3bb70160c9dfb8c6c722d72ac2a11268f757f8e4dc2929ae3e999881ace3fec5f8c443862ccc9348a124a9c92f0d → 83/17/50cff9732f145fc50e44a1c4a64f911d52adbf9d0ed9f1a35ac28d36a4b254ff95b520d761bf992e7c63d36c5c1afc6f7977135b8bad47fec0301a554dae}

@@ -28784,7 +28784,7 @@
     "gamma": "1.0.0-gamma.8",
     "rc": "1.0.0-rc.10"
   },
-  "_rev": "353-65424011ae258f71",
+  "_rev": "364-6f92a07cd23d36d0",
   "_id": "@aws-sdk/credential-provider-env",
   "readme": "# @aws-sdk/credential-provider-env\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/credential-provider-env/latest.svg)](https://www.npmjs.com/package/@aws-sdk/credential-provider-env)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/credential-provider-env.svg)](https://www.npmjs.com/package/@aws-sdk/credential-provider-env)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly. Please use [@aws-sdk/credential-providers](https://www.npmjs.com/package/@aws-sdk/credential-providers)\ninstead.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{f0/ff/6296c668cbf580d6af28e80bbc357f78f08621c8e8bc17479b1f25bdc4537569af5a14a4ec507707e0f45f2fc930cf2964cd7dccbea6b22fa6dbc984e4ba → 84/8a/585b0bfe14ce3d9b9c40c6c84a217c57a613cab8176f0694d7a2d914a7ff37bd30100d7c809b0e7c6de8d8cd077d12bd8ab30ef0624c3a490df6a0319ce1}

@@ -2819,7 +2819,7 @@
   "dist-tags": {
     "latest": "10.6.0"
   },
-  "_rev": "2824-65a608d714b80870",
+  "_rev": "2860-348c31d01f73ee4e",
   "_id": "emoji-regex",
   "readme": "# emoji-regex [![Build status](https://github.com/mathiasbynens/emoji-regex/actions/workflows/main.yml/badge.svg)](https://github.com/mathiasbynens/emoji-regex/actions/workflows/main.yml) [![emoji-regex on npm](https://img.shields.io/npm/v/emoji-regex)](https://www.npmjs.com/package/emoji-regex)\n\n_emoji-regex_ offers a regular expression to match all emoji symbols and sequences (including textual representations of emoji) as per the Unicode Standard. It’s based on [_emoji-test-regex-pattern_](https://github.com/mathiasbynens/emoji-test-regex-pattern), which generates (at build time) the regular expression pattern based on the Unicode Standard. As a result, _emoji-regex_ can easily be updated whenever new emoji are added to Unicode.\n\nSince each version of _emoji-regex_ is tied to the latest Unicode version at the time of release, results are deterministic. This is important for use cases like image replacement, where you want to guarantee that an image asset is available for every possibly matched emoji. If you don’t need a deterministic regex, a lighter-weight, general emoji pattern is available via the [_emoji-regex-xs_](https://github.com/slevithan/emoji-regex-xs) package that follows the same API.\n\n## Installation\n\nVia [npm](https://www.npmjs.com/):\n\n```bash\nnpm install emoji-regex\n```\n\nIn [Node.js](https://nodejs.org/):\n\n```js\nconst emojiRegex = require('emoji-regex');\n// Note: because the regular expression has the global flag set, this module\n// exports a function that returns the regex rather than exporting the regular\n// expression itself, to make it impossible to (accidentally) mutate the\n// original regular expression.\n\nconst text = `\n\\u{231A}: ⌚ default emoji presentation character (Emoji_Presentation)\n\\u{2194}\\u{FE0F}: ↔️ default text presentation character rendered as emoji\n\\u{1F469}: 👩 emoji modifier base (Emoji_Modifier_Base)\n\\u{1F469}\\u{1F3FF}: 👩🏿 emoji modifier base followed by a modifier\n`;\n\nconst regex = emojiRegex();\nfor (const match of text.matchAll(regex)) {\n  const emoji = match[0];\n  console.log(`Matched sequence ${ emoji } — code points: ${ [...emoji].length }`);\n}\n```\n\nConsole output:\n\n```\nMatched sequence ⌚ — code points: 1\nMatched sequence ⌚ — code points: 1\nMatched sequence ↔️ — code points: 2\nMatched sequence ↔️ — code points: 2\nMatched sequence 👩 — code points: 1\nMatched sequence 👩 — code points: 1\nMatched sequence 👩🏿 — code points: 2\nMatched sequence 👩🏿 — code points: 2\n```\n\n## For maintainers\n\n### How to update emoji-regex after new Unicode Standard releases\n\n1. [Update _emoji-test-regex-pattern_ as described in its repository](https://github.com/mathiasbynens/emoji-test-regex-pattern#how-to-update-emoji-test-regex-pattern-after-new-uts51-releases).\n\n1. Bump the _emoji-test-regex-pattern_ dependency to the latest version.\n\n1. Update the Unicode data dependency in `package.json` by running the following commands:\n\n     ```sh\n     # Example: updating from Unicode v13 to Unicode v14.\n     npm uninstall @unicode/unicode-13.0.0\n     npm install @unicode/unicode-14.0.0 --save-dev\n     ````\n\n 1. Generate the new output:\n\n     ```sh\n     npm run build\n     ```\n\n 1. Verify that tests still pass:\n\n     ```sh\n     npm test\n     ```\n\n### How to publish a new release\n\n1. On the `main` branch, bump the emoji-regex version number in `package.json`:\n\n    ```sh\n    npm version patch -m 'Release v%s'\n    ```\n\n    Instead of `patch`, use `minor` or `major` [as needed](https://semver.org/).\n\n    Note that this produces a Git commit + tag.\n\n1. Push the release commit and tag:\n\n    ```sh\n    git push && git push --tags\n    ```\n\n    Our CI then automatically publishes the new release to npm.\n\n## Author\n\n| [![twitter/mathias](https://gravatar.com/avatar/24e08a9ea84deb17ae121074d0f17125?s=70)](https://twitter.com/mathias \"Follow @mathias on Twitter\") |\n|---|\n| [Mathias Bynens](https://mathiasbynens.be/) |\n\n## License\n\n_emoji-regex_ is available under the [MIT](https://mths.be/mit) license.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{22/94/103a72938154d69f990897d8c60d5525c01c6e1a8239988b794509e5ed2388ca45e9e0c6bcc2b1c7ab85795bb84fa58d66e14a6c8b32c0afc90cb31548fc → 85/27/a9568777d56712a9657948f054951bcada0921d326f99d11a5c1577381b9aa869f3ad2b00e420777aba92f11f08fa6c3d47af9282e1464a214895613b8ca}

@@ -1884,7 +1884,7 @@
     "latest": "4.1.0",
     "n-api": "3.0.3-napi"
   },
-  "_rev": "344-083f18c6a2a7e245",
+  "_rev": "355-9f44de9222532770",
   "_id": "bufferutil",
   "readme": "# bufferutil\n\n[![Version npm](https://img.shields.io/npm/v/bufferutil.svg?logo=npm)](https://www.npmjs.com/package/bufferutil)\n[![Linux/macOS/Windows Build](https://img.shields.io/github/actions/workflow/status/websockets/bufferutil/ci.yml?branch=master&label=build&logo=github)](https://github.com/websockets/bufferutil/actions?query=workflow%3ACI+branch%3Amaster)\n\n`bufferutil` is what makes `ws` fast. It provides some utilities to efficiently\nperform some operations such as masking and unmasking the data payload of\nWebSocket frames.\n\n## Installation\n\n```\nnpm install bufferutil --save-optional\n```\n\nThe `--save-optional` flag tells npm to save the package in your package.json\nunder the\n[`optionalDependencies`](https://docs.npmjs.com/files/package.json#optionaldependencies)\nkey.\n\n## API\n\nThe module exports two functions. To maximize performance, parameters are not\nvalidated. It is the caller's responsibility to ensure that they are correct.\n\n### `bufferUtil.mask(source, mask, output, offset, length)`\n\nMasks a buffer using the given masking-key as specified by the WebSocket\nprotocol.\n\n#### Arguments\n\n- `source` - The buffer to mask.\n- `mask` - A buffer representing the masking-key.\n- `output` - The buffer where to store the result.\n- `offset` - The offset at which to start writing.\n- `length` - The number of bytes to mask.\n\n#### Example\n\n```js\n'use strict';\n\nconst bufferUtil = require('bufferutil');\nconst crypto = require('crypto');\n\nconst source = crypto.randomBytes(10);\nconst mask = crypto.randomBytes(4);\n\nbufferUtil.mask(source, mask, source, 0, source.length);\n```\n\n### `bufferUtil.unmask(buffer, mask)`\n\nUnmasks a buffer using the given masking-key as specified by the WebSocket\nprotocol.\n\n#### Arguments\n\n- `buffer` - The buffer to unmask.\n- `mask` - A buffer representing the masking-key.\n\n#### Example\n\n```js\n'use strict';\n\nconst bufferUtil = require('bufferutil');\nconst crypto = require('crypto');\n\nconst buffer = crypto.randomBytes(10);\nconst mask = crypto.randomBytes(4);\n\nbufferUtil.unmask(buffer, mask);\n```\n\n## License\n\n[MIT](LICENSE)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{31/ce/bbd17cd373afb6c501bd08ea79605e7fc2fe77284cc02594e1f934595e2df574e859b3c8de3fca0ba25c47e24ddccf463fd15716d71395e653142f65edf0 → 87/99/fbceb1b2551f33051facc2ab5d1b772b725e97dfd04991402f5a6b3b261e314acce3ba02a7ef890af0f2564c36eb9b766c4783e29e6b8c52d502e6eaa0ab}

@@ -5540,7 +5540,7 @@
   "dist-tags": {
     "latest": "4.2.10"
   },
-  "_rev": "228-9e4e099286dc3e67",
+  "_rev": "239-6e79cff849eb5281",
   "_id": "@smithy/service-error-classification",
   "readme": "# @smithy/service-error-classification\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/service-error-classification/latest.svg)](https://www.npmjs.com/package/@smithy/service-error-classification)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/service-error-classification.svg)](https://www.npmjs.com/package/@smithy/service-error-classification)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{58/8e/27e3b7ca2af0c161c0e9606558a5f2513eecb377c588e4c2a635464f96f15c76f398eaa2dbff711470ad3dc5a756d37f89075262ca190745c18895914b26 → 88/f6/39bb52459bc19f9511d50c0d69534b229be5886458d19b31a2ee32a5d72324fb14f624b160fcb333ed597b62cf9c37332efb8b3bbbdd5356a4160cd96957}

@@ -1103,7 +1103,7 @@
   "dist-tags": {
     "latest": "5.2.0"
   },
-  "_rev": "366-21c1e524b059eb75",
+  "_rev": "377-b38ad23599d8a1ca",
   "_id": "@aws-crypto/util",
   "readme": "# @aws-crypto/util\n\nHelper functions\n\n## Usage\n\n```\nimport { convertToBuffer } from '@aws-crypto/util';\n\nconst data = \"asdf\";\nconst utf8EncodedUint8Array = convertToBuffer(data);\n```\n\n## Test\n\n`npm test`",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{31/6e/80364cfd9556b49f850032c6b2e36978bfe36fa2e0fc8552a4b76a2e4ec3eaea53b81d6de3eeca054cdc75d4117ab586ca4f36be169680819c8429b34f72 → 89/61/c100a58e367e30fe00b21c7fa40170469750c238c8bebae259e029e710c43fdd65569159732cff54dc8904fea7342c9a389164d08de29992ffe677d751d2}

@@ -3816,11 +3816,96 @@
       },
       "_hasShrinkwrap": false,
       "contributors": []
+    },
+    "3.5.0": {
+      "name": "bare-buffer",
+      "version": "3.5.0",
+      "description": "Native buffers for JavaScript",
+      "exports": {
+        "./package": "./package.json",
+        ".": {
+          "types": "./index.d.ts",
+          "default": "./index.js"
+        },
+        "./global": {
+          "types": "./global.d.ts",
+          "default": "./global.js"
+        },
+        "./constants": {
+          "types": "./lib/constants.d.ts",
+          "default": "./lib/constants.js"
+        }
+      },
+      "addon": true,
+      "scripts": {
+        "test": "prettier . --check && bare test.js"
+      },
+      "repository": {
+        "type": "git",
+        "url": "git+https://github.com/holepunchto/bare-buffer.git"
+      },
+      "author": {
+        "name": "Holepunch"
+      },
+      "license": "Apache-2.0",
+      "bugs": {
+        "url": "https://github.com/holepunchto/bare-buffer/issues"
+      },
+      "homepage": "https://github.com/holepunchto/bare-buffer#readme",
+      "engines": {
+        "bare": ">=1.20.0"
+      },
+      "devDependencies": {
+        "brittle": "^3.1.1",
+        "cmake-bare": "^1.1.6",
+        "cmake-fetch": "^1.0.0",
+        "prettier": "^3.3.3",
+        "prettier-config-holepunch": "^2.0.0"
+      },
+      "gitHead": "df205baeb9a1c476d695b5d6fd454ec0a7b3de17",
+      "types": "./index.d.ts",
+      "_id": "bare-buffer@3.5.0",
+      "_nodeVersion": "25.6.1",
+      "_npmVersion": "11.9.0",
+      "dist": {
+        "integrity": "sha512-Oybzt+Pu85Tl66QQzS/tS0FJXxhvdcRvasrdWgw85XWjPNG9ijC9IfjFf+B5SbcpaMX99OjhdtJ5Ct2yzzBJsA==",
+        "shasum": "b56cdeb8cb6d3f320fe7c20ed8c19d539959b8eb",
+        "tarball": "https://verdaccio.mrsdev.ru/bare-buffer/-/bare-buffer-3.5.0.tgz",
+        "fileCount": 32,
+        "unpackedSize": 1089041,
+        "signatures": [
+          {
+            "keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U",
+            "sig": "MEUCIHzuOe3NeKz4WndjjB2rj8fIulWvmWy5O5x1snfX6ViYAiEAxiuXyT0wBWphgaQxPAp1K4n5zVSuG/oLk6UTiwOcXMg="
+          }
+        ]
+      },
+      "_npmUser": {
+        "name": "kasperisager",
+        "email": "kasperisager@hey.com"
+      },
+      "directories": {},
+      "maintainers": [
+        {
+          "name": "mafintosh",
+          "email": "mathiasbuus@gmail.com"
+        },
+        {
+          "name": "kasperisager",
+          "email": "kasperisager@hey.com"
+        }
+      ],
+      "_npmOperationalInternal": {
+        "host": "s3://npm-registry-packages-npm-production",
+        "tmp": "tmp/bare-buffer_3.5.0_1772471140954_0.9788586919495803"
+      },
+      "_hasShrinkwrap": false,
+      "contributors": []
     }
   },
   "time": {
     "created": "2023-05-16T08:13:44.306Z",
-    "modified": "2026-02-17T09:25:48.753Z",
+    "modified": "2026-03-02T17:05:41.269Z",
     "1.2.2": "2023-05-16T08:13:44.492Z",
     "1.2.3": "2023-05-22T11:57:06.664Z",
     "1.2.4": "2023-05-22T13:25:18.256Z",
@@ -3873,13 +3958,14 @@
     "3.4.1": "2025-10-16T10:10:18.621Z",
     "3.4.2": "2025-11-06T07:37:52.950Z",
     "3.4.3": "2026-02-13T09:05:17.622Z",
-    "3.4.4": "2026-02-17T09:25:48.639Z"
+    "3.4.4": "2026-02-17T09:25:48.639Z",
+    "3.5.0": "2026-03-02T17:05:41.156Z"
   },
   "users": {},
   "dist-tags": {
-    "latest": "3.4.4"
+    "latest": "3.5.0"
   },
-  "_rev": "1-3ca9b2cc8c982328",
+  "_rev": "12-fcbf07185ff87651",
   "_id": "bare-buffer",
   "readme": "# bare-buffer\n\nNative buffers for JavaScript.\n\n```\nnpm i bare-buffer\n```\n\n## Usage\n\n```js\nconst Buffer = require('bare-buffer')\n\nconst message = Buffer.from('hello')\nconst empty = Buffer.alloc(16)\nconst buffer = Buffer.allocUnsafe(4).fill(123)\nconst combined = Buffer.concat([buffer, buffer])\n```\n\n## License\n\nApache-2.0",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{c2/17/edddef70406326c7efd6e3d3c9aa41a63241eeadbaeac6702eb196561b2c9ca6a146723c646111eaff1d8fbbf36340270ffc401d132c8a47623f24701656 → 8a/b4/d39b55dd843b768bbe5760afbc0a488ea8356a81b18908afd56968a621735e956dd8a83cd910d2f17f4416bb6c606cdbb245727027f65e30b1d85a81c1d5}

@@ -25096,7 +25096,7 @@
   "dist-tags": {
     "latest": "3.973.15"
   },
-  "_rev": "213-d06181a797cc687b",
+  "_rev": "224-b894dd47aed6c4ab",
   "_id": "@aws-sdk/core",
   "readme": "# `@aws-sdk/core`\n\nThis package provides common or core functionality to the AWS SDK for JavaScript (v3).\n\nYou do not need to explicitly install this package, since it will be transitively installed by AWS SDK clients.\n\n## `@aws-sdk/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).\n\nThink of `@aws-sdk/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 an SDK 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 `@aws-sdk/<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 `@aws-sdk/core`.\n  The linter runs during `yarn build` and also as `yarn lint`.\n\n### When should I create an `@aws-sdk/core/submodule` vs. `@aws-sdk/new-package`?\n\nKeep in mind that the core package is installed by all AWS SDK clients.\n\nIf the component functionality is upstream of multiple clients, it is\na good candidate for a core submodule. For example, XML serialization.\n\nIf the component's functionality is downstream of a client, for example S3 pre-signing,\nit should be a standalone package with potentially a peer or runtime dependency on an AWS SDK client.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{c1/16/afb5f95882d3c6941f85414b38892d58d1a057911b92e5f771068f68cd804fd4a6b93618fc31f41309dba37c9e85e381344b9fd08e4ae2150e52461e0d2c → 8b/4e/50cf6a74628312026149396317be4ba091ecd0392795a144453a3e93fc65013929adb47fd2b39ff104cdf67e545c54f649bf063fa287404d737590a27a3d}

@@ -1344,7 +1344,7 @@
   "dist-tags": {
     "latest": "4.2.1"
   },
-  "_rev": "215-eb11e58805b57cb7",
+  "_rev": "226-94aaeed314597bb2",
   "_id": "@smithy/util-buffer-from",
   "readme": "# @smithy/util-buffer-from\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/util-buffer-from/latest.svg)](https://www.npmjs.com/package/@smithy/util-buffer-from)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/util-buffer-from.svg)](https://www.npmjs.com/package/@smithy/util-buffer-from)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{42/70/4ea7b8edcc8ee2db688277114d3aef4f5459231d74224c78f5726f1e7ffde0ea1396af58c909d0e5f12cbb67645c0f3485022da017034bb80ad25035ecaa → 8e/d1/c14bcdd621c24af4272198a708ab38f73d18efc3b10309055df3183f27430b9957290fe086af5d911e7005c5c7051759f95bf9c42a226d4329bf20ac2bc0}

@@ -35546,7 +35546,7 @@
     "gamma": "1.0.0-gamma.8",
     "rc": "1.0.0-rc.10"
   },
-  "_rev": "321-23d5b7de7d969766",
+  "_rev": "332-115b3ab33a746310",
   "_id": "@aws-sdk/middleware-sdk-s3",
   "readme": "# @aws-sdk/middleware-sdk-s3\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/middleware-sdk-s3/latest.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-sdk-s3)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/middleware-sdk-s3.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-sdk-s3)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{f1/e5/973c03b4c9beb9da3c8a4f7d0a4664b0182983667b0c671deb2261289b87c4e77e2e9132f81ef28cd36ba0de3cca9b0134bd9b21781514fd1391bc81e139 → 90/34/8c4e38200699c6a209f8d6cec1f21582748b50354ed170be8d94fe326f18ed586e77c5c8a6dbcc4f7e9a67f74975802f3efe15fd425e040c97579d945167}

@@ -6575,7 +6575,7 @@
   "dist-tags": {
     "latest": "4.2.10"
   },
-  "_rev": "218-0a64b00eedf85e22",
+  "_rev": "229-9842685e9f200676",
   "_id": "@smithy/middleware-content-length",
   "readme": "# @smithy/middleware-content-length\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/middleware-content-length/latest.svg)](https://www.npmjs.com/package/@smithy/middleware-content-length)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/middleware-content-length.svg)](https://www.npmjs.com/package/@smithy/middleware-content-length)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{4b/9a/a8454a41438670019b2980f667a02e68383252bb727fde295f778b808493e79fd4c1f7e73310bd6e32b4d8df16bd9988e61f35b250cf76a242a732b44cc6 → 90/70/010c9aad6a5861873bae917598d73a1000a1ec49148af239d5acb1c495bf429a23b1eedb4378fad55f8e9103c583842a64a96ad029181b0df1ae34e8438a}

@@ -496,7 +496,7 @@
   "dist-tags": {
     "latest": "5.1.0"
   },
-  "_rev": "2877-b03855e1432f7abf",
+  "_rev": "2905-9cc9afe76cf90899",
   "_id": "is-fullwidth-code-point",
   "readme": "# is-fullwidth-code-point\n\n> Check if the character represented by a given [Unicode code point](https://en.wikipedia.org/wiki/Code_point) is [fullwidth](https://en.wikipedia.org/wiki/Halfwidth_and_fullwidth_forms)\n\n## Install\n\n```sh\nnpm install is-fullwidth-code-point\n```\n\n## Usage\n\n```js\nimport isFullwidthCodePoint from 'is-fullwidth-code-point';\n\nisFullwidthCodePoint('谢'.codePointAt(0));\n//=> true\n\nisFullwidthCodePoint('a'.codePointAt(0));\n//=> false\n```\n\n## API\n\n### isFullwidthCodePoint(codePoint)\n\n#### codePoint\n\nType: `number`\n\nThe [code point](https://en.wikipedia.org/wiki/Code_point) of a character.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{9e/04/58b1939e3bdf2f2497389f958d6f06441c5c0b140e4d73689f4e431f3cd6ef90378ef40bad83d8d40c3b61606e8221184ff2a148b7145720fd692c0d4cd7 → 92/02/c884d8d6ef8d16265819c7a0ceb2fe5675ef7838f70cee515795865977292aee43ca20cfce5d7aff923af794ed2b6555e32ca407338dbdc105b236765869}

@@ -339,7 +339,7 @@
   "dist-tags": {
     "latest": "9.0.0"
   },
-  "_rev": "1085-70491cc8d0af469c",
+  "_rev": "1113-ba07640f3036f6ec",
   "_id": "@isaacs/cliui",
   "readme": "# @isaacs/cliui\n\nFork of [cliui](http://npm.im/cliui). Fully CommonJS/ESM\nhybridized, with all dependencies vendored and optimized for\nminimal bundle size without sacrificing functionality.\n\neasily create complex multi-column command-line-interfaces.\n\n## Changes in v9\n\nThe default export is no longer exported. So, intead of `import\ncliui from '@isaacs/cliui'`, you'll do `import { cliui } from\n'@isaacs/cliui'`. This is done in order to minimize typescript\noddness between the CommonJS and ESM versions.\n\nA minified export is provided at `@isaacs/cliui/min`. If you are\nconcerned about bundle size, that's the thing to use.\n\n## Example\n\n```js\nimport { cliui } from '@isaacs/cliui'\n// or: const { cliui } = require('cliui')\nconst ui = cliui()\n\nui.div('Usage: $0 [command] [options]')\n\nui.div({\n  text: 'Options:',\n  padding: [2, 0, 1, 0],\n})\n\nui.div(\n  {\n    text: '-f, --file',\n    width: 20,\n    padding: [0, 4, 0, 4],\n  },\n  {\n    text:\n      'the file to load.' +\n      chalk.green('(if this description is long it wraps).'),\n    width: 20,\n  },\n  {\n    text: chalk.red('[required]'),\n    align: 'right',\n  },\n)\n\nconsole.log(ui.toString())\n```\n\n## Deno/ESM Support\n\nLoad the minified version from unpkg.\n\n```typescript\nimport { cliui } from 'https://unpkg.com/@isaacs/cliui/dist/esm/index.min.js'\n\nconst ui = cliui({})\n\nui.div('Usage: $0 [command] [options]')\n\nui.div({\n  text: 'Options:',\n  padding: [2, 0, 1, 0],\n})\n\nui.div({\n  text: '-f, --file',\n  width: 20,\n  padding: [0, 4, 0, 4],\n})\n\nconsole.log(ui.toString())\n```\n\n<img width=\"500\" src=\"screenshot.png\">\n\n## Layout DSL\n\ncliui exposes a simple layout DSL:\n\nIf you create a single `ui.div`, passing a string rather than an\nobject:\n\n- `\\n`: characters will be interpreted as new rows.\n- `\\t`: characters will be interpreted as new columns.\n- `\\s`: characters will be interpreted as padding.\n\n**as an example...**\n\n```js\nvar ui = require('./')({\n  width: 60,\n})\n\nui.div(\n  'Usage: node ./bin/foo.js\\n' +\n    '  <regex>\\t  provide a regex\\n' +\n    '  <glob>\\t  provide a glob\\t [required]',\n)\n\nconsole.log(ui.toString())\n```\n\n**will output:**\n\n```shell\nUsage: node ./bin/foo.js\n  <regex>  provide a regex\n  <glob>   provide a glob          [required]\n```\n\n## Methods\n\n```js\ncliui = require('@isaacs/cliui')\n```\n\n### cliui({width: integer})\n\nSpecify the maximum width of the UI being generated.\nIf no width is provided, cliui will try to get the current window's width and use it, and if that doesn't work, width will be set to `80`.\n\n### cliui({wrap: boolean})\n\nEnable or disable the wrapping of text in a column.\n\n### cliui.div(column, column, column)\n\nCreate a row with any number of columns, a column\ncan either be a string, or an object with the following\noptions:\n\n- **text:** some text to place in the column.\n- **width:** the width of a column.\n- **align:** alignment, `right` or `center`.\n- **padding:** `[top, right, bottom, left]`.\n- **border:** should a border be placed around the div?\n\n### cliui.span(column, column, column)\n\nSimilar to `div`, except the next row will be appended without\na new line being created.\n\n### cliui.resetOutput()\n\nResets the UI elements of the current cliui instance, maintaining the values\nset for `width` and `wrap`.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{67/28/26188a9850694245c5b211cce720c5e0a033132ad56583c5cbf9afdcf533eb625ca3a07b6f7e9545a4acaa841aafd1ddbaf44989c8c67dd01b65f23b1252 → 97/23/ef4d90761a1993e8a22c4b728ff16a499eef833821c13ca5012b0e30604434982b521fee6eee3c61c51d3fce9f621e508403b41f9764688cfa2c3dd96e86}

@@ -1172,7 +1172,7 @@
   "dist-tags": {
     "latest": "3.3.0"
   },
-  "_rev": "3413-2ed2efd38921e416",
+  "_rev": "3459-c36784a66425e014",
   "_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/{87/7e/a91b4681ca2054a61666f7f2292e41103bb7da61b5cb4b7b8215f77e86651e8d8ecf9907fa0e750262efcb263259393646862be0aeb4c27384ff4601f2d4 → 9a/56/0ae7fcc92b11dd0b79b87aa0e19bc64bb144b2f003a47df371f8e6529d42207b4d41c03caa5a03cd9f47c45632c19a95452614d5ae72bf8f52f7986bf220}

@@ -1244,7 +1244,7 @@
   "dist-tags": {
     "latest": "5.0.2"
   },
-  "_rev": "245-eebad529a83d95cc",
+  "_rev": "256-d94a4fabb16b4658",
   "_id": "archiver-utils",
   "readme": "# Archiver Utils\n\n## Things of Interest\n- [Changelog](https://github.com/archiverjs/archiver-utils/releases)\n- [Contributing](https://github.com/archiverjs/archiver-utils/blob/master/CONTRIBUTING.md)\n- [MIT License](https://github.com/archiverjs/archiver-utils/blob/master/LICENSE)",
   "_attachments": {}