mrs-toolbox-cli 6.0.19-0f15ba8 → 6.0.20

package/kotlinx-coroutines-core.js

@@ -256,7 +256,7 @@
   initMetadataForClass(Symbol, 'Symbol');
   initMetadataForInterface(SelectInstance, 'SelectInstance');
   initMetadataForClass(ClauseData, 'ClauseData', VOID, VOID, VOID, [1]);
-  initMetadataForClass(SelectImplementation, 'SelectImplementation', VOID, VOID, [CancelHandler, Waiter, SelectInstance], [0, 2]);
+  initMetadataForClass(SelectImplementation, 'SelectImplementation', VOID, VOID, [CancelHandler, SelectInstance, Waiter], [0, 2]);
   initMetadataForClass(TrySelectDetailedResult, 'TrySelectDetailedResult', VOID, Enum);
   initMetadataForClass(SetTimeoutBasedDispatcher, 'SetTimeoutBasedDispatcher', VOID, CoroutineDispatcher, [CoroutineDispatcher, Delay], [1]);
   initMetadataForObject(NodeDispatcher, 'NodeDispatcher', VOID, SetTimeoutBasedDispatcher, VOID, [1]);

package/npm-cache/_cacache/content-v2/sha512/{eb/14/d0f6c53ac9b4fd25992095e34f6d812eeaa60caa9489d72b8470fe7da1e8013feba67e6ac41f9895877c81c887ebcc5356bb1a128ca00f72460088305bbe → 00/0e/db6d36f5eb1c18fbc89b1a80defcc30ce06bec50b33b2d543e7e75cba4e429fc1362c621f9a9fe2aeb37435cd510332e35c52462023e438f895b695a2445}

@@ -1106,7 +1106,7 @@
   "dist-tags": {
     "latest": "7.0.0"
   },
-  "_rev": "542-4f736e026caa48e6",
+  "_rev": "539-f4eef2a3ed9fcb0f",
   "_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/{a1/00/e6d2e08bf51ab5dbc8ea7079c97149f0f715cfb3d01cf374f8955feaf6ebf576287324ae167fc6dd16ab6da6a9ce9525076a7a94d35537f9ac00e461010e → 00/e4/6f786e27db9a4944d8f6cc35e6fc571b12c327e74c12fa5c10978590af4411718d028493e953e4d53ed45863240c30050c3fb6daeb63da2bc8e2449619a1}

@@ -969,7 +969,7 @@
   "dist-tags": {
     "latest": "0.11.0"
   },
-  "_rev": "175-30e891f365571b8d",
+  "_rev": "170-9522d557fa8644d7",
   "_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/{a3/34/1e06ebf645a14a4f596349e373fc3e052c86882bfaef4b95adcade075c0e9467174ab8355256d820989f9b74fab5e53bcad64fe6a7988598b359e19c8fac → 01/0a/74fe8ff0bfed10ec323b8668c16d4cf409c4cfd8a4fd097f10249661729c9f57bc2245d2b91e04d21b83fa1b896323f6f33d6b111b3244df4c3928873d05}

@@ -45059,230 +45059,12 @@
       },
       "_hasShrinkwrap": false,
       "contributors": []
-    },
-    "3.806.0": {
-      "name": "@aws-sdk/credential-provider-ini",
-      "version": "3.806.0",
-      "keywords": [
-        "aws",
-        "credentials"
-      ],
-      "author": {
-        "url": "https://aws.amazon.com/javascript/",
-        "name": "AWS SDK for JavaScript Team"
-      },
-      "license": "Apache-2.0",
-      "_id": "@aws-sdk/credential-provider-ini@3.806.0",
-      "maintainers": [
-        {
-          "name": "amzn-oss",
-          "email": "osa-3p@amazon.com"
-        },
-        {
-          "name": "aws-sdk-bot",
-          "email": "aws-sdk-js-automation@amazon.com"
-        }
-      ],
-      "homepage": "https://github.com/aws/aws-sdk-js-v3/tree/main/packages/credential-provider-ini",
-      "bugs": {
-        "url": "https://github.com/aws/aws-sdk-js-v3/issues"
-      },
-      "dist": {
-        "shasum": "535cef9b760089e02811030202b69f6d54973ad4",
-        "tarball": "https://verdaccio.mrsdev.ru/@aws-sdk%2fcredential-provider-ini/-/credential-provider-ini-3.806.0.tgz",
-        "fileCount": 31,
-        "integrity": "sha512-FogfbuYSEZgFxbNy0QcsBZHHe5mSv5HV3+JyB5n0kCyjOISCVCZD7gwxKdXjt8O1hXq5k5SOdQvydGULlB6rew==",
-        "signatures": [
-          {
-            "sig": "MEYCIQDX5MCODGgYkmwbGpiEVud8vI3PquuFs/YMvWuS52pdbAIhAKIEjpaO7Oy8l28B1hnZiJx9g4KCATbjIw8ihPj/c5HT",
-            "keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"
-          }
-        ],
-        "unpackedSize": 51683
-      },
-      "main": "./dist-cjs/index.js",
-      "types": "./dist-types/index.d.ts",
-      "module": "./dist-es/index.js",
-      "engines": {
-        "node": ">=18.0.0"
-      },
-      "scripts": {
-        "test": "yarn g:vitest run",
-        "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
-        "clean": "rimraf ./dist-* && rimraf *.tsbuildinfo",
-        "build:es": "tsc -p tsconfig.es.json",
-        "build:cjs": "node ../../scripts/compilation/inline credential-provider-ini",
-        "test:watch": "yarn g:vitest watch",
-        "build:types": "tsc -p tsconfig.types.json",
-        "test:integration": "yarn g:vitest run -c vitest.config.integ.ts",
-        "build:include:deps": "lerna run --scope $npm_package_name --include-dependencies build",
-        "build:types:downlevel": "downlevel-dts dist-types dist-types/ts3.4",
-        "test:integration:watch": "yarn g:vitest watch -c vitest.config.integ.ts"
-      },
-      "_npmUser": {
-        "name": "aws-sdk-bot",
-        "email": "aws-sdk-js-automation@amazon.com"
-      },
-      "repository": {
-        "url": "git+https://github.com/aws/aws-sdk-js-v3.git",
-        "type": "git",
-        "directory": "packages/credential-provider-ini"
-      },
-      "_npmVersion": "10.9.2",
-      "description": "AWS credential provider that sources credentials from ~/.aws/credentials and ~/.aws/config",
-      "directories": {},
-      "_nodeVersion": "18.20.6",
-      "dependencies": {
-        "tslib": "^2.6.2",
-        "@aws-sdk/core": "3.806.0",
-        "@smithy/types": "^4.2.0",
-        "@aws-sdk/types": "3.804.0",
-        "@aws-sdk/nested-clients": "3.806.0",
-        "@smithy/property-provider": "^4.0.2",
-        "@smithy/shared-ini-file-loader": "^4.0.2",
-        "@aws-sdk/credential-provider-env": "3.806.0",
-        "@aws-sdk/credential-provider-sso": "3.806.0",
-        "@smithy/credential-provider-imds": "^4.0.2",
-        "@aws-sdk/credential-provider-http": "3.806.0",
-        "@aws-sdk/credential-provider-process": "3.806.0",
-        "@aws-sdk/credential-provider-web-identity": "3.806.0"
-      },
-      "typesVersions": {
-        "<4.0": {
-          "dist-types/*": [
-            "dist-types/ts3.4/*"
-          ]
-        }
-      },
-      "_hasShrinkwrap": false,
-      "devDependencies": {
-        "rimraf": "3.0.2",
-        "typescript": "~5.8.3",
-        "@types/node": "^18.19.69",
-        "concurrently": "7.0.0",
-        "downlevel-dts": "0.10.1",
-        "@tsconfig/recommended": "1.0.1"
-      },
-      "_npmOperationalInternal": {
-        "tmp": "tmp/credential-provider-ini_3.806.0_1746730764211_0.7834470022031153",
-        "host": "s3://npm-registry-packages-npm-production"
-      },
-      "contributors": []
-    },
-    "3.808.0": {
-      "name": "@aws-sdk/credential-provider-ini",
-      "version": "3.808.0",
-      "description": "AWS credential provider that sources credentials from ~/.aws/credentials and ~/.aws/config",
-      "main": "./dist-cjs/index.js",
-      "module": "./dist-es/index.js",
-      "scripts": {
-        "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
-        "build:cjs": "node ../../scripts/compilation/inline credential-provider-ini",
-        "build:es": "tsc -p tsconfig.es.json",
-        "build:include:deps": "lerna run --scope $npm_package_name --include-dependencies build",
-        "build:types": "tsc -p tsconfig.types.json",
-        "build:types:downlevel": "downlevel-dts dist-types dist-types/ts3.4",
-        "clean": "rimraf ./dist-* && rimraf *.tsbuildinfo",
-        "test": "yarn g:vitest run",
-        "test:watch": "yarn g:vitest watch",
-        "test:integration": "yarn g:vitest run -c vitest.config.integ.ts",
-        "test:integration:watch": "yarn g:vitest watch -c vitest.config.integ.ts"
-      },
-      "keywords": [
-        "aws",
-        "credentials"
-      ],
-      "author": {
-        "name": "AWS SDK for JavaScript Team",
-        "url": "https://aws.amazon.com/javascript/"
-      },
-      "license": "Apache-2.0",
-      "dependencies": {
-        "@aws-sdk/core": "3.808.0",
-        "@aws-sdk/credential-provider-env": "3.808.0",
-        "@aws-sdk/credential-provider-http": "3.808.0",
-        "@aws-sdk/credential-provider-process": "3.808.0",
-        "@aws-sdk/credential-provider-sso": "3.808.0",
-        "@aws-sdk/credential-provider-web-identity": "3.808.0",
-        "@aws-sdk/nested-clients": "3.808.0",
-        "@aws-sdk/types": "3.804.0",
-        "@smithy/credential-provider-imds": "^4.0.2",
-        "@smithy/property-provider": "^4.0.2",
-        "@smithy/shared-ini-file-loader": "^4.0.2",
-        "@smithy/types": "^4.2.0",
-        "tslib": "^2.6.2"
-      },
-      "devDependencies": {
-        "@tsconfig/recommended": "1.0.1",
-        "@types/node": "^18.19.69",
-        "concurrently": "7.0.0",
-        "downlevel-dts": "0.10.1",
-        "rimraf": "3.0.2",
-        "typescript": "~5.8.3"
-      },
-      "types": "./dist-types/index.d.ts",
-      "engines": {
-        "node": ">=18.0.0"
-      },
-      "typesVersions": {
-        "<4.0": {
-          "dist-types/*": [
-            "dist-types/ts3.4/*"
-          ]
-        }
-      },
-      "homepage": "https://github.com/aws/aws-sdk-js-v3/tree/main/packages/credential-provider-ini",
-      "repository": {
-        "type": "git",
-        "url": "git+https://github.com/aws/aws-sdk-js-v3.git",
-        "directory": "packages/credential-provider-ini"
-      },
-      "_id": "@aws-sdk/credential-provider-ini@3.808.0",
-      "bugs": {
-        "url": "https://github.com/aws/aws-sdk-js-v3/issues"
-      },
-      "_nodeVersion": "18.20.6",
-      "_npmVersion": "10.9.2",
-      "dist": {
-        "integrity": "sha512-Y53CW0pCvFQQEvtVFwExCCMbTg+6NOl8b3YOuZVzPmVmDoW7M1JIn9IScesqoGERXL3VoXny6nYTsZj+vfpp7Q==",
-        "shasum": "544869aeb67cdb0e338aadf29c4fa92240b4e944",
-        "tarball": "https://verdaccio.mrsdev.ru/@aws-sdk%2fcredential-provider-ini/-/credential-provider-ini-3.808.0.tgz",
-        "fileCount": 31,
-        "unpackedSize": 51683,
-        "signatures": [
-          {
-            "keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U",
-            "sig": "MEUCIB3kZWrO8Hl12FSsejI6/p1ulNyHhZR/X0owIdb6s4iaAiEAtX2TToQ+xaetjEYYV4cDMRzxIlieLCB2Fcv0ZayX6f8="
-          }
-        ]
-      },
-      "_npmUser": {
-        "name": "aws-sdk-bot",
-        "email": "aws-sdk-js-automation@amazon.com"
-      },
-      "directories": {},
-      "maintainers": [
-        {
-          "name": "amzn-oss",
-          "email": "osa-3p@amazon.com"
-        },
-        {
-          "name": "aws-sdk-bot",
-          "email": "aws-sdk-js-automation@amazon.com"
-        }
-      ],
-      "_npmOperationalInternal": {
-        "host": "s3://npm-registry-packages-npm-production",
-        "tmp": "tmp/credential-provider-ini_3.808.0_1747076709122_0.45998901785365676"
-      },
-      "_hasShrinkwrap": false,
-      "contributors": []
     }
   },
   "time": {
     "created": "2018-11-19T23:23:06.599Z",
     "0.1.0-preview.1": "2018-11-19T23:23:06.885Z",
-    "modified": "2025-05-12T19:05:10.283Z",
+    "modified": "2025-05-06T19:20:47.260Z",
     "0.1.0-preview.2": "2019-03-27T19:15:36.656Z",
     "0.1.0-preview.3": "2019-04-19T22:24:15.294Z",
     "0.1.0-preview.4": "2019-07-12T18:57:54.915Z",
@@ -45675,20 +45457,18 @@
     "3.798.0": "2025-04-28T18:51:54.310Z",
     "3.799.0": "2025-04-29T18:53:53.798Z",
     "3.803.0": "2025-05-05T19:32:29.284Z",
-    "3.804.0": "2025-05-06T19:20:47.040Z",
-    "3.806.0": "2025-05-08T18:59:24.422Z",
-    "3.808.0": "2025-05-12T19:05:09.333Z"
+    "3.804.0": "2025-05-06T19:20:47.040Z"
   },
   "users": {},
   "dist-tags": {
     "preview": "0.1.0-preview.7",
-    "latest": "3.808.0",
+    "latest": "3.804.0",
     "alpha": "1.0.0-alpha.6",
     "beta": "1.0.0-beta.4",
     "gamma": "1.0.0-gamma.9",
     "rc": "3.5.1-rc.0"
   },
-  "_rev": "117-3feeac92223743e1",
+  "_rev": "116-8c776695efb00f22",
   "_id": "@aws-sdk/credential-provider-ini",
   "readme": "# @aws-sdk/credential-provider-ini\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/credential-provider-ini/latest.svg)](https://www.npmjs.com/package/@aws-sdk/credential-provider-ini)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/credential-provider-ini.svg)](https://www.npmjs.com/package/@aws-sdk/credential-provider-ini)\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/{31/56/ebd8341312432dfe94a9948dd4ef00015f6f42ade9bc33c456437f3076403ba40db894fd05c79427f49a8647815d3736cc9d21466b079934fa94d64da35b → 01/a1/ca1b49ada33d8efbade4f74a2ddc3ed74005a3f41631df485372a1514b981d3c3452502f2fe65d78be381f235a38888ba096a6b584ecfebe4732652fc1f1}

@@ -823,7 +823,7 @@
   "dist-tags": {
     "latest": "3.374.0"
   },
-  "_rev": "104-f13a1087ab0aae50",
+  "_rev": "103-b66293bfe45d2071",
   "_id": "@aws-sdk/util-base64",
   "readme": "# @aws-sdk/util-base64\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/util-base64/latest.svg)](https://www.npmjs.com/package/@aws-sdk/util-base64)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/util-base64.svg)](https://www.npmjs.com/package/@aws-sdk/util-base64)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{a6/1d/5f9403ec05158642d76c2a969b8dea147198016f30ba635aa36f7701ee86fd4ac919d2f22c7dee17c663ed4bcbf7c99c65ee44b3221ce47535c8f76b0977 → 03/ff/e5b5f738341a9e7436afce61c8b7cc9a7a5545cbc2d9fb06d4bfaf24b4a7b13c69af1c8903e38d924d455a4b768104756f6ab7aa1523aa3f17e281fabe20}

@@ -1740,7 +1740,7 @@
   "dist-tags": {
     "latest": "5.2.0"
   },
-  "_rev": "99-616ac59f20455c23",
+  "_rev": "98-699b2513b6910648",
   "_id": "@aws-crypto/crc32",
   "readme": "# @aws-crypto/crc32\n\nPure JS implementation of CRC32 https://en.wikipedia.org/wiki/Cyclic_redundancy_check\n\n## Usage\n\n```\nimport { Crc32 } from '@aws-crypto/crc32';\n\nconst crc32Digest = (new Crc32).update(buffer).digest()\n\n```\n\n## Test\n\n`npm test`",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{5a/88/eeaa686b530da5eec824705441047e2246786339404763e0fffd34f8ef5f5ea6805fa1ed1d10d1f96554dbd380db1e6f31e9528a295cd6f0cced4db1b467 → 06/7d/9d131d9b8816811ec0384cf2c265b2abd255b12c1dd35fd90c2d7d955d59974621307d55d5c0bbafa44b32c7f17804b50965dbb2e9867c2b6bc9e7037507}

@@ -11181,7 +11181,7 @@
     "gamma": "1.0.0-gamma.8",
     "rc": "1.0.0-rc.9"
   },
-  "_rev": "111-d6025eaddeea673f",
+  "_rev": "110-3e0f93cb740c4ec2",
   "_id": "@aws-sdk/shared-ini-file-loader",
   "readme": "# @aws-sdk/shared-ini-file-loader\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/shared-ini-file-loader/latest.svg)](https://www.npmjs.com/package/@aws-sdk/shared-ini-file-loader)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/shared-ini-file-loader.svg)](https://www.npmjs.com/package/@aws-sdk/shared-ini-file-loader)\n\n## AWS Shared Configuration File Loader\n\nThis module provides a function that reads from AWS SDK configuration files and\nreturns a promise that will resolve with a hash of the parsed contents of the\nAWS credentials file and of the AWS config file. Given the [sample\nfiles](#sample-files) below, the promise returned by `loadSharedConfigFiles`\nwould resolve with:\n\n```javascript\n{\n  configFile: {\n    'default': {\n      aws_access_key_id: 'foo',\n      aws_secret_access_key: 'bar',\n    },\n    dev: {\n      aws_access_key_id: 'foo1',\n      aws_secret_access_key: 'bar1',\n    },\n    prod: {\n      aws_access_key_id: 'foo2',\n      aws_secret_access_key: 'bar2',\n    },\n    'testing host': {\n      aws_access_key_id: 'foo4',\n      aws_secret_access_key: 'bar4',\n    }\n  },\n  credentialsFile: {\n    'default': {\n      aws_access_key_id: 'foo',\n      aws_secret_access_key: 'bar',\n    },\n    dev: {\n      aws_access_key_id: 'foo1',\n      aws_secret_access_key: 'bar1',\n    },\n    prod: {\n      aws_access_key_id: 'foo2',\n      aws_secret_access_key: 'bar2',\n    }\n  },\n}\n```\n\nIf a file is not found, its key (`configFile` or `credentialsFile`) will instead\nhave a value of an empty object.\n\n## Supported configuration\n\nYou may customize how the files are loaded by providing an options hash to the\n`loadSharedConfigFiles` function. The following options are supported:\n\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- `ignoreCache` - The provider will normally cache the contents of the files it\n  loads. This option will force the provider to reload the files from disk.\n  Defaults to `false`.\n\n## Sample files\n\n### `~/.aws/credentials`\n\n```ini\n[default]\naws_access_key_id=foo\naws_secret_access_key=bar\n\n[dev]\naws_access_key_id=foo2\naws_secret_access_key=bar2\n\n[prod]\naws_access_key_id=foo3\naws_secret_access_key=bar3\n```\n\n### `~/.aws/config`\n\n```ini\n[default]\naws_access_key_id=foo\naws_secret_access_key=bar\n\n[profile dev]\naws_access_key_id=foo2\naws_secret_access_key=bar2\n\n[profile prod]\naws_access_key_id=foo3\naws_secret_access_key=bar3\n\n[profile \"testing host\"]\naws_access_key_id=foo4\naws_secret_access_key=bar4\n```",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{a4/1b/af7fd86e6ef5ffcd84f1256f7517f4ecfce741af0504aadb2f0430387fbd8861aabd420b0ccf92ea0e18693174d4c88641c01a6e318fe7f36f673bfa6392 → 0c/5e/f1bcb3002d3a7f23ad138a2958a049d0f0fab7636f1971c31b57eea19cfdf8ee9171e2ea5442d9cdd1f337f950ca7f8fee0f6e45230fc89a775d7eb36eae}

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

package/npm-cache/_cacache/content-v2/sha512/{44/98/d8b7d1b84d48c3b49aafd2d3d1bbd9c4e360caaae12ed9efc078967cd22dfbc4a6798585eb9923446574837fda9f7372de55b314c2361e01ad5c366a8848 → 0d/53/b894f2e679342785a4fbaf2c5f27efdeec3712cb8f57c16ff580cf9ee1db5cd661d4b124aa9bf93866c1a102644749a418f1e048b7150a7c93cc064dd1c4}

@@ -2018,7 +2018,7 @@
   "dist-tags": {
     "latest": "4.5.0"
   },
-  "_rev": "101-022a95edc0ade8d3",
+  "_rev": "100-c4d6ac3a9d52a056",
   "_id": "lodash.difference",
   "readme": "# lodash.difference v4.5.0\n\nThe [lodash](https://lodash.com/) method `_.difference` exported as a [Node.js](https://nodejs.org/) module.\n\n## Installation\n\nUsing npm:\n```bash\n$ {sudo -H} npm i -g npm\n$ npm i --save lodash.difference\n```\n\nIn Node.js:\n```js\nvar difference = require('lodash.difference');\n```\n\nSee the [documentation](https://lodash.com/docs#difference) or [package source](https://github.com/lodash/lodash/blob/4.5.0-npm-packages/lodash.difference) for more details.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{7c/e4/3c505246be62a554295db3133f890bcf3d46f49788ab9e514c8211264152b73e9e377175223435575fb7b0497d8186f6fcff2c8dbd3e513da7653d919896 → 0f/cc/88afcd129aebcadf5502a1bae07189e7374182c5568dcafdb0a47fa6367aa1681734ff1121666d1e02ded78241e75ce8a38e17030ec23b0b3f68accdc541}

@@ -14373,7 +14373,7 @@
   "dist-tags": {
     "latest": "1.26.2"
   },
-  "_rev": "164-b262a07068a30834",
+  "_rev": "161-6d1bb6f8214a4931",
   "_id": "aws-crt",
   "readme": "## AWS CRT JS\n\nNodeJS/Browser bindings for the AWS Common Runtime\n\n[API Docs](https://awslabs.github.io/aws-crt-nodejs/)\n\n## License\n\nThis library is licensed under the Apache 2.0 License.\n\n## Building the package\n\n### Prereqs:\n* Node 14+\n* npm\n* CMake 3.1+\n* Linux: gcc 5+ or clang 3.6+\n    * If your compiler can compile node, it can compile this library\n* Windows: Visual Studio 2015+\n* OSX: XCode or brew-installed llvm\n\nTo build the package locally\n```bash\ngit clone https://github.com/awslabs/aws-crt-nodejs.git\ncd aws-crt-nodejs\ngit submodule update --init\nnpm install\n```\n\n## Using From Your NodeJS Application\n\nNormally, you just declare `aws-crt` as a dependency in your package.json file.\n\n## Using From Your Browser Application\n\nYou can either add it to package.json (if using a tool like webpack), or just import the ```dist.browser/``` folder into your web project\n\n### Installing from npm\n\n```bash\nnpm install aws-crt\n```\n\nTo reduce the size of package, we put the C source code in the S3 bucket. If the platform you are using doesn't have the prebuilt binary, the install script will pull the source from S3 bucket. In case of no public internet access, you can specify the \"CRT_BINARY_HOST\" environment variable for the host of the source code. The build script will fetch source code from that host instead. To fetch the source from S3, you can reach to the cloudfront distribution (Only works for version after v1.9.2) `https://d332vdhbectycy.cloudfront.net/aws-crt-<version>-source.tgz`, the sha256 checksum `https://d332vdhbectycy.cloudfront.net/aws-crt-<version>-source.sha256`\n\n### Debug C part of code\n\nAfter building the package locally, use ```node ./scripts/build.js --debug``` to enable debug. Then, attach any C debugger to use node to run `jest`\n\n## Mac-Only TLS Behavior\n\nPlease note that on Mac, once a private key is used with a certificate, that certificate-key pair is imported into the Mac Keychain.  All subsequent uses of that certificate will use the stored private key and ignore anything passed in programmatically.  Beginning in v1.1.11, when a stored private key from the Keychain is used, the following will be logged at the \"info\" log level:\n\n```\nstatic: certificate has an existing certificate-key pair that was previously imported into the Keychain.  Using key from Keychain instead of the one provided.\n```",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{15/a5/7fd33d6bf002937433496bef49333edf634eb9da8d31866a091f0ba844cdd4aadef58731dc0d77af935d6737c3cbe46145f7a42eccc5aff6bd6aac60f159 → 0f/e1/b7cbf7ce512588b54c8885eeec648edef2db0a3bb001c807214aee0ce8bd81b0c19480a650ebe38629b5ac9ab880345b8f8077799972d8a349c189f9d254}

@@ -237,7 +237,7 @@
   "dist-tags": {
     "latest": "1.0.3"
   },
-  "_rev": "1273-a2f57831ec79ab7e",
+  "_rev": "1267-d9c73ef1ae154206",
   "_id": "core-util-is",
   "readme": "# core-util-is\n\nThe `util.is*` functions introduced in Node v0.12.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{c8/d5/b8f73cea93f0bc1e7b4d35f8ad414fc44d2dccbd0f7dd75163e9a378a3750e53296cdf99a2f713c97674b8d69b20b95e962900cb4e42e3327f9412305d30 → 0f/e4/b72779bf6d8999b51da98fb23042e506a64d93b9326cd20dc22abe9a08e0d0b8fe13dc02241887647a8cf519e8035cdb4e6c0b7eb10b1e0dce3616e5f49c}

@@ -466,7 +466,7 @@
   "dist-tags": {
     "latest": "2.0.1"
   },
-  "_rev": "1172-753dcc5c3b77b53b",
+  "_rev": "1165-8c0664bb470ebe10",
   "_id": "process-nextick-args",
   "readme": "process-nextick-args\n=====\n\n[![Build Status](https://travis-ci.org/calvinmetcalf/process-nextick-args.svg?branch=master)](https://travis-ci.org/calvinmetcalf/process-nextick-args)\n\n```bash\nnpm install --save process-nextick-args\n```\n\nAlways be able to pass arguments to process.nextTick, no matter the platform\n\n```js\nvar pna = require('process-nextick-args');\n\npna.nextTick(function (a, b, c) {\n  console.log(a, b, c);\n}, 'step', 3,  'profit');\n```",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{1f/55/daef565f185c8f3750808ffdd48c33fffbb8ad3b86765402f031a9ab804f53fa91def65b3a179648a28d22bb86555f7c6aa9addaf44fe0f8c5ddde32d0e4 → 10/55/58c4aba444b5cc0764652da10df30914aed6115644e4d7e7a0a87a4ceb192b0b1352acd20cd0124aab3ab58739cb6fe95b4289dfab8224fed6c391ff30ae}

@@ -2078,7 +2078,7 @@
   "dist-tags": {
     "latest": "3.3.1"
   },
-  "_rev": "611-7b6e2c35d15788a6",
+  "_rev": "604-87817fbfde6ed79d",
   "_id": "foreground-child",
   "readme": "# foreground-child\n\nRun a child as if it's the foreground process. Give it stdio. Exit\nwhen it exits.\n\nMostly this module is here to support some use cases around\nwrapping child processes for test coverage and such. But it's\nalso generally useful any time you want one program to execute\nanother as if it's the \"main\" process, for example, if a program\ntakes a `--cmd` argument to execute in some way.\n\n## USAGE\n\n```js\nimport { foregroundChild } from 'foreground-child'\n// hybrid module, this also works:\n// const { foregroundChild } = require('foreground-child')\n\n// cats out this file\nconst child = foregroundChild('cat', [__filename])\n\n// At this point, it's best to just do nothing else.\n// return or whatever.\n// If the child gets a signal, or just exits, then this\n// parent process will exit in the same way.\n```\n\nYou can provide custom spawn options by passing an object after\nthe program and arguments:\n\n```js\nconst child = foregroundChild(`cat ${__filename}`, { shell: true })\n```\n\nA callback can optionally be provided, if you want to perform an\naction before your foreground-child exits:\n\n```js\nconst child = foregroundChild('cat', [__filename], spawnOptions, () => {\n  doSomeActions()\n})\n```\n\nThe callback can return a Promise in order to perform\nasynchronous actions. If the callback does not return a promise,\nthen it must complete its actions within a single JavaScript\ntick.\n\n```js\nconst child = foregroundChild('cat', [__filename], async () => {\n  await doSomeAsyncActions()\n})\n```\n\nIf the callback throws or rejects, then it will be unhandled, and\nnode will exit in error.\n\nIf the callback returns a string value, then that will be used as\nthe signal to exit the parent process. If it returns a number,\nthen that number will be used as the parent exit status code. If\nit returns boolean `false`, then the parent process will not be\nterminated. If it returns `undefined`, then it will exit with the\nsame signal/code as the child process.\n\n## Caveats\n\nThe \"normal\" standard IO file descriptors (0, 1, and 2 for stdin,\nstdout, and stderr respectively) are shared with the child process.\nAdditionally, if there is an IPC channel set up in the parent, then\nmessages are proxied to the child on file descriptor 3.\n\nIn Node, it's possible to also map arbitrary file descriptors\ninto a child process. In these cases, foreground-child will not\nmap the file descriptors into the child. If file descriptors 0,\n1, or 2 are used for the IPC channel, then strange behavior may\nhappen (like printing IPC messages to stderr, for example).\n\nNote that a SIGKILL will always kill the parent process, but\nwill not proxy the signal to the child process, because SIGKILL\ncannot be caught. In order to address this, a special \"watchdog\"\nchild process is spawned which will send a SIGKILL to the child\nprocess if it does not terminate within half a second after the\nwatchdog receives a SIGHUP due to its parent terminating.\n\nOn Windows, issuing a `process.kill(process.pid, signal)` with a\nfatal termination signal may cause the process to exit with a `1`\nstatus code rather than reporting the signal properly. This\nmodule tries to do the right thing, but on Windows systems, you\nmay see that incorrect result. There is as far as I'm aware no\nworkaround for this.\n\n## util: `foreground-child/proxy-signals`\n\nIf you just want to proxy the signals to a child process that the\nmain process receives, you can use the `proxy-signals` export\nfrom this package.\n\n```js\nimport { proxySignals } from 'foreground-child/proxy-signals'\n\nconst childProcess = spawn('command', ['some', 'args'])\nproxySignals(childProcess)\n```\n\nNow, any fatal signal received by the current process will be\nproxied to the child process.\n\nIt doesn't go in the other direction; ie, signals sent to the\nchild process will not affect the parent. For that, listen to the\nchild `exit` or `close` events, and handle them appropriately.\n\n## util: `foreground-child/watchdog`\n\nIf you are spawning a child process, and want to ensure that it\nisn't left dangling if the parent process exits, you can use the\nwatchdog utility exported by this module.\n\n```js\nimport { watchdog } from 'foreground-child/watchdog'\n\nconst childProcess = spawn('command', ['some', 'args'])\nconst watchdogProcess = watchdog(childProcess)\n\n// watchdogProcess is a reference to the process monitoring the\n// parent and child. There's usually no reason to do anything\n// with it, as it's silent and will terminate\n// automatically when it's no longer needed.\n```",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{4d/1a/a180f86f8ddf8ab9a6ed5f1fdb678d7bef37547333175d57546b6eeb6d51300d61d9e53c7dff1078164586cca68290a6a268ac0772ee2b80964034e9007b → 10/ad/1976e409ad442d489d67ff0e91dd5efd863316c92bc0d76a1df3965b3d43e55348362eb68b5796d535b18c28f9e0f659a039400a0ab7bd2fa20fbc601350}

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

package/npm-cache/_cacache/content-v2/sha512/{62/0f/5b4be12ef0f9ecafb17a964f5cc4d9d7e75259fed4b13a31c1e56e62567aa72f9536f5114cda182abf50abc85c463d69eae0396fafdb9b26b4c2663b3844 → 11/10/33f1c84bcfbd0d7e6440232123e63ea69b4b39255b25d57e715eadf8de970aa9c9c963dc6a2bc0af4c4847dbeb63fa0a911a5e2d9fd904b730e3c30811b9}

@@ -13290,7 +13290,7 @@
     "gamma": "1.0.0-gamma.8",
     "rc": "1.0.0-rc.10"
   },
-  "_rev": "97-8628aeb01832674b",
+  "_rev": "96-c27f6c8eabfb5486",
   "_id": "@aws-sdk/hash-blob-browser",
   "readme": "# @aws-sdk/sha256-blob-browser\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/hash-blob-browser/latest.svg)](https://www.npmjs.com/package/@aws-sdk/hash-blob-browser)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/hash-blob-browser.svg)](https://www.npmjs.com/package/@aws-sdk/hash-blob-browser)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{9d/42/488c15c55a4a7cefe3b2ce591781f0ec2d66b8fb4517b68a4e1cd168e0f98749fd4c93e071212e06e19623aebd9e3bd261a3bfe3bb53a62f8a81465c4682 → 11/86/4bae3465ca8b2f73471f0a706b08f3e763f03f8f0fded531affa4a4700af3a67452966fd35d800a3e6688f83cdc1afac4153c0fe0f56526431f74a6902f7}

@@ -11805,7 +11805,7 @@
     "gamma": "1.0.0-gamma.8",
     "rc": "1.0.0-rc.10"
   },
-  "_rev": "109-50b3eff63709f37d",
+  "_rev": "108-5e78f4a754ca8928",
   "_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/{18/5c/de2b5e212526f75b6d665d204bfd206382eb882c7f6f0971f87e26f09a34417c1c358f6ccedace0befcb4b5590dc156cc8869b2c23ed97448285508a55df → 12/94/fbc9265327ff5364157331762ec99fbb6fdfa9a638efda59b362a522610a4acabd7569118622b9fb7fbbcef4dab457efbae377831e002883175368ba8bbe}

@@ -1924,7 +1924,7 @@
   "dist-tags": {
     "latest": "5.2.0"
   },
-  "_rev": "108-6f21f220577507ab",
+  "_rev": "107-3771734c251a1aaf",
   "_id": "@aws-crypto/sha256-browser",
   "readme": "# @aws-crypto/sha256-browser\n\nSHA256 wrapper for browsers that prefers `window.crypto.subtle` but will\nfall back to a pure JS implementation in @aws-crypto/sha256-js\nto provide a consistent interface for SHA256.\n\n## Usage\n\n- To hash \"some data\"\n```\nimport {Sha256} from '@aws-crypto/sha256-browser'\n\nconst hash = new Sha256();\nhash.update('some data');\nconst result = await hash.digest();\n\n```\n\n- To hmac \"some data\" with \"a key\"\n```\nimport {Sha256} from '@aws-crypto/sha256-browser'\n\nconst hash = new Sha256('a key');\nhash.update('some data');\nconst result = await hash.digest();\n\n```\n\n## Test\n\n`npm test`",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{2b/c3/746f822b73b33379547ef283f9d3ca08eae476a555e9aa01ab9d241b88b84e2eca2730574c8bd19fbc5bfaa7ee5759682137e64c9179ed8654495284a1da → 12/cd/0d5277dbc17b0b7b10f7dae2a82a8a75effa3d5916151dce0e050d164dedb6ef73eaf0744f0646cb75fd143fd8463b591fe729c95eaf740a9681b8d2ca21}

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

package/npm-cache/_cacache/content-v2/sha512/{58/14/6cb90507da5d9b862b38f00434e72551e3c2fce9fd31604bf038a33737b7614ab62a80364554a18944235a6bc45dbd55a126106bf0d992070e93c8adbbeb → 13/ed/f134ebb7579d5d724d0c4f2f700199b82823c5be396e55679f6dc0af880d306fc83acbc1db4e59f3d7b30611ef7c656e99a82a0069b4e46036c215fc5326}

@@ -12577,7 +12577,7 @@
     "latest": "3.374.0",
     "rc": "3.5.1-rc.0"
   },
-  "_rev": "110-4cd143d0a51eb295",
+  "_rev": "109-1920f2f9d02998a4",
   "_id": "@aws-sdk/node-config-provider",
   "readme": "# @aws-sdk/node-config-provider\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/node-config-provider/latest.svg)](https://www.npmjs.com/package/@aws-sdk/node-config-provider)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/node-config-provider.svg)](https://www.npmjs.com/package/@aws-sdk/node-config-provider)",
   "_attachments": {}