mrs-toolbox-cli 9.1.9 → 10.0.9-d68939b

package/npm-cache/_cacache/content-v2/sha512/{35/12/189789dc7056763977b27ca330e102e7944a5b14040682d57be42690dd94b89fe5187e1ea0748cee93bba1ff46117e015c56c837cd9cb7ea7c9f32a3d47e → 3a/d0/c75ef5bbf2db6caccda906b577354bb7c6ed444ad711e9c2684e368fe17cde89f562b7f932067dcd75f1816558870e0575a5a9b6a690646e447b58d679dd}

@@ -1754,7 +1754,7 @@
   "dist-tags": {
     "latest": "5.2.0"
   },
-  "_rev": "299-3d84c7e1f40d644b",
+  "_rev": "304-dc024efe099a7574",
   "_id": "@aws-crypto/sha256-js",
   "readme": "# crypto-sha256-js\n\nA pure JS implementation SHA256.\n\n## Usage\n\n- To hash \"some data\"\n```\nimport {Sha256} from '@aws-crypto/sha256-js';\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-js';\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/{81/60/36c3b4636f6fb3652e5158f46785b68c1eb13fb740ce0f56d3c38962b06b2f96e7a302ba5cb9d0923a01f292890b5f0ac5b6bde9a495518c4a2d6c594c13 → 3c/c8/5db16c8cc97ce40df3caeed9460bbf5d88d4c2a211a8e5df22b56d9b739701d2bcd24537f08333a91a7b8ae1e151b2c15c3b48fdcba363fcac0159b49853}

@@ -496830,10 +496830,227 @@
       },
       "_hasShrinkwrap": false,
       "contributors": []
+    },
+    "0.84.0": {
+      "name": "react-native",
+      "version": "0.84.0",
+      "description": "A framework for building native apps using React",
+      "license": "MIT",
+      "repository": {
+        "type": "git",
+        "url": "git+https://github.com/facebook/react-native.git",
+        "directory": "packages/react-native"
+      },
+      "homepage": "https://reactnative.dev/",
+      "keywords": [
+        "react",
+        "react-native",
+        "android",
+        "ios",
+        "mobile",
+        "cross-platform",
+        "app-framework",
+        "mobile-development"
+      ],
+      "bugs": {
+        "url": "https://github.com/facebook/react-native/issues"
+      },
+      "engines": {
+        "node": ">= 20.19.4"
+      },
+      "bin": {
+        "react-native": "cli.js"
+      },
+      "main": "./index.js",
+      "types": "types",
+      "exports": {
+        ".": {
+          "react-native-strict-api": "./types_generated/index.d.ts",
+          "types": "./types/index.d.ts",
+          "default": "./index.js"
+        },
+        "./*": {
+          "react-native-strict-api": null,
+          "types": "./*.d.ts",
+          "default": "./*.js"
+        },
+        "./*.js": {
+          "react-native-strict-api": null,
+          "default": "./*.js"
+        },
+        "./Libraries/*.d.ts": {
+          "react-native-strict-api": null,
+          "default": "./Libraries/*.d.ts"
+        },
+        "./scripts/*": "./scripts/*",
+        "./src/*": {
+          "react-native-strict-api": null,
+          "default": "./src/*.js"
+        },
+        "./types/*.d.ts": {
+          "react-native-strict-api": null,
+          "default": "./types/*.d.ts"
+        },
+        "./gradle/*": null,
+        "./React/*": null,
+        "./ReactAndroid/*": null,
+        "./ReactApple/*": null,
+        "./ReactCommon/*": null,
+        "./sdks/*": null,
+        "./src/fb_internal/*": "./src/fb_internal/*",
+        "./third-party-podspecs/*": null,
+        "./types/*": null,
+        "./types_generated/*": null,
+        "./package.json": "./package.json"
+      },
+      "jest-junit": {
+        "outputDirectory": "reports/junit",
+        "outputName": "js-test-results.xml"
+      },
+      "scripts": {
+        "prepack": "node ./scripts/prepack.js",
+        "featureflags": "node ./scripts/featureflags/index.js"
+      },
+      "peerDependencies": {
+        "@types/react": "^19.1.1",
+        "react": "^19.2.3"
+      },
+      "peerDependenciesMeta": {
+        "@types/react": {
+          "optional": true
+        }
+      },
+      "dependencies": {
+        "@jest/create-cache-key-function": "^29.7.0",
+        "@react-native/assets-registry": "0.84.0",
+        "@react-native/codegen": "0.84.0",
+        "@react-native/community-cli-plugin": "0.84.0",
+        "@react-native/gradle-plugin": "0.84.0",
+        "@react-native/js-polyfills": "0.84.0",
+        "@react-native/normalize-colors": "0.84.0",
+        "@react-native/virtualized-lists": "0.84.0",
+        "abort-controller": "^3.0.0",
+        "anser": "^1.4.9",
+        "ansi-regex": "^5.0.0",
+        "babel-jest": "^29.7.0",
+        "babel-plugin-syntax-hermes-parser": "0.32.0",
+        "base64-js": "^1.5.1",
+        "commander": "^12.0.0",
+        "flow-enums-runtime": "^0.0.6",
+        "hermes-compiler": "250829098.0.7",
+        "invariant": "^2.2.4",
+        "jest-environment-node": "^29.7.0",
+        "memoize-one": "^5.0.0",
+        "metro-runtime": "^0.83.3",
+        "metro-source-map": "^0.83.3",
+        "nullthrows": "^1.1.1",
+        "pretty-format": "^29.7.0",
+        "promise": "^8.3.0",
+        "react-devtools-core": "^6.1.5",
+        "react-refresh": "^0.14.0",
+        "regenerator-runtime": "^0.13.2",
+        "scheduler": "0.27.0",
+        "semver": "^7.1.3",
+        "stacktrace-parser": "^0.1.10",
+        "tinyglobby": "^0.2.15",
+        "whatwg-fetch": "^3.0.0",
+        "ws": "^7.5.10",
+        "yargs": "^17.6.2"
+      },
+      "codegenConfig": {
+        "libraries": [
+          {
+            "name": "FBReactNativeSpec",
+            "type": "all",
+            "ios": {
+              "modules": {
+                "AccessibilityManager": {
+                  "unstableRequiresMainQueueSetup": true
+                },
+                "Appearance": {
+                  "unstableRequiresMainQueueSetup": true
+                },
+                "AppState": {
+                  "unstableRequiresMainQueueSetup": true
+                },
+                "DeviceInfo": {
+                  "unstableRequiresMainQueueSetup": true
+                },
+                "PlatformConstants": {
+                  "unstableRequiresMainQueueSetup": true
+                },
+                "StatusBarManager": {
+                  "unstableRequiresMainQueueSetup": true
+                }
+              }
+            },
+            "android": {},
+            "jsSrcsDir": "src"
+          }
+        ]
+      },
+      "_id": "react-native@0.84.0",
+      "gitHead": "5693f6097d8a5345e21b3035231bbc523752d465",
+      "_nodeVersion": "22.14.0",
+      "_npmVersion": "10.9.2",
+      "dist": {
+        "integrity": "sha512-CcBfucLDHz8MAjQx9kFXasYtpcn8zP1YapUgGtAy0psRZTLShwF9yeh5+ErSgEK2gXV1CCSz7hqCZqx1eMyBLA==",
+        "shasum": "0758f856df367789be3dcc78640eec8a77dbcbbb",
+        "tarball": "https://verdaccio.mrsdev.ru/react-native/-/react-native-0.84.0.tgz",
+        "fileCount": 4516,
+        "unpackedSize": 21467955,
+        "signatures": [
+          {
+            "keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U",
+            "sig": "MEUCICJ4zezq/4qKbyJdPJ+yyOjoiEY+i0bCPUMg8i4iLp4zAiEA5+TQopv+epXvYOslcQhyT8mtPikl2lZ5JgZ78Tf6cHs="
+          }
+        ]
+      },
+      "_npmUser": {
+        "name": "react-native-bot",
+        "email": "opensource+react-native-bot@fb.com"
+      },
+      "directories": {},
+      "maintainers": [
+        {
+          "name": "react-native-bot",
+          "email": "opensource+react-native-bot@fb.com"
+        },
+        {
+          "name": "fb",
+          "email": "opensource+npm@fb.com"
+        },
+        {
+          "name": "lunaleaps",
+          "email": "lunaleaps@gmail.com"
+        },
+        {
+          "name": "eliwhite",
+          "email": "npm@eli-white.com"
+        },
+        {
+          "name": "yungsters",
+          "email": "yungsters@gmail.com"
+        },
+        {
+          "name": "cortinico",
+          "email": "corti.nico@gmail.com"
+        },
+        {
+          "name": "fkgozali",
+          "email": "fkgozali@gmail.com"
+        }
+      ],
+      "_npmOperationalInternal": {
+        "host": "s3://npm-registry-packages-npm-production",
+        "tmp": "tmp/react-native_0.84.0_1770825859106_0.7663193261901364"
+      },
+      "_hasShrinkwrap": false,
+      "contributors": []
     }
   },
   "time": {
-    "modified": "2026-02-10T04:02:19.475Z",
+    "modified": "2026-02-11T16:04:19.744Z",
     "created": "2015-01-27T23:23:42.403Z",
     "0.0.0": "2015-01-27T23:23:42.403Z",
     "0.0.1": "2015-03-25T22:44:01.648Z",
@@ -499311,11 +499528,12 @@
     "0.85.0-nightly-20260206-d494510ce": "2026-02-06T04:00:39.059Z",
     "0.85.0-nightly-20260207-7e7f491c9": "2026-02-07T03:41:16.370Z",
     "0.85.0-nightly-20260208-0dd9e73be": "2026-02-08T04:01:29.261Z",
-    "0.85.0-nightly-20260210-4535df4f6": "2026-02-10T04:02:19.358Z"
+    "0.85.0-nightly-20260210-4535df4f6": "2026-02-10T04:02:19.358Z",
+    "0.84.0": "2026-02-11T16:04:19.627Z"
   },
   "users": {},
   "dist-tags": {
-    "latest": "0.83.1",
+    "latest": "0.84.0",
     "next": "0.84.0-rc.5",
     "nightly": "0.85.0-nightly-20260210-4535df4f6",
     "0.66-stable": "0.66.5",
@@ -499339,7 +499557,7 @@
     "0.81-stable": "0.81.6",
     "0.83-stable": "0.83.2"
   },
-  "_rev": "756-b56da46fef85e675",
+  "_rev": "765-4f64123db1963994",
   "_id": "react-native",
   "readme": "<h1 align=\"center\">\n  <a href=\"https://reactnative.dev/\">\n    React Native\n  </a>\n</h1>\n\n<p align=\"center\">\n  <strong>Learn once, write anywhere:</strong><br>\n  Build mobile apps with React.\n</p>\n\n<p align=\"center\">\n  <a href=\"https://github.com/facebook/react-native/blob/HEAD/LICENSE\">\n    <img src=\"https://img.shields.io/badge/license-MIT-blue.svg\" alt=\"React Native is released under the MIT license.\" />\n  </a>\n  <a href=\"https://www.npmjs.org/package/react-native\">\n    <img src=\"https://img.shields.io/npm/v/react-native?color=brightgreen&label=npm%20package\" alt=\"Current npm package version.\" />\n  </a>\n  <a href=\"https://reactnative.dev/docs/contributing\">\n    <img src=\"https://img.shields.io/badge/PRs-welcome-brightgreen.svg\" alt=\"PRs are welcome!\" />\n  </a>\n  <a href=\"https://twitter.com/intent/follow?screen_name=reactnative\">\n    <img src=\"https://img.shields.io/twitter/follow/reactnative.svg?label=Follow%20@reactnative\" alt=\"Follow @reactnative on X\" />\n  </a>\n  <a href=\"https://bsky.app/profile/reactnative.dev\">\n    <img src=\"https://img.shields.io/badge/Bluesky-0285FF?logo=bluesky&logoColor=fff\" alt=\"Follow @reactnative.dev on Bluesky\" />\n  </a>\n</p>\n\n<h3 align=\"center\">\n  <a href=\"https://reactnative.dev/docs/getting-started\">Getting Started</a>\n  <span> · </span>\n  <a href=\"https://reactnative.dev/docs/tutorial\">Learn the Basics</a>\n  <span> · </span>\n  <a href=\"https://reactnative.dev/showcase\">Showcase</a>\n  <span> · </span>\n  <a href=\"https://reactnative.dev/docs/contributing\">Contribute</a>\n  <span> · </span>\n  <a href=\"https://reactnative.dev/help\">Community</a>\n  <span> · </span>\n  <a href=\"https://github.com/facebook/react-native/blob/HEAD/.github/SUPPORT.md\">Support</a>\n</h3>\n\nReact Native brings [**React**'s][r] declarative UI framework to iOS and Android. With React Native, you use native UI controls and have full access to the native platform.\n\n- **Declarative.** React makes it painless to create interactive UIs. Declarative views make your code more predictable and easier to debug.\n- **Component-Based.** Build encapsulated components that manage their state, then compose them to make complex UIs.\n- **Developer Velocity.** See local changes in seconds. Changes to JavaScript code can be live reloaded without rebuilding the native app.\n- **Portability.** Reuse code across iOS, Android, and [other platforms][p].\n\nReact Native is developed and supported by many companies and individual core contributors. Find out more in our [ecosystem overview][e].\n\n[r]: https://react.dev/\n[p]: https://reactnative.dev/docs/out-of-tree-platforms\n[e]: https://github.com/facebook/react-native/blob/HEAD/ECOSYSTEM.md\n\n## Contents\n\n- [Requirements](#-requirements)\n- [Building your first React Native app](#-building-your-first-react-native-app)\n- [Documentation](#-documentation)\n- [Upgrading](#-upgrading)\n- [How to Contribute](#-how-to-contribute)\n- [Code of Conduct](#code-of-conduct)\n- [License](#-license)\n\n\n## 📋 Requirements\n\nReact Native apps may target iOS 15.1 and Android 7.0 (API 24) or newer. You may use Windows, macOS, or Linux as your development operating system, though building and running iOS apps is limited to macOS. Tools like [Expo](https://expo.dev) can be used to work around this.\n\n## 🎉 Building your first React Native app\n\nFollow the [Getting Started guide](https://reactnative.dev/docs/getting-started). The recommended way to install React Native depends on your project. Here you can find short guides for the most common scenarios:\n\n- [Trying out React Native][hello-world]\n- [Creating a New Application][new-app]\n- [Adding React Native to an Existing Application][existing]\n\n[hello-world]: https://snack.expo.dev/@samples/hello-world\n[new-app]: https://reactnative.dev/docs/getting-started\n[existing]: https://reactnative.dev/docs/integration-with-existing-apps\n\n## 📖 Documentation\n\nThe full documentation for React Native can be found on our [website][docs].\n\nThe React Native documentation discusses components, APIs, and topics that are specific to React Native. For further documentation on the React API that is shared between React Native and React DOM, refer to the [React documentation][r-docs].\n\nThe source for the React Native documentation and website is hosted on a separate repository, [**@facebook/react-native-website**][repo-website].\n\n[docs]: https://reactnative.dev/docs/getting-started\n[r-docs]: https://react.dev/learn\n[repo-website]: https://github.com/facebook/react-native-website\n\n## 🚀 Upgrading\n\nUpgrading to new versions of React Native may give you access to more APIs, views, developer tools, and other goodies. See the [Upgrading Guide][u] for instructions.\n\nReact Native releases are discussed [in this discussion repo](https://github.com/reactwg/react-native-releases/discussions).\n\n[u]: https://reactnative.dev/docs/upgrading\n[repo-releases]: https://github.com/react-native-community/react-native-releases\n\n## 👏 How to Contribute\n\nThe main purpose of this repository is to continue evolving React Native core. We want to make contributing to this project as easy and transparent as possible, and we are grateful to the community for contributing bug fixes and improvements. Read below to learn how you can take part in improving React Native.\n\n### [Code of Conduct][code]\n\nFacebook has adopted a Code of Conduct that we expect project participants to adhere to.\nPlease read the [full text][code] so that you can understand what actions will and will not be tolerated.\n\n[code]: https://code.fb.com/codeofconduct/\n\n### [Contributing Guide][contribute]\n\nRead our [**Contributing Guide**][contribute] to learn about our development process, how to propose bugfixes and improvements, and how to build and test your changes to React Native.\n\n[contribute]: https://reactnative.dev/docs/contributing\n\n### [Open Source Roadmap][roadmap]\n\nYou can learn more about our vision for React Native in the [**Roadmap**][roadmap].\n\n[roadmap]: https://github.com/facebook/react-native/wiki/Roadmap\n\n### Good First Issues\n\nWe have a list of [good first issues][gfi] that contain bugs which have a relatively limited scope. This is a great place to get started, gain experience, and get familiar with our contribution process.\n\n[gfi]: https://github.com/facebook/react-native/labels/good%20first%20issue\n\n### Discussions\n\nLarger discussions and proposals are discussed in [**@react-native-community/discussions-and-proposals**][repo-meta].\n\n[repo-meta]: https://github.com/react-native-community/discussions-and-proposals\n\n## 📄 License\n\nReact Native is MIT licensed, as found in the [LICENSE][l] file.\n\n[l]: https://github.com/facebook/react-native/blob/main/LICENSE",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{17/6b/c6f976f9e397d5a000bd8c368360ec5b8f6ebeeda60fdaff0673da8350e3a249b94242a944a1738a43343c3d6ee03ceb501ef11ec1d91005ce18f77411b3 → 3d/c2/00e13ee31c0eaa839bd82a985393fe9bac6fbb59984bd74c0d0392e85da758074ac413b1cef01f07e58b559f551caaea014c94c5941c8d862443893c25fc}

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

package/npm-cache/_cacache/content-v2/sha512/{ce/b0/eaa462652e7ce5a5075eca61c8c0d147e8c875812febcfe527a58ee561d1051e974f59d27b593496cf4acaf06df028bf35b19142cd9434186c4d8837e21c → 3e/b9/a5a2558e9ddb55355e821aebfeb23dcd14a309ab9e4a12ecfce6bc14e8c21d90fcffb42cdb85a10f50a381d48db31ab43c2819916125b37f7221b80d2111}

@@ -606,7 +606,7 @@
   "dist-tags": {
     "latest": "4.0.1"
   },
-  "_rev": "2026-14a106ed86319a57",
+  "_rev": "2035-b80165d2f211d911",
   "_id": "is-stream",
   "readme": "# is-stream\n\n> Check if something is a [Node.js stream](https://nodejs.org/api/stream.html)\n\n## Install\n\n```sh\nnpm install is-stream\n```\n\n## Usage\n\n```js\nimport fs from 'node:fs';\nimport {isStream} from 'is-stream';\n\nisStream(fs.createReadStream('unicorn.png'));\n//=> true\n\nisStream({});\n//=> false\n```\n\n## API\n\n### isStream(stream, options?)\n\nReturns a `boolean` for whether it's a [`Stream`](https://nodejs.org/api/stream.html#stream_stream).\n\n### isWritableStream(stream, options?)\n\nReturns a `boolean` for whether it's a [`stream.Writable`](https://nodejs.org/api/stream.html#stream_class_stream_writable), an [`http.OutgoingMessage`](https://nodejs.org/api/http.html#class-httpoutgoingmessage), an [`http.ServerResponse`](https://nodejs.org/api/http.html#class-httpserverresponse) or an [`http.ClientRequest`](https://nodejs.org/api/http.html#class-httpserverresponse).\n\n### isReadableStream(stream, options?)\n\nReturns a `boolean` for whether it's a [`stream.Readable`](https://nodejs.org/api/stream.html#stream_class_stream_readable) or an [`http.IncomingMessage`](https://nodejs.org/api/http.html#class-httpincomingmessage).\n\n### isDuplexStream(stream, options?)\n\nReturns a `boolean` for whether it's a [`stream.Duplex`](https://nodejs.org/api/stream.html#stream_class_stream_duplex).\n\n### isTransformStream(stream, options?)\n\nReturns a `boolean` for whether it's a [`stream.Transform`](https://nodejs.org/api/stream.html#stream_class_stream_transform).\n\n### Options\n\n#### checkOpen\n\nType: `boolean`\\\nDefault: `true`\n\nWhen this option is `true`, the method returns `false` if the stream has already been closed.\n\n## Related\n\n- [is-file-stream](https://github.com/jamestalmage/is-file-stream) - Detect if a stream is a file stream",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{a7/f8/c211ebfc7996d3f2257d6c3fcfe16719ec360cbbf8fdc8817e7162e5795c7742e25e1d35970bebef9f85ee035890b2e8204e2cc1b2849eb9e71df7b2dfe0 → 41/61/121e9668478a86ea85326e927499ec2a476275a396a707e1d9e2519d367f83f1d9149b1dcd7617c4dd75bce498e6812a8ff69515cdb60363b475e191c291}

@@ -969,7 +969,7 @@
   "dist-tags": {
     "latest": "0.11.0"
   },
-  "_rev": "948-75c9230a6e2d1105",
+  "_rev": "960-ff0d06ea145829fa",
   "_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/{b5/6d/bd9bf1eacfeb606636730a72fe432b5b0d8232b05f9b15ef239a58f0173b455ae9e1abe65f9c4a6ed81e4542be9ffe194fb745d277a609a222c18a6bccfd → 42/45/d0cede606ff2eac0bf193da352aebe760b8302f511f984ea5a6add963337831f5a54cd0819fb4f08e8a86344be5036ee35d515f0240de636bb91091eb0af}

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

package/npm-cache/_cacache/content-v2/sha512/{1d/cc/7124baea7ee82b5b1a982f0cde3317dda9d7520973d36dd79bf1f457492117d1e82bd546231f98546af9a2b8419492a6f28a20f6bff0039151cbca150b44 → 42/96/1c1f15e3544681817fe1a06042937aa0ef7f2ae30518ef30ab3dde620705a360190bcf6d3dc7aa8784e9ac9afe8d93c6cd766600781d28053ca71481c67b}

@@ -19242,7 +19242,7 @@
     "gamma": "1.0.0-gamma.8",
     "rc": "1.0.0-rc.10"
   },
-  "_rev": "308-763dc4454b86ee8b",
+  "_rev": "313-18604595a895c7b2",
   "_id": "@aws-sdk/middleware-ssec",
   "readme": "# @aws-sdk/middleware-ssec\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/middleware-ssec/latest.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-ssec)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/middleware-ssec.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-ssec)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{5a/43/17bf5e34e0bfa28223e20d0d81545553d3ffde900c58d948494f968e0a3d56ebf8fce5be2b0b5288ceefe8d05035156b6555ee8ff28e410a6ea1d83c4dae → 44/b7/72c6934342fbce95fa59be5b94aa4f1e3921eea9c15768466f6748aa65ad44b9e08cb83667a9ada5a443dfb2d51f2d7ab936d3e0af498ad9f5d68358fb21}

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

package/npm-cache/_cacache/content-v2/sha512/{b5/c8/3c9ca4e8d4871d1e3972a28a61c6a15c93d9736306f76e4b067721b2030c2660ade42867fe7bddebb79752b8357d65f20833377d18ba17b3c06272e5fcbe → 45/a3/053df3d450ee23d29ec55ef15ffa7ed571dc9929ca324c05509e7cb65dc2d380c257356d69cdcbf6945b432c2de667ff85e63ca9abc3029fe425019616b1}

@@ -6257,7 +6257,7 @@
   "dist-tags": {
     "latest": "4.2.8"
   },
-  "_rev": "205-44f6bc23b8763271",
+  "_rev": "210-56808477c0894894",
   "_id": "@smithy/util-waiter",
   "readme": "# @smithy/util-waiter\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/util-waiter/latest.svg)](https://www.npmjs.com/package/@smithy/util-waiter)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/util-waiter.svg)](https://www.npmjs.com/package/@smithy/util-waiter)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{64/1f/9525ac3ee864de4b2c28906a49e78029bbf5ed47b0368fdd333f7a02c51ada828695def6d9b100dc718930122e72595a75caf2a6fdaf18e6a6130893cc44 → 47/71/3389210a0f5ffa2a2a27b3e84b761bdf220279bc3496180adf7b7af7b66ac0c4e134c65cc73a7cfb05a9602cbfd5f064efa8b81ee0746c950a0b245552ed}

@@ -7074,7 +7074,7 @@
   "dist-tags": {
     "latest": "4.2.9"
   },
-  "_rev": "205-c61a607b87028ce9",
+  "_rev": "210-8c3973e18385dda3",
   "_id": "@smithy/hash-blob-browser",
   "readme": "# @smithy/sha256-blob-browser\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/hash-blob-browser/latest.svg)](https://www.npmjs.com/package/@smithy/hash-blob-browser)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/hash-blob-browser.svg)](https://www.npmjs.com/package/@smithy/hash-blob-browser)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{09/cf/7026c1499efdb2390f09fd0930edc9c02813400b6214cfe9731b644e2f51d1146bc75402444117cf5a08b89830fcb882bdd07319d94325065cc9789dc3e8 → 47/ac/b75f1b1391411cd8733b77c710b146dbecb4ea3153d956dcac0aa33c2f214dc81737873c2f10d35382df037c25c0d9205a778851cb1020b4e5b1d5c70806}

@@ -826,7 +826,7 @@
   "dist-tags": {
     "latest": "5.2.0"
   },
-  "_rev": "287-52c3fcf5ab5faa48",
+  "_rev": "292-265904232099ff74",
   "_id": "@aws-crypto/sha1-browser",
   "readme": "# @aws-crypto/sha1-browser\n\nSHA1 wrapper for browsers that prefers `window.crypto.subtle`.\n\nSHA1 is **NOT** a cryptographically secure algorithm.\nIt should _only_ be used for non cryptographic functions like checksums.\n\n## Usage\n\n```\nimport {Sha1} from '@aws-crypto/sha1-browser'\n\nconst hash = new Sha1();\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/{fb/14/5aa54d8363f7e4955f35126d1b2469f81f609146d37a36ca8b14bb122176ff194e6f3c05febbb7d9f76cdb308d6cdfa96b2c2c45ab06ad83c4cb0ac8953e → 48/04/c40c999fed2e1c7ca5a9e9a5c8e0dae9aac8e65e31407316502e79013813de467faaa1cb521c35f94eb211a470a5deba2bf78c907ce70d918fd80ef7d131}

@@ -246195,7 +246195,7 @@
     "beta": "19.0.0-beta-e7d213dfb0-20240507",
     "rc": "19.0.0-rc-fb9a90fa48-20240614"
   },
-  "_rev": "13374-d78303433270cafb",
+  "_rev": "13395-40710e50a727f4c7",
   "_id": "react",
   "readme": "",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{81/3b/9bfc7f0d3d21e740dbfa842b1cfec57451e219ef3e330a75cec9e02b44542bb63601a011b3fd8fa6bf8a182c63243af2a7298bddc3724e8709438c41cad1 → 48/14/2d2547ef7608bcf09b3be4ec4a47d631b92ad79711152a9c7e087bab9593d8bdc6683ef52f0028783b0f3c68925b126d592f480a70747731619bccdca6a5}

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

package/npm-cache/_cacache/content-v2/sha512/{6f/71/4fa81f2baa898d49e940303a881441de9053fb4079885d78d3f5bbc9023c473909afbd4b9a966be5b9d1ed6926d0241c59213438c746ee87b249a30224fd → 4a/26/3387eff70c1b296900f7b53348aa4e20363df3d0a93a7aedcc1a6e62e7e2f493c93d35f52dba0369a12708951d6d88d307597a77d84a726a536dc64541ca}

@@ -240,7 +240,7 @@
   "dist-tags": {
     "latest": "4.0.1"
   },
-  "_rev": "608-3cc4a779a7f22230",
+  "_rev": "617-86f2616fc0ebeace",
   "_id": "@isaacs/balanced-match",
   "readme": "# @isaacs/balanced-match\n\nA hybrid CJS/ESM TypeScript fork of\n[balanced-match](http://npm.im/balanced-match).\n\nMatch balanced string pairs, like `{` and `}` or `<b>` and `</b>`. Supports regular expressions as well!\n\n[![CI](https://github.com/juliangruber/balanced-match/actions/workflows/ci.yml/badge.svg)](https://github.com/juliangruber/balanced-match/actions/workflows/ci.yml)\n[![downloads](https://img.shields.io/npm/dm/balanced-match.svg)](https://www.npmjs.org/package/balanced-match)\n\n## Example\n\nGet the first matching pair of braces:\n\n```js\nimport { balanced } from '@isaacs/balanced-match'\n\nconsole.log(balanced('{', '}', 'pre{in{nested}}post'))\nconsole.log(balanced('{', '}', 'pre{first}between{second}post'))\nconsole.log(balanced(/\\s+\\{\\s+/, /\\s+\\}\\s+/, 'pre  {   in{nest}   }  post'))\n```\n\nThe matches are:\n\n```bash\n$ node example.js\n{ start: 3, end: 14, pre: 'pre', body: 'in{nested}', post: 'post' }\n{ start: 3,\n  end: 9,\n  pre: 'pre',\n  body: 'first',\n  post: 'between{second}post' }\n{ start: 3, end: 17, pre: 'pre', body: 'in{nest}', post: 'post' }\n```\n\n## API\n\n### const m = balanced(a, b, str)\n\nFor the first non-nested matching pair of `a` and `b` in `str`, return an\nobject with those keys:\n\n- **start** the index of the first match of `a`\n- **end** the index of the matching `b`\n- **pre** the preamble, `a` and `b` not included\n- **body** the match, `a` and `b` not included\n- **post** the postscript, `a` and `b` not included\n\nIf there's no match, `undefined` will be returned.\n\nIf the `str` contains more `a` than `b` / there are unmatched pairs, the first match that was closed will be used. For example, `{{a}` will match `['{', 'a', '']` and `{a}}` will match `['', 'a', '}']`.\n\n### const r = balanced.range(a, b, str)\n\nFor the first non-nested matching pair of `a` and `b` in `str`, return an\narray with indexes: `[ <a index>, <b index> ]`.\n\nIf there's no match, `undefined` will be returned.\n\nIf the `str` contains more `a` than `b` / there are unmatched pairs, the first match that was closed will be used. For example, `{{a}` will match `[ 1, 3 ]` and `{a}}` will match `[0, 2]`.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{65/b6/6f460e4bab86fcd7e1ae15c3bf72bc44e73bc0650702d7af42bbca8775c52c521bd6de29888e105f77173cfc8fbb6bfb57255edf88151787df9ac72c3008 → 4a/6e/1424b72b07dc4b16ad06419cdca38717f8e2e20a34040af7d7e67966c3661af48f89ab709031641c55558564fa65790ee9298a36323b1f1543dd36beac9d}

@@ -7793,7 +7793,7 @@
   "dist-tags": {
     "latest": "4.4.10"
   },
-  "_rev": "207-6e10827d18f429e6",
+  "_rev": "212-93dc2bc815ce5ba6",
   "_id": "@smithy/node-http-handler",
   "readme": "# @smithy/node-http-handler\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/node-http-handler/latest.svg)](https://www.npmjs.com/package/@smithy/node-http-handler)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/node-http-handler.svg)](https://www.npmjs.com/package/@smithy/node-http-handler)\n\nThis package implements the default `requestHandler` for Node.js using `node:http`, `node:https`, and `node:http2`.\n\nFor an example on how `requestHandler`s are used by Smithy generated SDK clients, refer to\nthe [AWS SDK for JavaScript (v3) supplemental docs](https://github.com/aws/aws-sdk-js-v3/blob/main/supplemental-docs/CLIENTS.md#request-handler-requesthandler).",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{3e/a1/b6828aef9a5a0d3180f3915065624a7e329aba6c715fbb5e516772e8346bd8d547e119a4b8b4e425f3601909e43b0acb3122dda19d7a6aee2a9164aab19a → 4b/d0/984e80daf350500f3c06ef0fd74bd0c32bd77755502915cba7f162ca345f4cfbc05051484b9bc6cec06a939e09bdb6147b84baffd329d40c65040e3cf142}

@@ -20358,7 +20358,7 @@
     "gamma": "1.0.0-gamma.8",
     "rc": "1.0.0-rc.10"
   },
-  "_rev": "325-f2e7d80388464a9e",
+  "_rev": "330-ded92c26713fb14c",
   "_id": "@aws-sdk/util-user-agent-browser",
   "readme": "# @aws-sdk/util-user-agent-browser\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/util-user-agent-browser/latest.svg)](https://www.npmjs.com/package/@aws-sdk/util-user-agent-browser)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/util-user-agent-browser.svg)](https://www.npmjs.com/package/@aws-sdk/util-user-agent-browser)\n\n## Usage\n\nIn previous versions of the AWS SDK for JavaScript v3, the AWS SDK user agent header was provided by parsing the navigator user agent string with the `bowser` library.\n\nThis was later changed to browser feature detection using the native Navigator APIs, but if you would like to have the previous functionality, use the following code:\n\n```js\nimport { createUserAgentStringParsingProvider } from \"@aws-sdk/util-user-agent-browser\";\n\nimport { S3Client } from \"@aws-sdk/client-s3\";\nimport pkgInfo from \"@aws-sdk/client-s3/package.json\";\n// or any other client.\n\nconst client = new S3Client({\n  defaultUserAgentProvider: createUserAgentStringParsingProvider({\n    // For a client's serviceId, check the corresponding shared runtimeConfig file\n    // https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-s3/src/runtimeConfig.shared.ts\n    serviceId: \"S3\",\n    clientVersion: pkgInfo.version,\n  }),\n});\n```\n\nThis usage is not recommended, due to the size of the additional parsing library.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{db/f6/8946fe10ef581d20e40d8e6b24c366b2a2ecd95b0599b46b733f826ffb1a03dbf09cabbf35719992f689cee579898ad3c423748d0103ec1807f0232bdd2a → 4d/7e/d638082cd5467e7b12c80cf1d2abbb249246931b7d295a3ff8f3da96aecd622ca679e27eb1c814dcb6cc830e2dcba3a99f253189978cbfb596f527bb82e1}

@@ -2642,7 +2642,7 @@
   "dist-tags": {
     "latest": "4.0.3"
   },
-  "_rev": "1452-6b1931a19d48ad4c",
+  "_rev": "1464-97a5efa060f6fa19",
   "_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": {}