mrs-toolbox-cli 5.3.1 → 5.3.2

package/npm-cache/_cacache/content-v2/sha512/{ef/49/38c355630ba0575cd42819ce098f0b2414c523133fbc171457ec80f55099049f7cc8f6d3c9b43f1014f5cabb6314dab9a8c87b29c3e35511c1b301b050c3 → 82/f5/87a65587087bd027a0651f1bcd1ab49f7c963b82176b710815a442d256b789ea7dad10423967c7d7bd90d236c0b8338e007396ff4e119dd7eb27931c5dd5}

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

package/npm-cache/_cacache/content-v2/sha512/{c1/4a/0dbda3380a2502989f6819f1ad190a7f8b05549c142e8918ca323b521ae3608c00613c2d43d36aa45ab64d3d752312183f55811568d11374d2834be58264 → 84/3c/0a37f0e9259f9fa7fc236704a943bce7cbf58ab3e29ca7ba64b62e75e3b58015971840ccf3df0804003e53bcf669299ff5c4dff013a45e598450d6b53cfc}

@@ -1106,7 +1106,7 @@
   "dist-tags": {
     "latest": "7.0.0"
   },
-  "_rev": "484-cffc34a74b72646e",
+  "_rev": "485-e97a602ea7d869ae",
   "_id": "webidl-conversions",
   "readme": "# Web IDL Type Conversions on JavaScript Values\n\nThis package implements, in JavaScript, the algorithms to convert a given JavaScript value according to a given [Web IDL](http://heycam.github.io/webidl/) [type](http://heycam.github.io/webidl/#idl-types).\n\nThe goal is that you should be able to write code like\n\n```js\n\"use strict\";\nconst conversions = require(\"webidl-conversions\");\n\nfunction doStuff(x, y) {\n    x = conversions[\"boolean\"](x);\n    y = conversions[\"unsigned long\"](y);\n    // actual algorithm code here\n}\n```\n\nand your function `doStuff` will behave the same as a Web IDL operation declared as\n\n```webidl\nundefined doStuff(boolean x, unsigned long y);\n```\n\n## API\n\nThis package's main module's default export is an object with a variety of methods, each corresponding to a different Web IDL type. Each method, when invoked on a JavaScript value, will give back the new JavaScript value that results after passing through the Web IDL conversion rules. (See below for more details on what that means.) Alternately, the method could throw an error, if the Web IDL algorithm is specified to do so: for example `conversions[\"float\"](NaN)` [will throw a `TypeError`](http://heycam.github.io/webidl/#es-float).\n\nEach method also accepts a second, optional, parameter for miscellaneous options. For conversion methods that throw errors, a string option `{ context }` may be provided to provide more information in the error message. (For example, `conversions[\"float\"](NaN, { context: \"Argument 1 of Interface's operation\" })` will throw an error with message `\"Argument 1 of Interface's operation is not a finite floating-point value.\"`)\n\nIf we are dealing with multiple JavaScript realms (such as those created using Node.js' [vm](https://nodejs.org/api/vm.html) module or the HTML `iframe` element), and exceptions from another realm need to be thrown, one can supply an object option `globals` containing the following properties:\n\n```js\n{\n  globals: {\n    Number,\n    String,\n    TypeError\n  }\n}\n```\n\nThose specific functions will be used when throwing exceptions.\n\nSpecific conversions may also accept other options, the details of which can be found below.\n\n## Conversions implemented\n\nConversions for all of the basic types from the Web IDL specification are implemented:\n\n- [`any`](https://heycam.github.io/webidl/#es-any)\n- [`undefined`](https://heycam.github.io/webidl/#es-undefined)\n- [`boolean`](https://heycam.github.io/webidl/#es-boolean)\n- [Integer types](https://heycam.github.io/webidl/#es-integer-types), which can additionally be provided the boolean options `{ clamp, enforceRange }` as a second parameter\n- [`float`](https://heycam.github.io/webidl/#es-float), [`unrestricted float`](https://heycam.github.io/webidl/#es-unrestricted-float)\n- [`double`](https://heycam.github.io/webidl/#es-double), [`unrestricted double`](https://heycam.github.io/webidl/#es-unrestricted-double)\n- [`DOMString`](https://heycam.github.io/webidl/#es-DOMString), which can additionally be provided the boolean option `{ treatNullAsEmptyString }` as a second parameter\n- [`ByteString`](https://heycam.github.io/webidl/#es-ByteString), [`USVString`](https://heycam.github.io/webidl/#es-USVString)\n- [`object`](https://heycam.github.io/webidl/#es-object)\n- [Buffer source types](https://heycam.github.io/webidl/#es-buffer-source-types), which can additionally be provided with the boolean option `{ allowShared }` as a second parameter\n\nAdditionally, for convenience, the following derived type definitions are implemented:\n\n- [`ArrayBufferView`](https://heycam.github.io/webidl/#ArrayBufferView), which can additionally be provided with the boolean option `{ allowShared }` as a second parameter\n- [`BufferSource`](https://heycam.github.io/webidl/#BufferSource)\n- [`DOMTimeStamp`](https://heycam.github.io/webidl/#DOMTimeStamp)\n\nDerived types, such as nullable types, promise types, sequences, records, etc. are not handled by this library. You may wish to investigate the [webidl2js](https://github.com/jsdom/webidl2js) project.\n\n### A note on the `long long` types\n\nThe `long long` and `unsigned long long` Web IDL types can hold values that cannot be stored in JavaScript numbers. Conversions are still accurate as we make use of BigInt in the conversion process, but in the case of `unsigned long long` we simply cannot represent some possible output values in JavaScript. For example, converting the JavaScript number `-1` to a Web IDL `unsigned long long` is supposed to produce the Web IDL value `18446744073709551615`. Since we are representing our Web IDL values in JavaScript, we can't represent `18446744073709551615`, so we instead the best we could do is `18446744073709551616` as the output.\n\nTo mitigate this, we could return the raw BigInt value from the conversion function, but right now it is not implemented. If your use case requires such precision, [file an issue](https://github.com/jsdom/webidl-conversions/issues/new).\n\nOn the other hand, `long long` conversion is always accurate, since the input value can never be more precise than the output value.\n\n### A note on `BufferSource` types\n\nAll of the `BufferSource` types will throw when the relevant `ArrayBuffer` has been detached. This technically is not part of the [specified conversion algorithm](https://heycam.github.io/webidl/#es-buffer-source-types), but instead part of the [getting a reference/getting a copy](https://heycam.github.io/webidl/#ref-for-dfn-get-buffer-source-reference%E2%91%A0) algorithms. We've consolidated them here for convenience and ease of implementation, but if there is a need to separate them in the future, please open an issue so we can investigate.\n\n## Background\n\nWhat's actually going on here, conceptually, is pretty weird. Let's try to explain.\n\nWeb IDL, as part of its madness-inducing design, has its own type system. When people write algorithms in web platform specs, they usually operate on Web IDL values, i.e. instances of Web IDL types. For example, if they were specifying the algorithm for our `doStuff` operation above, they would treat `x` as a Web IDL value of [Web IDL type `boolean`](http://heycam.github.io/webidl/#idl-boolean). Crucially, they would _not_ treat `x` as a JavaScript variable whose value is either the JavaScript `true` or `false`. They're instead working in a different type system altogether, with its own rules.\n\nSeparately from its type system, Web IDL defines a [\"binding\"](http://heycam.github.io/webidl/#ecmascript-binding) of the type system into JavaScript. This contains rules like: when you pass a JavaScript value to the JavaScript method that manifests a given Web IDL operation, how does that get converted into a Web IDL value? For example, a JavaScript `true` passed in the position of a Web IDL `boolean` argument becomes a Web IDL `true`. But, a JavaScript `true` passed in the position of a [Web IDL `unsigned long`](http://heycam.github.io/webidl/#idl-unsigned-long) becomes a Web IDL `1`. And so on.\n\nFinally, we have the actual implementation code. This is usually C++, although these days [some smart people are using Rust](https://github.com/servo/servo). The implementation, of course, has its own type system. So when they implement the Web IDL algorithms, they don't actually use Web IDL values, since those aren't \"real\" outside of specs. Instead, implementations apply the Web IDL binding rules in such a way as to convert incoming JavaScript values into C++ values. For example, if code in the browser called `doStuff(true, true)`, then the implementation code would eventually receive a C++ `bool` containing `true` and a C++ `uint32_t` containing `1`.\n\nThe upside of all this is that implementations can abstract all the conversion logic away, letting Web IDL handle it, and focus on implementing the relevant methods in C++ with values of the correct type already provided. That is payoff of Web IDL, in a nutshell.\n\nAnd getting to that payoff is the goal of _this_ project—but for JavaScript implementations, instead of C++ ones. That is, this library is designed to make it easier for JavaScript developers to write functions that behave like a given Web IDL operation. So conceptually, the conversion pipeline, which in its general form is JavaScript values ↦ Web IDL values ↦ implementation-language values, in this case becomes JavaScript values ↦ Web IDL values ↦ JavaScript values. And that intermediate step is where all the logic is performed: a JavaScript `true` becomes a Web IDL `1` in an unsigned long context, which then becomes a JavaScript `1`.\n\n## Don't use this\n\nSeriously, why would you ever use this? You really shouldn't. Web IDL is … strange, and you shouldn't be emulating its semantics. If you're looking for a generic argument-processing library, you should find one with better rules than those from Web IDL. In general, your JavaScript should not be trying to become more like Web IDL; if anything, we should fix Web IDL to make it more like JavaScript.\n\nThe _only_ people who should use this are those trying to create faithful implementations (or polyfills) of web platform interfaces defined in Web IDL. Its main consumer is the [jsdom](https://github.com/jsdom/jsdom) project.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{e3/50/794a68bf4627a19dd01a85809dffefb4a59dd30365b592e3f826aaf84cbe96ac2b1c038ac36bba8128f97e08167833f5590029c93ceec0ecc8959eff35b8 → 87/65/e1618923a86a1c430c8a6955b185831da301a0fda74a4413c1393e1be4acea1a9f2b68f3a8345da3f9ab3fac01bf1fd176683f869464e4cc057324901ce1}

@@ -8107,7 +8107,7 @@
     "latest": "3.2.6",
     "next": "3.1.0"
   },
-  "_rev": "1113-020705072b293945",
+  "_rev": "1114-058598cc211c007c",
   "_id": "async",
   "readme": "![Async Logo](https://raw.githubusercontent.com/caolan/async/master/logo/async-logo_readme.jpg)\n\n![Github Actions CI status](https://github.com/caolan/async/actions/workflows/ci.yml/badge.svg)\n[![NPM version](https://img.shields.io/npm/v/async.svg)](https://www.npmjs.com/package/async)\n[![Coverage Status](https://coveralls.io/repos/caolan/async/badge.svg?branch=master)](https://coveralls.io/r/caolan/async?branch=master)\n[![Join the chat at https://gitter.im/caolan/async](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/caolan/async?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)\n[![jsDelivr Hits](https://data.jsdelivr.com/v1/package/npm/async/badge?style=rounded)](https://www.jsdelivr.com/package/npm/async)\n\n<!--\n|Linux|Windows|MacOS|\n|-|-|-|\n|[![Linux Build Status](https://dev.azure.com/caolanmcmahon/async/_apis/build/status/caolan.async?branchName=master&jobName=Linux&configuration=Linux%20node_10_x)](https://dev.azure.com/caolanmcmahon/async/_build/latest?definitionId=1&branchName=master) | [![Windows Build Status](https://dev.azure.com/caolanmcmahon/async/_apis/build/status/caolan.async?branchName=master&jobName=Windows&configuration=Windows%20node_10_x)](https://dev.azure.com/caolanmcmahon/async/_build/latest?definitionId=1&branchName=master) | [![MacOS Build Status](https://dev.azure.com/caolanmcmahon/async/_apis/build/status/caolan.async?branchName=master&jobName=OSX&configuration=OSX%20node_10_x)](https://dev.azure.com/caolanmcmahon/async/_build/latest?definitionId=1&branchName=master)| -->\n\nAsync is a utility module which provides straight-forward, powerful functions for working with [asynchronous JavaScript](http://caolan.github.io/async/v3/global.html). Although originally designed for use with [Node.js](https://nodejs.org/) and installable via `npm i async`, it can also be used directly in the browser.  An ESM/MJS version is included in the main `async` package that should automatically be used with compatible bundlers such as Webpack and Rollup.\n\nA pure ESM version of Async is available as [`async-es`](https://www.npmjs.com/package/async-es).\n\nFor Documentation, visit <https://caolan.github.io/async/>\n\n*For Async v1.5.x documentation, go [HERE](https://github.com/caolan/async/blob/v1.5.2/README.md)*\n\n\n```javascript\n// for use with Node-style callbacks...\nvar async = require(\"async\");\n\nvar obj = {dev: \"/dev.json\", test: \"/test.json\", prod: \"/prod.json\"};\nvar configs = {};\n\nasync.forEachOf(obj, (value, key, callback) => {\n    fs.readFile(__dirname + value, \"utf8\", (err, data) => {\n        if (err) return callback(err);\n        try {\n            configs[key] = JSON.parse(data);\n        } catch (e) {\n            return callback(e);\n        }\n        callback();\n    });\n}, err => {\n    if (err) console.error(err.message);\n    // configs is now a map of JSON data\n    doSomethingWith(configs);\n});\n```\n\n```javascript\nvar async = require(\"async\");\n\n// ...or ES2017 async functions\nasync.mapLimit(urls, 5, async function(url) {\n    const response = await fetch(url)\n    return response.body\n}, (err, results) => {\n    if (err) throw err\n    // results is now an array of the response bodies\n    console.log(results)\n})\n```",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{a5/08/1d866abf4fe606e9505571d66948b08a1db137b48569a635a78482dde25fbdc28d3a4a2c69e57eb1b8effe618ca31c5201378b6b392ebfa5fd23a8d68bc8 → 87/a0/0c8b6f623d957fc73d0057ee2dff45a852b0daf6341001eb21521b1d647c0749ee287857b25886ff21a130253a010437658571a56e6e51a5010c6418d66b}

@@ -13966,7 +13966,7 @@
   "dist-tags": {
     "latest": "3.743.0"
   },
-  "_rev": "90-b2e564f6e8b2fcf8",
+  "_rev": "91-09039a2c2da4e154",
   "_id": "@aws-sdk/util-endpoints",
   "readme": "# @aws-sdk/util-endpoints\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/util-endpoints/latest.svg)](https://www.npmjs.com/package/@aws-sdk/util-endpoints)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/util-endpoints.svg)](https://www.npmjs.com/package/@aws-sdk/util-endpoints)\n\n> An internal package",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{3d/2d/0c172293ac97d3d654b625306698bf91664db1405f3f900a17e44161e0ad8d6f7d0c7719efce17a4bdc2cbb2a038565b76d499aa15c8709e8a7121e8b4bd → 87/da/9ed977770c7fa7242544a48e0dadab0178babfea7c1820d1559a321871ddcb5b617a2ca1115cb0f18f08c48d44dd5114cedf777964447e912b1897cf335d}

@@ -5910,7 +5910,7 @@
     "gamma": "1.0.0-gamma.7",
     "rc": "1.0.0-rc.8"
   },
-  "_rev": "109-088129040d98cf82",
+  "_rev": "111-1a3028bafcc1c6a7",
   "_id": "@aws-sdk/util-locate-window",
   "readme": "# @aws-sdk/util-locate-window\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/util-locate-window/latest.svg)](https://www.npmjs.com/package/@aws-sdk/util-locate-window)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/util-locate-window.svg)](https://www.npmjs.com/package/@aws-sdk/util-locate-window)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{be/e0/736c7f095edf21b6f8e62a8900ef2e19b422d8fb6c0710bdf7d205f38bf92b9fc491c4874dc99318903c0bb356ada5b4bd1b8c1319c29272cdcfb5b24939 → 88/76/f76e45139044a6d9f24d287fc1191b10de15c7cc7616a54544d3384d9509f1a001dfce5be64e8824b75cc03aa380d7b2be64ed49844a15fce87fac746beb}

@@ -969,7 +969,7 @@
   "dist-tags": {
     "latest": "0.11.0"
   },
-  "_rev": "116-4ec92356ec8b0189",
+  "_rev": "118-372b4a021d69ac87",
   "_id": "@pkgjs/parseargs",
   "readme": "<!-- omit in toc -->\n# parseArgs\n\n[![Coverage][coverage-image]][coverage-url]\n\nPolyfill of `util.parseArgs()`\n\n## `util.parseArgs([config])`\n\n<!-- YAML\nadded: v18.3.0\nchanges:\n  - version: REPLACEME\n    pr-url: https://github.com/nodejs/node/pull/43459\n    description: add support for returning detailed parse information\n                 using `tokens` in input `config` and returned properties.\n-->\n\n> Stability: 1 - Experimental\n\n* `config` {Object} Used to provide arguments for parsing and to configure\n  the parser. `config` supports the following properties:\n  * `args` {string\\[]} array of argument strings. **Default:** `process.argv`\n    with `execPath` and `filename` removed.\n  * `options` {Object} Used to describe arguments known to the parser.\n    Keys of `options` are the long names of options and values are an\n    {Object} accepting the following properties:\n    * `type` {string} Type of argument, which must be either `boolean` or `string`.\n    * `multiple` {boolean} Whether this option can be provided multiple\n      times. If `true`, all values will be collected in an array. If\n      `false`, values for the option are last-wins. **Default:** `false`.\n    * `short` {string} A single character alias for the option.\n    * `default` {string | boolean | string\\[] | boolean\\[]} The default option\n      value when it is not set by args. It must be of the same type as the\n      the `type` property. When `multiple` is `true`, it must be an array.\n  * `strict` {boolean} Should an error be thrown when unknown arguments\n    are encountered, or when arguments are passed that do not match the\n    `type` configured in `options`.\n    **Default:** `true`.\n  * `allowPositionals` {boolean} Whether this command accepts positional\n    arguments.\n    **Default:** `false` if `strict` is `true`, otherwise `true`.\n  * `tokens` {boolean} Return the parsed tokens. This is useful for extending\n    the built-in behavior, from adding additional checks through to reprocessing\n    the tokens in different ways.\n    **Default:** `false`.\n\n* Returns: {Object} The parsed command line arguments:\n  * `values` {Object} A mapping of parsed option names with their {string}\n    or {boolean} values.\n  * `positionals` {string\\[]} Positional arguments.\n  * `tokens` {Object\\[] | undefined} See [parseArgs tokens](#parseargs-tokens)\n    section. Only returned if `config` includes `tokens: true`.\n\nProvides a higher level API for command-line argument parsing than interacting\nwith `process.argv` directly. Takes a specification for the expected arguments\nand returns a structured object with the parsed options and positionals.\n\n```mjs\nimport { parseArgs } from 'node:util';\nconst args = ['-f', '--bar', 'b'];\nconst options = {\n  foo: {\n    type: 'boolean',\n    short: 'f'\n  },\n  bar: {\n    type: 'string'\n  }\n};\nconst {\n  values,\n  positionals\n} = parseArgs({ args, options });\nconsole.log(values, positionals);\n// Prints: [Object: null prototype] { foo: true, bar: 'b' } []\n```\n\n```cjs\nconst { parseArgs } = require('node:util');\nconst args = ['-f', '--bar', 'b'];\nconst options = {\n  foo: {\n    type: 'boolean',\n    short: 'f'\n  },\n  bar: {\n    type: 'string'\n  }\n};\nconst {\n  values,\n  positionals\n} = parseArgs({ args, options });\nconsole.log(values, positionals);\n// Prints: [Object: null prototype] { foo: true, bar: 'b' } []\n```\n\n`util.parseArgs` is experimental and behavior may change. Join the\nconversation in [pkgjs/parseargs][] to contribute to the design.\n\n### `parseArgs` `tokens`\n\nDetailed parse information is available for adding custom behaviours by\nspecifying `tokens: true` in the configuration.\nThe returned tokens have properties describing:\n\n* all tokens\n  * `kind` {string} One of 'option', 'positional', or 'option-terminator'.\n  * `index` {number} Index of element in `args` containing token. So the\n    source argument for a token is `args[token.index]`.\n* option tokens\n  * `name` {string} Long name of option.\n  * `rawName` {string} How option used in args, like `-f` of `--foo`.\n  * `value` {string | undefined} Option value specified in args.\n    Undefined for boolean options.\n  * `inlineValue` {boolean | undefined} Whether option value specified inline,\n    like `--foo=bar`.\n* positional tokens\n  * `value` {string} The value of the positional argument in args (i.e. `args[index]`).\n* option-terminator token\n\nThe returned tokens are in the order encountered in the input args. Options\nthat appear more than once in args produce a token for each use. Short option\ngroups like `-xy` expand to a token for each option. So `-xxx` produces\nthree tokens.\n\nFor example to use the returned tokens to add support for a negated option\nlike `--no-color`, the tokens can be reprocessed to change the value stored\nfor the negated option.\n\n```mjs\nimport { parseArgs } from 'node:util';\n\nconst options = {\n  'color': { type: 'boolean' },\n  'no-color': { type: 'boolean' },\n  'logfile': { type: 'string' },\n  'no-logfile': { type: 'boolean' },\n};\nconst { values, tokens } = parseArgs({ options, tokens: true });\n\n// Reprocess the option tokens and overwrite the returned values.\ntokens\n  .filter((token) => token.kind === 'option')\n  .forEach((token) => {\n    if (token.name.startsWith('no-')) {\n      // Store foo:false for --no-foo\n      const positiveName = token.name.slice(3);\n      values[positiveName] = false;\n      delete values[token.name];\n    } else {\n      // Resave value so last one wins if both --foo and --no-foo.\n      values[token.name] = token.value ?? true;\n    }\n  });\n\nconst color = values.color;\nconst logfile = values.logfile ?? 'default.log';\n\nconsole.log({ logfile, color });\n```\n\n```cjs\nconst { parseArgs } = require('node:util');\n\nconst options = {\n  'color': { type: 'boolean' },\n  'no-color': { type: 'boolean' },\n  'logfile': { type: 'string' },\n  'no-logfile': { type: 'boolean' },\n};\nconst { values, tokens } = parseArgs({ options, tokens: true });\n\n// Reprocess the option tokens and overwrite the returned values.\ntokens\n  .filter((token) => token.kind === 'option')\n  .forEach((token) => {\n    if (token.name.startsWith('no-')) {\n      // Store foo:false for --no-foo\n      const positiveName = token.name.slice(3);\n      values[positiveName] = false;\n      delete values[token.name];\n    } else {\n      // Resave value so last one wins if both --foo and --no-foo.\n      values[token.name] = token.value ?? true;\n    }\n  });\n\nconst color = values.color;\nconst logfile = values.logfile ?? 'default.log';\n\nconsole.log({ logfile, color });\n```\n\nExample usage showing negated options, and when an option is used\nmultiple ways then last one wins.\n\n```console\n$ node negate.js\n{ logfile: 'default.log', color: undefined }\n$ node negate.js --no-logfile --no-color\n{ logfile: false, color: false }\n$ node negate.js --logfile=test.log --color\n{ logfile: 'test.log', color: true }\n$ node negate.js --no-logfile --logfile=test.log --color --no-color\n{ logfile: 'test.log', color: false }\n```\n\n-----\n\n<!-- omit in toc -->\n## Table of Contents\n- [`util.parseArgs([config])`](#utilparseargsconfig)\n- [Scope](#scope)\n- [Version Matchups](#version-matchups)\n- [🚀 Getting Started](#-getting-started)\n- [🙌 Contributing](#-contributing)\n- [💡 `process.mainArgs` Proposal](#-processmainargs-proposal)\n  - [Implementation:](#implementation)\n- [📃 Examples](#-examples)\n- [F.A.Qs](#faqs)\n- [Links & Resources](#links--resources)\n\n-----\n\n## Scope\n\nIt is already possible to build great arg parsing modules on top of what Node.js provides; the prickly API is abstracted away by these modules. Thus, process.parseArgs() is not necessarily intended for library authors; it is intended for developers of simple CLI tools, ad-hoc scripts, deployed Node.js applications, and learning materials.\n\nIt is exceedingly difficult to provide an API which would both be friendly to these Node.js users while being extensible enough for libraries to build upon. We chose to prioritize these use cases because these are currently not well-served by Node.js' API.\n\n----\n\n## Version Matchups\n\n| Node.js | @pkgjs/parseArgs |\n| -- | -- |\n| [v18.3.0](https://nodejs.org/docs/latest-v18.x/api/util.html#utilparseargsconfig) | [v0.9.1](https://github.com/pkgjs/parseargs/tree/v0.9.1#utilparseargsconfig) |\n| [v16.17.0](https://nodejs.org/dist/latest-v16.x/docs/api/util.html#utilparseargsconfig), [v18.7.0](https://nodejs.org/docs/latest-v18.x/api/util.html#utilparseargsconfig) | [0.10.0](https://github.com/pkgjs/parseargs/tree/v0.10.0#utilparseargsconfig) |\n\n----\n\n## 🚀 Getting Started\n\n1. **Install dependencies.**\n\n   ```bash\n   npm install\n   ```\n\n2. **Open the index.js file and start editing!**\n\n3. **Test your code by calling parseArgs through our test file**\n\n   ```bash\n   npm test\n   ```\n\n----\n\n## 🙌 Contributing\n\nAny person who wants to contribute to the initiative is welcome! Please first read the [Contributing Guide](CONTRIBUTING.md)\n\nAdditionally, reading the [`Examples w/ Output`](#-examples-w-output) section of this document will be the best way to familiarize yourself with the target expected behavior for parseArgs() once it is fully implemented.\n\nThis package was implemented using [tape](https://www.npmjs.com/package/tape) as its test harness.\n\n----\n\n## 💡 `process.mainArgs` Proposal\n\n> Note: This can be moved forward independently of the `util.parseArgs()` proposal/work.\n\n### Implementation:\n\n```javascript\nprocess.mainArgs = process.argv.slice(process._exec ? 1 : 2)\n```\n\n----\n\n## 📃 Examples\n\n```js\nconst { parseArgs } = require('@pkgjs/parseargs');\n```\n\n```js\nconst { parseArgs } = require('@pkgjs/parseargs');\n// specify the options that may be used\nconst options = {\n  foo: { type: 'string'},\n  bar: { type: 'boolean' },\n};\nconst args = ['--foo=a', '--bar'];\nconst { values, positionals } = parseArgs({ args, options });\n// values = { foo: 'a', bar: true }\n// positionals = []\n```\n\n```js\nconst { parseArgs } = require('@pkgjs/parseargs');\n// type:string & multiple\nconst options = {\n  foo: {\n    type: 'string',\n    multiple: true,\n  },\n};\nconst args = ['--foo=a', '--foo', 'b'];\nconst { values, positionals } = parseArgs({ args, options });\n// values = { foo: [ 'a', 'b' ] }\n// positionals = []\n```\n\n```js\nconst { parseArgs } = require('@pkgjs/parseargs');\n// shorts\nconst options = {\n  foo: {\n    short: 'f',\n    type: 'boolean'\n  },\n};\nconst args = ['-f', 'b'];\nconst { values, positionals } = parseArgs({ args, options, allowPositionals: true });\n// values = { foo: true }\n// positionals = ['b']\n```\n\n```js\nconst { parseArgs } = require('@pkgjs/parseargs');\n// unconfigured\nconst options = {};\nconst args = ['-f', '--foo=a', '--bar', 'b'];\nconst { values, positionals } = parseArgs({ strict: false, args, options, allowPositionals: true });\n// values = { f: true, foo: 'a', bar: true }\n// positionals = ['b']\n```\n\n----\n\n## F.A.Qs\n\n- Is `cmd --foo=bar baz` the same as `cmd baz --foo=bar`?\n  - yes\n- Does the parser execute a function?\n  - no\n- Does the parser execute one of several functions, depending on input?\n  - no\n- Can subcommands take options that are distinct from the main command?\n  - no\n- Does it output generated help when no options match?\n  - no\n- Does it generated short usage?  Like: `usage: ls [-ABCFGHLOPRSTUWabcdefghiklmnopqrstuwx1] [file ...]`\n  - no (no usage/help at all)\n- Does the user provide the long usage text?  For each option?  For the whole command?\n  - no\n- Do subcommands (if implemented) have their own usage output?\n  - no\n- Does usage print if the user runs `cmd --help`?\n  - no\n- Does it set `process.exitCode`?\n  - no\n- Does usage print to stderr or stdout?\n  - N/A\n- Does it check types?  (Say, specify that an option is a boolean, number, etc.)\n  - no\n- Can an option have more than one type?  (string or false, for example)\n  - no\n- Can the user define a type?  (Say, `type: path` to call `path.resolve()` on the argument.)\n  - no\n- Does a `--foo=0o22` mean 0, 22, 18, or \"0o22\"?\n  - `\"0o22\"`\n- Does it coerce types?\n  - no\n- Does `--no-foo` coerce to `--foo=false`?  For all options?  Only boolean options?\n  - no, it sets `{values:{'no-foo': true}}`\n- Is `--foo` the same as `--foo=true`?  Only for known booleans?  Only at the end?\n  - no, they are not the same. There is no special handling of `true` as a value so it is just another string.\n- Does it read environment variables?  Ie, is `FOO=1 cmd` the same as `cmd --foo=1`?\n  - no\n- Do unknown arguments raise an error?  Are they parsed?  Are they treated as positional arguments?\n  - no, they are parsed, not treated as positionals\n- Does `--` signal the end of options?\n  - yes\n- Is `--` included as a positional?\n  - no\n- Is `program -- foo` the same as `program foo`?\n  - yes, both store `{positionals:['foo']}`\n- Does the API specify whether a `--` was present/relevant?\n  - no\n- Is `-bar` the same as `--bar`?\n  - no, `-bar` is a short option or options, with expansion logic that follows the\n    [Utility Syntax Guidelines in POSIX.1-2017](https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html). `-bar` expands to `-b`, `-a`, `-r`.\n- Is `---foo` the same as `--foo`?\n  - no\n  - the first is a long option named `'-foo'`\n  - the second is a long option named `'foo'`\n- Is `-` a positional? ie, `bash some-test.sh | tap -`\n  - yes\n\n## Links & Resources\n\n* [Initial Tooling Issue](https://github.com/nodejs/tooling/issues/19)\n* [Initial Proposal](https://github.com/nodejs/node/pull/35015)\n* [parseArgs Proposal](https://github.com/nodejs/node/pull/42675)\n\n[coverage-image]: https://img.shields.io/nycrc/pkgjs/parseargs\n[coverage-url]: https://github.com/pkgjs/parseargs/blob/main/.nycrc\n[pkgjs/parseargs]: https://github.com/pkgjs/parseargs",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{7d/32/26634affcae2e0d863fef45428319f1a30b8b9c76ddd57c0aa039ce7a49a67da7acf2f494913e25777efc7c0da5fa04d610c8d9ed65d204b5f2bf702605a → 89/47/b83b934ee2ba448c8e84df4bfaaa12e6f3c0f258ee63c9285f9f7cbc8d6a493fecad677a73a8414a120b8aa6860ce6a2d2157f60f965777eb7aeafd69eed}

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

package/npm-cache/_cacache/content-v2/sha512/{ee/b8/18963a5fc0a75915f7060c1ee271da4372d49f7540e7054c23c6d05e09b126f0fcc2f4353a9a8081e5110f9b0bf163dbfc87bf02b21b5147bab7e8d11454 → 8b/de/e0a632adb89d4f2c4901f785edd80fc71d933088ff43a5b2f78a8f18931090cd3541d6134ff1ebf91f323a5a4851a1f11d73825748d2a2a2180f7ee44525}

@@ -3929,7 +3929,7 @@
   "dist-tags": {
     "latest": "7.0.2"
   },
-  "_rev": "76-bcf0a4181b679ab5",
+  "_rev": "77-7d18c2301ada9a3f",
   "_id": "zip-stream",
   "readme": "# ZipStream\n\nzip-stream is a streaming zip archive generator based on the `ZipArchiveOutputStream` prototype found in the [compress-commons](https://www.npmjs.org/package/compress-commons) project.\n\nIt was originally created to be a successor to [zipstream](https://npmjs.org/package/zipstream).\n\nVisit the [API documentation](http://archiverjs.com/zip-stream) for a list of all methods available.\n\n### Install\n\n```bash\nnpm install zip-stream --save\n```\n\nYou can also use `npm install https://github.com/archiverjs/node-zip-stream/archive/master.tar.gz` to test upcoming versions.\n\n### Usage\n\nThis module is meant to be wrapped internally by other modules and therefore lacks any queue management. This means you have to wait until the previous entry has been fully consumed to add another. Nested callbacks should be used to add multiple entries. There are modules like [async](https://npmjs.org/package/async) that ease the so called \"callback hell\".\n\nIf you want a module that handles entry queueing and much more, you should check out [archiver](https://npmjs.org/package/archiver) which uses this module internally.\n\n```js\nimport { ZipStream } from \"zip-stream\":\nconst archive = new ZipStream(); // OR new ZipStream(options)\n\narchive.on(\"error\", function (err) {\n  throw err;\n});\n\n// pipe archive where you want it (ie fs, http, etc)\n// listen to the destination's end, close, or finish event\n\narchive.entry(\"string contents\", { name: \"string.txt\" }, function (err, entry) {\n  if (err) throw err;\n  archive.entry(null, { name: \"directory/\" }, function (err, entry) {\n    if (err) throw err;\n    archive.finish();\n  });\n});\n```\n\n## Credits\n\nConcept inspired by Antoine van Wel's [zipstream](https://npmjs.org/package/zipstream) module, which is no longer being updated.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{ff/52/9504941be5ef3f4cb23f401d85d1b47701b069a4a8b13cc4c412ffadcf376f43d4a30231bc0db0c497fd4254d9e3161a5c99069c9e5f4e58d4dfe5f224b4 → 8c/3c/8e517d39410f5d47a43553363151980a2dd88a33b02d5914a50696eb653d63b5be7e137ebc11a555ac519af1847046857e04f9fa627d7a49bf88fcfb5082}

@@ -137,7 +137,7 @@
   "dist-tags": {
     "latest": "8.0.2"
   },
-  "_rev": "116-cfa07a8aeec2780c",
+  "_rev": "118-461ce74394b1d983",
   "_id": "@isaacs/cliui",
   "readme": "# @isaacs/cliui\n\nTemporary fork of [cliui](http://npm.im/cliui).\n\n![ci](https://github.com/yargs/cliui/workflows/ci/badge.svg)\n[![NPM version](https://img.shields.io/npm/v/cliui.svg)](https://www.npmjs.com/package/cliui)\n[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)\n![nycrc config on GitHub](https://img.shields.io/nycrc/yargs/cliui)\n\neasily create complex multi-column command-line-interfaces.\n\n## Example\n\n```js\nconst ui = require('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: \"the file to load.\" +\n      chalk.green(\"(if this description is long it wraps).\")\n    ,\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\nAs of `v7` `cliui` supports [Deno](https://github.com/denoland/deno) and\n[ESM](https://nodejs.org/api/esm.html#esm_ecmascript_modules):\n\n```typescript\nimport cliui from \"https://deno.land/x/cliui/deno.ts\";\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('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/{7e/3a/38c313497c62a26ede33347321681fb687eb90e6ab6b63118fc1a542706a16eda11b83664f645eea376cc5520d2306251e8776707af9f32b801e158dd555 → 8f/44/d78072aa48e7f76b44cd60c05a8095b0c0287c6380c825470fc15b09e0c100e62a611165a9fbd65c240557692ac8ff64f755c9a7f560c3e5d971d8a5c218}

@@ -11527,7 +11527,7 @@
     "gamma": "1.0.0-gamma.8",
     "rc": "1.0.0-rc.10"
   },
-  "_rev": "86-28d70967e7994a8b",
+  "_rev": "87-0727d5a4b0cc6529",
   "_id": "@aws-sdk/abort-controller",
   "readme": "# @aws-sdk/abort-controller\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/abort-controller/latest.svg)](https://www.npmjs.com/package/@aws-sdk/abort-controller)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/abort-controller.svg)](https://www.npmjs.com/package/@aws-sdk/abort-controller)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{58/be/732dbf9ace2b6cd3192371858906b60ec12d8b25b9fa8867a1d06795e374733bcbd6963901de03bb7fb1448d2a2df898b124fa6a79f332815b9793bd7159 → 91/2b/e03f665db7642f482d421e7c0a539f9ee32cdaffa194b5acc405eb504cd8a4e3c9dc6d5fa6abe8464e8aedebaf66f3ff30b6f0ff07bd7d90d96cf92a1f9a}

@@ -46525,7 +46525,7 @@
     "gamma": "1.0.0-gamma.9",
     "rc": "3.5.1-rc.0"
   },
-  "_rev": "93-83b761cb6ed12905",
+  "_rev": "94-166329975e6718f9",
   "_id": "@aws-sdk/credential-provider-node",
   "readme": "# @aws-sdk/credential-provider-node\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/credential-provider-node/latest.svg)](https://www.npmjs.com/package/@aws-sdk/credential-provider-node)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/credential-provider-node.svg)](https://www.npmjs.com/package/@aws-sdk/credential-provider-node)\n\n## AWS Credential Provider for Node.JS\n\nThis module provides a factory function, `defaultProvider`, that will attempt to\nsource AWS credentials from a Node.JS environment. It will attempt to find\ncredentials from the following sources (listed in order of precedence):\n\n- Environment variables exposed via `process.env`\n- SSO credentials from token cache\n- Web identity token credentials\n- Shared credentials and config ini files\n- The EC2/ECS Instance Metadata Service\n\nThe default credential provider will invoke one provider at a time and only\ncontinue to the next if no credentials have been located. For example, if the\nprocess finds values defined via the `AWS_ACCESS_KEY_ID` and\n`AWS_SECRET_ACCESS_KEY` environment variables, the files at `~/.aws/credentials`\nand `~/.aws/config` will not be read, nor will any messages be sent to the\nInstance Metadata Service.\n\nIf invalid configuration is encountered (such as a profile in\n`~/.aws/credentials` specifying as its `source_profile` the name of a profile\nthat does not exist), then the chained provider will be rejected with an error\nand will not invoke the next provider in the list.\n\n_IMPORTANT_: if you intend to acquire credentials using EKS \n[IAM Roles for Service Accounts](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html), \nthen you must explicitly specify a value for `roleAssumerWithWebIdentity`. There is a\ndefault function available in `@aws-sdk/client-sts` package. An example of using\nthis:\n\n```js\nconst { getDefaultRoleAssumerWithWebIdentity } = require(\"@aws-sdk/client-sts\");\nconst { defaultProvider } = require(\"@aws-sdk/credential-provider-node\");\nconst { S3Client, GetObjectCommand } = require(\"@aws-sdk/client-s3\");\n\nconst provider = defaultProvider({\n  roleAssumerWithWebIdentity: getDefaultRoleAssumerWithWebIdentity({\n    // You must explicitly pass a region if you are not using us-east-1\n    region: \"eu-west-1\"\n  }),\n});\n\nconst client = new S3Client({ credentialDefaultProvider: provider });\n```\n\n_IMPORTANT_: We provide a wrapper of this provider in `@aws-sdk/credential-providers`\npackage to save you from importing `getDefaultRoleAssumerWithWebIdentity()` or\n`getDefaultRoleAssume()` from STS package. Similarly, you can do:\n\n```js\nconst { fromNodeProviderChain } = require(\"@aws-sdk/credential-providers\");\n\nconst credentials = fromNodeProviderChain();\n\nconst client = new S3Client({ credentials });\n```\n\n## Supported configuration\n\nYou may customize how credentials are resolved by providing an options hash to\nthe `defaultProvider` factory function. The following options are\nsupported:\n\n- `profile` - The configuration profile to use. If not specified, the provider\n  will use the value in the `AWS_PROFILE` environment variable or a default of\n  `default`.\n- `filepath` - The path to the shared credentials file. If not specified, the\n  provider will use the value in the `AWS_SHARED_CREDENTIALS_FILE` environment\n  variable or a default of `~/.aws/credentials`.\n- `configFilepath` - The path to the shared config file. If not specified, the\n  provider will use the value in the `AWS_CONFIG_FILE` environment variable or a\n  default of `~/.aws/config`.\n- `mfaCodeProvider` - A function that returns a a promise fulfilled with an\n  MFA token code for the provided MFA Serial code. If a profile requires an MFA\n  code and `mfaCodeProvider` is not a valid function, the credential provider\n  promise will be rejected.\n- `roleAssumer` - A function that assumes a role and returns a promise\n  fulfilled with credentials for the assumed role. If not specified, no role\n  will be assumed, and an error will be thrown.\n- `roleArn` - ARN to assume. If not specified, the provider will use the value\n  in the `AWS_ROLE_ARN` environment variable.\n- `webIdentityTokenFile` - File location of where the `OIDC` token is stored.\n  If not specified, the provider will use the value in the `AWS_WEB_IDENTITY_TOKEN_FILE`\n  environment variable.\n- `roleAssumerWithWebIdentity` - A function that assumes a role with web identity and\n  returns a promise fulfilled with credentials for the assumed role.\n- `timeout` - The connection timeout (in milliseconds) to apply to any remote\n  requests. If not specified, a default value of `1000` (one second) is used.\n- `maxRetries` - The maximum number of times any HTTP connections should be\n  retried. If not specified, a default value of `0` will be used.\n\n## Related packages:\n\n- [AWS Credential Provider for Node.JS - Environment Variables](../credential-provider-env)\n- [AWS Credential Provider for Node.JS - SSO](../credential-provider-sso)\n- [AWS Credential Provider for Node.JS - Web Identity](../credential-provider-web-identity)\n- [AWS Credential Provider for Node.JS - Shared Configuration Files](../credential-provider-ini)\n- [AWS Credential Provider for Node.JS - Instance and Container Metadata](../credential-provider-imds)\n- [AWS Shared Configuration File Loader](../shared-ini-file-loader)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{0c/05/d778195c17a5d1350e318ee441fbd1e74fa7faa37dec7364e9fe3e7a4398f565d54513dc82e792cfedf76d62f1291171499c096b5ba8c7522af31abdb6cf → 92/38/6803c0331cf2176b732cefaa0511fd489bd5095608cbf3806f1a5ba0bb027a7e3defade9efa90c8d5634c3ced015d409816d22e4ba451746d0880390bc12}

@@ -1767,7 +1767,7 @@
     "latest": "1.0.0",
     "next": "1.0.0-RC9"
   },
-  "_rev": "145-18d40ec50f63641b",
+  "_rev": "146-da7bc9cec14751a1",
   "_id": "buffer-crc32",
   "readme": "# buffer-crc32\n\n[![NPM Version](https://img.shields.io/npm/v/buffer-crc32.svg)](https://npmjs.org/package/buffer-crc32)\n[![Build Status](https://github.com/brianloveswords/buffer-crc32/actions/workflows/ci.yml/badge.svg)](https://github.com/brianloveswords/buffer-crc32/actions/workflows/ci.yml)\n\ncrc32 that works with binary data and fancy character sets, outputs\nbuffer, signed or unsigned data and has tests.\n\nDerived from the sample CRC implementation in the PNG specification: http://www.w3.org/TR/PNG/#D-CRCAppendix\n\nThis package requires Node 8+ to work.\n\n# install\n\n```\nnpm install buffer-crc32\n```\n\n# example\n\n```js\nconst crc32 = require('buffer-crc32');\n// works with buffers\nconst buf = Buffer([0x00, 0x73, 0x75, 0x70, 0x20, 0x62, 0x72, 0x6f, 0x00]);\ncrc32(buf); // -> <Buffer 94 5a ab 4a>\n\n// has convenience methods for getting signed or unsigned ints\ncrc32.signed(buf); // -> -1805997238\ncrc32.unsigned(buf); // -> 2488970058\n\n// will cast to buffer if given a string, so you can\n// directly use foreign characters safely\ncrc32('自動販売機'); // -> <Buffer cb 03 1a c5>\n\n// and works in append mode too\nconst partialCrc = crc32('hey');\nconst partialCrc = crc32(' ', partialCrc);\nconst partialCrc = crc32('sup', partialCrc);\nconst partialCrc = crc32(' ', partialCrc);\nconst finalCrc = crc32('bros', partialCrc); // -> <Buffer 47 fa 55 70>\n```\n\n# tests\n\nThis was tested against the output of zlib's crc32 method. You can run\nthe tests with`npm test` (requires tap)\n\n# see also\n\nhttps://github.com/alexgorbatchev/node-crc, `crc.buffer.crc32` also\nsupports buffer inputs and return unsigned ints (thanks @tjholowaychuk).\n\n# license\n\nMIT/X11",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{42/24/ce89862621b499ffc310bddfdb9ff3d3cb93b80880b6f2ef56f988f6b83ece98f0de9bb502563b41ae024e1a42d590493d1ff4b1b57be4bc026593f4a2a7 → 92/97/305ab860295dcde895afb59d7c253fe1feca5e2a4d12741bb6dea8937cdeae073ce3b7cd5f6cb7957e6fcca3393f4300239559bf2db99ba33c57ea034ba4}

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

package/npm-cache/_cacache/content-v2/sha512/{88/38/f5951dab15402003c4e5d12163b8fc970be51e62eed5fde55cf1adf4b8bd6703e62fc84cdda2a563b5367cde13b8f2e9b6993dfa09475211586a0fbd8e7e → 95/c6/233cb1591adf8f95bba988b6c023a086f8d4d7a0792730387d1c37435675191f8759357229274f425d992a8ebd228e9c7eb21da42d7f9123ff9639beca32}

@@ -529310,10 +529310,358 @@
       },
       "_hasShrinkwrap": false,
       "contributors": []
+    },
+    "5.9.0-dev.20250318": {
+      "name": "typescript",
+      "version": "5.9.0-dev.20250318",
+      "keywords": [
+        "TypeScript",
+        "Microsoft",
+        "compiler",
+        "language",
+        "javascript"
+      ],
+      "author": {
+        "name": "Microsoft Corp."
+      },
+      "license": "Apache-2.0",
+      "_id": "typescript@5.9.0-dev.20250318",
+      "maintainers": [
+        {
+          "name": "typescript-bot",
+          "email": "typescript@microsoft.com"
+        },
+        {
+          "name": "weswigham",
+          "email": "wwigham@gmail.com"
+        },
+        {
+          "name": "sanders_n",
+          "email": "nathan@shively-sanders.com"
+        },
+        {
+          "name": "andrewbranch",
+          "email": "andrew@wheream.io"
+        },
+        {
+          "name": "minestarks",
+          "email": "mineyalc@microsoft.com"
+        },
+        {
+          "name": "rbuckton",
+          "email": "rbuckton@chronicles.org"
+        },
+        {
+          "name": "sheetalkamat",
+          "email": "shkamat@microsoft.com"
+        },
+        {
+          "name": "typescript-deploys",
+          "email": "typescript-design@microsoft.com"
+        }
+      ],
+      "homepage": "https://www.typescriptlang.org/",
+      "bugs": {
+        "url": "https://github.com/microsoft/TypeScript/issues"
+      },
+      "bin": {
+        "tsc": "bin/tsc",
+        "tsserver": "bin/tsserver"
+      },
+      "dist": {
+        "shasum": "77e25bbbbb403da9afeb49e72775fd10b4349fe0",
+        "tarball": "https://verdaccio.mrsdev.ru/typescript/-/typescript-5.9.0-dev.20250318.tgz",
+        "fileCount": 130,
+        "integrity": "sha512-PargTTEKzWpTiNuMV24CBaPCvXjRnpLNwCVVAjQjWBABOazwuYXJ3nXp3VCBavv9IJo2riKWWG7TgLOthATwSQ==",
+        "signatures": [
+          {
+            "sig": "MEYCIQD/BJv2FLUq2zrCnAUTRBzP1IxdNdUKPogL/8yTV9UV6QIhAO+lZEbCHDbjzmjP7nQXeTHWCy+2qpRSJDx6KJJKObEy",
+            "keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"
+          }
+        ],
+        "unpackedSize": 22874027
+      },
+      "main": "./lib/typescript.js",
+      "volta": {
+        "npm": "8.19.4",
+        "node": "20.1.0"
+      },
+      "browser": {
+        "fs": false,
+        "os": false,
+        "path": false,
+        "buffer": false,
+        "crypto": false,
+        "inspector": false,
+        "perf_hooks": false,
+        "source-map-support": false
+      },
+      "engines": {
+        "node": ">=14.17"
+      },
+      "gitHead": "ee3dd7264b23e58bbad86d08a475cac78f330abf",
+      "scripts": {
+        "gulp": "hereby",
+        "knip": "hereby knip",
+        "lint": "hereby lint",
+        "test": "hereby runtests-parallel --light=false",
+        "build": "npm run build:compiler && npm run build:tests",
+        "clean": "hereby clean",
+        "format": "dprint fmt",
+        "build:tests": "hereby tests",
+        "setup-hooks": "node scripts/link-hooks.mjs",
+        "build:compiler": "hereby local",
+        "test:eslint-rules": "hereby run-eslint-rules-tests",
+        "build:tests:notypecheck": "hereby tests --no-typecheck"
+      },
+      "typings": "./lib/typescript.d.ts",
+      "_npmUser": {
+        "name": "typescript-bot",
+        "email": "typescript@microsoft.com"
+      },
+      "overrides": {
+        "typescript@*": "$typescript"
+      },
+      "repository": {
+        "url": "git+https://github.com/microsoft/TypeScript.git",
+        "type": "git"
+      },
+      "_npmVersion": "8.19.4",
+      "description": "TypeScript is a language for application scale JavaScript development",
+      "directories": {},
+      "_nodeVersion": "22.14.0",
+      "_hasShrinkwrap": false,
+      "packageManager": "npm@8.19.4",
+      "readmeFilename": "README.md",
+      "devDependencies": {
+        "c8": "^10.1.3",
+        "ms": "^2.1.3",
+        "chai": "^4.5.0",
+        "diff": "^7.0.0",
+        "glob": "^10.4.5",
+        "knip": "^5.44.4",
+        "mocha": "^10.8.2",
+        "tslib": "^2.8.1",
+        "which": "^3.0.1",
+        "dprint": "^0.49.0",
+        "eslint": "^9.20.1",
+        "hereby": "^1.10.0",
+        "esbuild": "^0.25.0",
+        "globals": "^15.15.0",
+        "chokidar": "^4.0.3",
+        "minimist": "^1.2.8",
+        "@types/ms": "^0.7.34",
+        "@eslint/js": "^9.20.0",
+        "picocolors": "^1.1.1",
+        "playwright": "^1.50.1",
+        "typescript": "^5.7.3",
+        "@types/chai": "^4.3.20",
+        "@types/diff": "^7.0.1",
+        "@types/node": "latest",
+        "@types/mocha": "^10.0.10",
+        "@types/which": "^3.0.4",
+        "jsonc-parser": "^3.3.1",
+        "@octokit/rest": "^21.1.1",
+        "@types/minimist": "^1.2.5",
+        "fast-xml-parser": "^4.5.2",
+        "@dprint/formatter": "^0.4.1",
+        "@esfx/canceltoken": "^1.0.0",
+        "typescript-eslint": "^8.24.1",
+        "@dprint/typescript": "0.93.4",
+        "source-map-support": "^0.5.21",
+        "eslint-plugin-regexp": "^2.7.0",
+        "azure-devops-node-api": "^14.1.0",
+        "@typescript-eslint/utils": "^8.24.1",
+        "@types/source-map-support": "^0.5.10",
+        "monocart-coverage-reports": "^2.12.1",
+        "@typescript-eslint/type-utils": "^8.24.1",
+        "@typescript-eslint/rule-tester": "^8.24.1",
+        "mocha-fivemat-progress-reporter": "^0.1.0",
+        "eslint-formatter-autolinkable-stylish": "^1.4.0"
+      },
+      "_npmOperationalInternal": {
+        "tmp": "tmp/typescript_5.9.0-dev.20250318_1742282095283_0.05236136688413984",
+        "host": "s3://npm-registry-packages-npm-production"
+      },
+      "contributors": []
+    },
+    "5.9.0-dev.20250319": {
+      "name": "typescript",
+      "author": {
+        "name": "Microsoft Corp."
+      },
+      "homepage": "https://www.typescriptlang.org/",
+      "version": "5.9.0-dev.20250319",
+      "license": "Apache-2.0",
+      "description": "TypeScript is a language for application scale JavaScript development",
+      "keywords": [
+        "TypeScript",
+        "Microsoft",
+        "compiler",
+        "language",
+        "javascript"
+      ],
+      "bugs": {
+        "url": "https://github.com/microsoft/TypeScript/issues"
+      },
+      "repository": {
+        "type": "git",
+        "url": "git+https://github.com/microsoft/TypeScript.git"
+      },
+      "main": "./lib/typescript.js",
+      "typings": "./lib/typescript.d.ts",
+      "bin": {
+        "tsc": "bin/tsc",
+        "tsserver": "bin/tsserver"
+      },
+      "engines": {
+        "node": ">=14.17"
+      },
+      "devDependencies": {
+        "@dprint/formatter": "^0.4.1",
+        "@dprint/typescript": "0.93.4",
+        "@esfx/canceltoken": "^1.0.0",
+        "@eslint/js": "^9.20.0",
+        "@octokit/rest": "^21.1.1",
+        "@types/chai": "^4.3.20",
+        "@types/diff": "^7.0.1",
+        "@types/minimist": "^1.2.5",
+        "@types/mocha": "^10.0.10",
+        "@types/ms": "^0.7.34",
+        "@types/node": "latest",
+        "@types/source-map-support": "^0.5.10",
+        "@types/which": "^3.0.4",
+        "@typescript-eslint/rule-tester": "^8.24.1",
+        "@typescript-eslint/type-utils": "^8.24.1",
+        "@typescript-eslint/utils": "^8.24.1",
+        "azure-devops-node-api": "^14.1.0",
+        "c8": "^10.1.3",
+        "chai": "^4.5.0",
+        "chokidar": "^4.0.3",
+        "diff": "^7.0.0",
+        "dprint": "^0.49.0",
+        "esbuild": "^0.25.0",
+        "eslint": "^9.20.1",
+        "eslint-formatter-autolinkable-stylish": "^1.4.0",
+        "eslint-plugin-regexp": "^2.7.0",
+        "fast-xml-parser": "^4.5.2",
+        "glob": "^10.4.5",
+        "globals": "^15.15.0",
+        "hereby": "^1.10.0",
+        "jsonc-parser": "^3.3.1",
+        "knip": "^5.44.4",
+        "minimist": "^1.2.8",
+        "mocha": "^10.8.2",
+        "mocha-fivemat-progress-reporter": "^0.1.0",
+        "monocart-coverage-reports": "^2.12.1",
+        "ms": "^2.1.3",
+        "picocolors": "^1.1.1",
+        "playwright": "^1.50.1",
+        "source-map-support": "^0.5.21",
+        "tslib": "^2.8.1",
+        "typescript": "^5.7.3",
+        "typescript-eslint": "^8.24.1",
+        "which": "^3.0.1"
+      },
+      "overrides": {
+        "typescript@*": "$typescript"
+      },
+      "scripts": {
+        "test": "hereby runtests-parallel --light=false",
+        "test:eslint-rules": "hereby run-eslint-rules-tests",
+        "build": "npm run build:compiler && npm run build:tests",
+        "build:compiler": "hereby local",
+        "build:tests": "hereby tests",
+        "build:tests:notypecheck": "hereby tests --no-typecheck",
+        "clean": "hereby clean",
+        "gulp": "hereby",
+        "lint": "hereby lint",
+        "knip": "hereby knip",
+        "format": "dprint fmt",
+        "setup-hooks": "node scripts/link-hooks.mjs"
+      },
+      "browser": {
+        "fs": false,
+        "os": false,
+        "path": false,
+        "crypto": false,
+        "buffer": false,
+        "source-map-support": false,
+        "inspector": false,
+        "perf_hooks": false
+      },
+      "packageManager": "npm@8.19.4",
+      "volta": {
+        "node": "20.1.0",
+        "npm": "8.19.4"
+      },
+      "gitHead": "ee3dd7264b23e58bbad86d08a475cac78f330abf",
+      "readmeFilename": "README.md",
+      "_id": "typescript@5.9.0-dev.20250319",
+      "_nodeVersion": "22.14.0",
+      "_npmVersion": "8.19.4",
+      "dist": {
+        "integrity": "sha512-C6kzsa+mmHXyelLcfTYaINXz01XaznLJKoZKKfcwYa4rDEMVwp2cYd5HcDBd44pJkXbbQprSfPvmgjFDoBTnbw==",
+        "shasum": "3ae44dd6f8c40134b067a6a9c7a723ffbbbb6e3e",
+        "tarball": "https://verdaccio.mrsdev.ru/typescript/-/typescript-5.9.0-dev.20250319.tgz",
+        "fileCount": 130,
+        "unpackedSize": 22874027,
+        "signatures": [
+          {
+            "keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U",
+            "sig": "MEQCIA3VD+XhWkzCN1mp0pUu41ZCryRaXXvv+BOQpdxnR2e+AiBP2IvxxSqu6+5K7RF3Hp3B6ZCJv0XiPz93wHB8HenGmw=="
+          }
+        ]
+      },
+      "_npmUser": {
+        "name": "typescript-bot",
+        "email": "typescript@microsoft.com"
+      },
+      "directories": {},
+      "maintainers": [
+        {
+          "name": "typescript-bot",
+          "email": "typescript@microsoft.com"
+        },
+        {
+          "name": "weswigham",
+          "email": "wwigham@gmail.com"
+        },
+        {
+          "name": "sanders_n",
+          "email": "nathan@shively-sanders.com"
+        },
+        {
+          "name": "andrewbranch",
+          "email": "andrew@wheream.io"
+        },
+        {
+          "name": "minestarks",
+          "email": "mineyalc@microsoft.com"
+        },
+        {
+          "name": "rbuckton",
+          "email": "rbuckton@chronicles.org"
+        },
+        {
+          "name": "sheetalkamat",
+          "email": "shkamat@microsoft.com"
+        },
+        {
+          "name": "typescript-deploys",
+          "email": "typescript-design@microsoft.com"
+        }
+      ],
+      "_npmOperationalInternal": {
+        "host": "s3://npm-registry-packages-npm-production",
+        "tmp": "tmp/typescript_5.9.0-dev.20250319_1742368519947_0.3042535938497817"
+      },
+      "_hasShrinkwrap": false,
+      "contributors": []
     }
   },
   "time": {
-    "modified": "2025-03-17T07:15:06.661Z",
+    "modified": "2025-03-19T07:15:20.534Z",
     "created": "2012-10-01T15:35:39.553Z",
     "0.8.0": "2012-10-01T15:35:41.062Z",
     "0.8.1": "2012-11-15T20:53:44.894Z",
@@ -532697,19 +533045,21 @@
     "5.9.0-dev.20250314": "2025-03-14T07:14:36.695Z",
     "5.9.0-dev.20250315": "2025-03-15T07:14:52.510Z",
     "5.9.0-dev.20250316": "2025-03-16T07:14:40.092Z",
-    "5.9.0-dev.20250317": "2025-03-17T07:15:06.393Z"
+    "5.9.0-dev.20250317": "2025-03-17T07:15:06.393Z",
+    "5.9.0-dev.20250318": "2025-03-18T07:14:55.647Z",
+    "5.9.0-dev.20250319": "2025-03-19T07:15:20.305Z"
   },
   "users": {},
   "dist-tags": {
     "latest": "5.8.2",
-    "next": "5.9.0-dev.20250317",
+    "next": "5.9.0-dev.20250319",
     "beta": "5.8.0-beta",
     "rc": "5.8.1-rc",
     "insiders": "4.6.2-insiders.20220225",
     "tag-for-publishing-older-releases": "4.1.6",
     "dev": "3.9.4"
   },
-  "_rev": "1633-61e2b945b4b34372",
+  "_rev": "1635-c06bc743027e0822",
   "_id": "typescript",
   "readme": "",
   "_attachments": {}