mrs-toolbox-cli 10.0.11 → 10.0.12-adfe739

package/npm-cache/_cacache/content-v2/sha512/{58/0f/862c7cc3c123dfcf26672a5191a4512edbf2b0be696b858f3db108a1520d716980525f9c337074e79b40165545bf085b4a5e450e12ea00378f8910554d11 → 01/c7/9fed088f1aa53fa657355ee4bd1e599f904462f4b8a3db8e485608b549e12ef6308765e15f7f9b12045741b43f2a9e58b145f9bc46c9ffdba93ea2f1e46f}

@@ -1318,7 +1318,7 @@
   "dist-tags": {
     "latest": "4.2.1"
   },
-  "_rev": "205-e8dbbc230b833780",
+  "_rev": "213-7b0be22f752c121b",
   "_id": "@smithy/util-hex-encoding",
   "readme": "# @smithy/util-hex-encoding\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/util-hex-encoding/latest.svg)](https://www.npmjs.com/package/@smithy/util-hex-encoding)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/util-hex-encoding.svg)](https://www.npmjs.com/package/@smithy/util-hex-encoding)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{66/6e/a488981d1f6306a581d999fd44c55a5d1da36d2836c9a145030f351253f75a7f0782ca369b5a67111fbda37285f88861fd61de853cd62247159a964c4f8a → 02/c6/07f729ac3faedfc7f7ea342a2e0498f82198cc4b4c1cffa9c3d816c5fb29dae8a70fcd7bdb159e16038509f5474d1b70120fd7dcba06fa6ea85fa3f46c0c}

@@ -483,7 +483,7 @@
   "dist-tags": {
     "latest": "1.0.5"
   },
-  "_rev": "265-25d021ef358221ae",
+  "_rev": "273-e479a94e2e063478",
   "_id": "format-util",
   "readme": "Table of Contents\n=================\n\n* [Format Util](#format-util)\n  * [Install](#install)\n  * [Usage](#usage)\n  * [Developer](#developer)\n    * [Test](#test)\n    * [Spec](#spec)\n    * [Cover](#cover)\n    * [Browserify](#browserify)\n    * [Lint](#lint)\n    * [Clean](#clean)\n    * [Docs](#docs)\n    * [Readme](#readme)\n  * [License](#license)\n\nFormat Util\n===========\n\n[<img src=\"https://travis-ci.org/tmpfs/format-util.svg\" alt=\"Build Status\">](https://travis-ci.org/tmpfs/format-util)\n[<img src=\"http://img.shields.io/npm/v/format-util.svg\" alt=\"npm version\">](https://npmjs.org/package/format-util)\n[<img src=\"https://coveralls.io/repos/tmpfs/format-util/badge.svg?branch=master&service=github&v=1\" alt=\"Coverage Status\">](https://coveralls.io/github/tmpfs/format-util?branch=master).\n\nLightweight format utility for the browser, based on `util.format()`.\n\n## Install\n\n```\nnpm i format-util\n```\n\n## Usage\n\n```javascript\nvar format = require('format-util')\n  , msg = format('%s', 'foo');\n```\n\n## Developer\n\n### Test\n\nRun the test specifications:\n\n```\nnpm test\n```\n\n### Spec\n\nCompile test specifications for the browser (open `test/index.html`):\n\n```\nnpm run spec\n```\n\n### Cover\n\nGenerate code coverage:\n\n```\nnpm run cover\n```\n\n### Browserify\n\nCreate a standalone browserify build:\n\n```\nnpm run browserify\n```\n\n### Lint\n\nLint the source tree with [jshint](http://jshint.com) and [jscs](http://jscs.info):\n\n```\nnpm run lint\n```\n\n### Clean\n\nRemove generated files:\n\n```\nnpm run clean\n```\n\n### Docs\n\nTo generate all documentation:\n\n```\nnpm run docs\n```\n\n### Readme\n\nGenerate the project readme file [mdp](https://github.com/tmpfs/mdp):\n\n```\nnpm run readme\n```\n\n## License\n\nEverything is [MIT](http://en.wikipedia.org/wiki/MIT_License). Read the [license](https://github.com/tmpfs/format-util/blob/master/LICENSE) if you feel inclined.\n\nGenerated by [mdp(1)](https://github.com/tmpfs/mdp).\n\n[node]: http://nodejs.org\n[npm]: http://www.npmjs.org\n[mdp]: https://github.com/tmpfs/mdp\n[zephyr]: https://github.com/tmpfs/zephyr\n[jshint]: http://jshint.com\n[jscs]: http://jscs.info",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{ec/39/7744438793a0731055f86ca84b5c83a3d740f49ef5166e11a5ec81004b3c456186ef22e91c0605b3e6d7dd9b425f5d7ced0b6c2c80485bd4c2e4eb42741f → 04/fe/03c5b5759854946dc0be4e2f031dda8803c929a57624dacb5cc8fb491de96ab4dffe011af7a17feeea4851703f2f83a22328e6fd8c21b0fa6b0a3cbeb1b1}

@@ -72569,12 +72569,154 @@
       },
       "_hasShrinkwrap": false,
       "contributors": []
+    },
+    "3.1000.0": {
+      "name": "@aws-sdk/client-sso",
+      "description": "AWS SDK for JavaScript Sso Client for Node.js, Browser and React Native",
+      "version": "3.1000.0",
+      "scripts": {
+        "build": "concurrently 'yarn:build:types' 'yarn:build:es' && yarn build:cjs",
+        "build:cjs": "node ../../scripts/compilation/inline client-sso",
+        "build:es": "tsc -p tsconfig.es.json",
+        "build:include:deps": "yarn g:turbo run build -F=\"$npm_package_name\"",
+        "build:types": "tsc -p tsconfig.types.json",
+        "build:types:downlevel": "downlevel-dts dist-types dist-types/ts3.4",
+        "clean": "premove dist-cjs dist-es dist-types tsconfig.cjs.tsbuildinfo tsconfig.es.tsbuildinfo tsconfig.types.tsbuildinfo",
+        "extract:docs": "api-extractor run --local",
+        "generate:client": "node ../../scripts/generate-clients/single-service --solo sso",
+        "test": "yarn g:vitest run --passWithNoTests",
+        "test:index": "tsc --noEmit ./test/index-types.ts && node ./test/index-objects.spec.mjs",
+        "test:integration": "yarn g:vitest run --passWithNoTests -c vitest.config.integ.mts",
+        "test:integration:watch": "yarn g:vitest run --passWithNoTests -c vitest.config.integ.mts",
+        "test:watch": "yarn g:vitest watch --passWithNoTests"
+      },
+      "main": "./dist-cjs/index.js",
+      "types": "./dist-types/index.d.ts",
+      "module": "./dist-es/index.js",
+      "sideEffects": false,
+      "dependencies": {
+        "@aws-crypto/sha256-browser": "5.2.0",
+        "@aws-crypto/sha256-js": "5.2.0",
+        "@aws-sdk/core": "^3.973.15",
+        "@aws-sdk/middleware-host-header": "^3.972.6",
+        "@aws-sdk/middleware-logger": "^3.972.6",
+        "@aws-sdk/middleware-recursion-detection": "^3.972.6",
+        "@aws-sdk/middleware-user-agent": "^3.972.15",
+        "@aws-sdk/region-config-resolver": "^3.972.6",
+        "@aws-sdk/types": "^3.973.4",
+        "@aws-sdk/util-endpoints": "^3.996.3",
+        "@aws-sdk/util-user-agent-browser": "^3.972.6",
+        "@aws-sdk/util-user-agent-node": "^3.973.0",
+        "@smithy/config-resolver": "^4.4.9",
+        "@smithy/core": "^3.23.6",
+        "@smithy/fetch-http-handler": "^5.3.11",
+        "@smithy/hash-node": "^4.2.10",
+        "@smithy/invalid-dependency": "^4.2.10",
+        "@smithy/middleware-content-length": "^4.2.10",
+        "@smithy/middleware-endpoint": "^4.4.20",
+        "@smithy/middleware-retry": "^4.4.37",
+        "@smithy/middleware-serde": "^4.2.11",
+        "@smithy/middleware-stack": "^4.2.10",
+        "@smithy/node-config-provider": "^4.3.10",
+        "@smithy/node-http-handler": "^4.4.12",
+        "@smithy/protocol-http": "^5.3.10",
+        "@smithy/smithy-client": "^4.12.0",
+        "@smithy/types": "^4.13.0",
+        "@smithy/url-parser": "^4.2.10",
+        "@smithy/util-base64": "^4.3.1",
+        "@smithy/util-body-length-browser": "^4.2.1",
+        "@smithy/util-body-length-node": "^4.2.2",
+        "@smithy/util-defaults-mode-browser": "^4.3.36",
+        "@smithy/util-defaults-mode-node": "^4.2.39",
+        "@smithy/util-endpoints": "^3.3.1",
+        "@smithy/util-middleware": "^4.2.10",
+        "@smithy/util-retry": "^4.2.10",
+        "@smithy/util-utf8": "^4.2.1",
+        "tslib": "^2.6.2"
+      },
+      "devDependencies": {
+        "@smithy/snapshot-testing": "^1.0.7",
+        "@tsconfig/node20": "20.1.8",
+        "@types/node": "^20.14.8",
+        "concurrently": "7.0.0",
+        "downlevel-dts": "0.10.1",
+        "premove": "4.0.0",
+        "typescript": "~5.8.3",
+        "vitest": "^4.0.17"
+      },
+      "engines": {
+        "node": ">=20.0.0"
+      },
+      "typesVersions": {
+        "<4.0": {
+          "dist-types/*": [
+            "dist-types/ts3.4/*"
+          ]
+        }
+      },
+      "author": {
+        "name": "AWS SDK for JavaScript Team",
+        "url": "https://aws.amazon.com/javascript/"
+      },
+      "license": "Apache-2.0",
+      "browser": {
+        "./dist-es/runtimeConfig": "./dist-es/runtimeConfig.browser"
+      },
+      "react-native": {
+        "./dist-es/runtimeConfig": "./dist-es/runtimeConfig.native"
+      },
+      "homepage": "https://github.com/aws/aws-sdk-js-v3/tree/main/clients/client-sso",
+      "repository": {
+        "type": "git",
+        "url": "git+https://github.com/aws/aws-sdk-js-v3.git",
+        "directory": "clients/client-sso"
+      },
+      "_id": "@aws-sdk/client-sso@3.1000.0",
+      "bugs": {
+        "url": "https://github.com/aws/aws-sdk-js-v3/issues"
+      },
+      "_nodeVersion": "20.19.5",
+      "_npmVersion": "10.8.2",
+      "dist": {
+        "integrity": "sha512-z7DNbLUU9fpmKcweZyjM2JtiNNe9nk1OT9n/GE+0od+Bp+ByKNYAxfdrSR7C6+zkwZWEWpjPPCdgPDCM8wfHaw==",
+        "shasum": "3e85a8fc7195582378f0a64e25ce2dd65ce38ca0",
+        "tarball": "https://verdaccio.mrsdev.ru/@aws-sdk%2fclient-sso/-/client-sso-3.1000.0.tgz",
+        "fileCount": 95,
+        "unpackedSize": 195454,
+        "signatures": [
+          {
+            "keyid": "SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U",
+            "sig": "MEQCIBULRJyjGRPFgh+XqWKKWI19+mE6b3fCaJeSjgkXUl3cAiB9d7zvMSEYbJZo1yXpmwakFLsuKTJBKm5dp0apeGF+Vw=="
+          }
+        ]
+      },
+      "_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/client-sso_3.1000.0_1772222780728_0.7289674382488134"
+      },
+      "_hasShrinkwrap": false,
+      "contributors": []
     }
   },
   "time": {
     "created": "2020-01-08T03:14:16.291Z",
     "1.0.0-alpha.1": "2020-01-08T03:14:16.692Z",
-    "modified": "2026-02-26T20:04:09.212Z",
+    "modified": "2026-02-27T20:06:21.045Z",
     "1.0.0-alpha.2": "2020-01-09T23:19:55.564Z",
     "1.0.0-alpha.3": "2020-01-10T05:11:09.168Z",
     "1.0.0-alpha.4": "2020-01-10T22:50:03.271Z",
@@ -73084,17 +73226,18 @@
     "3.996.0": "2026-02-23T19:59:48.661Z",
     "3.997.0": "2026-02-24T20:05:27.979Z",
     "3.998.0": "2026-02-25T20:05:40.863Z",
-    "3.999.0": "2026-02-26T20:04:09.064Z"
+    "3.999.0": "2026-02-26T20:04:09.064Z",
+    "3.1000.0": "2026-02-27T20:06:20.920Z"
   },
   "users": {},
   "dist-tags": {
     "alpha": "1.0.0-alpha.23",
-    "latest": "3.999.0",
+    "latest": "3.1000.0",
     "beta": "1.0.0-beta.5",
     "gamma": "1.0.0-gamma.11",
     "rc": "3.5.1-rc.0"
   },
-  "_rev": "324-efc58c9a99f69526",
+  "_rev": "333-545371db9c1ad45f",
   "_id": "@aws-sdk/client-sso",
   "readme": "<!-- generated file, do not edit directly -->\n\n# @aws-sdk/client-sso\n\n## Description\n\nAWS SDK for JavaScript SSO Client for Node.js, Browser and React Native.\n\n<p>AWS IAM Identity Center (successor to AWS Single Sign-On) Portal is a web service that makes it easy for you to assign user access to\nIAM Identity Center resources such as the AWS access portal. Users can get AWS account applications and roles\nassigned to them and get federated into the application.</p>\n<note>\n<p>Although AWS Single Sign-On was renamed, the <code>sso</code> and\n<code>identitystore</code> API namespaces will continue to retain their original name for\nbackward compatibility purposes. For more information, see <a href=\"https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html#renamed\">IAM Identity Center rename</a>.</p>\n</note>\n<p>This reference guide describes the IAM Identity Center Portal operations that you can call\nprogramatically and includes detailed information on data types and errors.</p>\n<note>\n<p>AWS provides SDKs that consist of libraries and sample code for various programming\nlanguages and platforms, such as Java, Ruby, .Net, iOS, or Android. The SDKs provide a\nconvenient way to create programmatic access to IAM Identity Center and other AWS services. For more\ninformation about the AWS SDKs, including how to download and install them, see <a href=\"http://aws.amazon.com/tools/\">Tools for Amazon Web Services</a>.</p>\n</note>\n\n## Installing\nTo install this package, simply type add or install @aws-sdk/client-sso\nusing your favorite package manager:\n- `npm install @aws-sdk/client-sso`\n- `yarn add @aws-sdk/client-sso`\n- `pnpm add @aws-sdk/client-sso`\n\n## Getting Started\n\n### Import\n\nThe AWS SDK is modulized by clients and commands.\nTo send a request, you only need to import the `SSOClient` and\nthe commands you need, for example `ListAccountsCommand`:\n\n```js\n// ES5 example\nconst { SSOClient, ListAccountsCommand } = require(\"@aws-sdk/client-sso\");\n```\n\n```ts\n// ES6+ example\nimport { SSOClient, ListAccountsCommand } from \"@aws-sdk/client-sso\";\n```\n\n### Usage\n\nTo send a request, you:\n\n- Initiate client with configuration (e.g. credentials, region).\n- Initiate command with input parameters.\n- Call `send` operation on client with command object as input.\n- If you are using a custom http handler, you may call `destroy()` to close open connections.\n\n```js\n// a client can be shared by different commands.\nconst client = new SSOClient({ region: \"REGION\" });\n\nconst params = { /** input parameters */ };\nconst command = new ListAccountsCommand(params);\n```\n\n#### Async/await\n\nWe recommend using [await](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/await)\noperator to wait for the promise returned by send operation as follows:\n\n```js\n// async/await.\ntry {\n  const data = await client.send(command);\n  // process data.\n} catch (error) {\n  // error handling.\n} finally {\n  // finally.\n}\n```\n\nAsync-await is clean, concise, intuitive, easy to debug and has better error handling\nas compared to using Promise chains or callbacks.\n\n#### Promises\n\nYou can also use [Promise chaining](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Using_promises#chaining)\nto execute send operation.\n\n```js\nclient.send(command).then(\n  (data) => {\n    // process data.\n  },\n  (error) => {\n    // error handling.\n  }\n);\n```\n\nPromises can also be called using `.catch()` and `.finally()` as follows:\n\n```js\nclient\n  .send(command)\n  .then((data) => {\n    // process data.\n  })\n  .catch((error) => {\n    // error handling.\n  })\n  .finally(() => {\n    // finally.\n  });\n```\n\n#### Callbacks\n\nWe do not recommend using callbacks because of [callback hell](http://callbackhell.com/),\nbut they are supported by the send operation.\n\n```js\n// callbacks.\nclient.send(command, (err, data) => {\n  // process err and data.\n});\n```\n\n#### v2 compatible style\n\nThe client can also send requests using v2 compatible style.\nHowever, it results in a bigger bundle size and may be dropped in next major version. More details in the blog post\non [modular packages in AWS SDK for JavaScript](https://aws.amazon.com/blogs/developer/modular-packages-in-aws-sdk-for-javascript/)\n\n```ts\nimport * as AWS from \"@aws-sdk/client-sso\";\nconst client = new AWS.SSO({ region: \"REGION\" });\n\n// async/await.\ntry {\n  const data = await client.listAccounts(params);\n  // process data.\n} catch (error) {\n  // error handling.\n}\n\n// Promises.\nclient\n  .listAccounts(params)\n  .then((data) => {\n    // process data.\n  })\n  .catch((error) => {\n    // error handling.\n  });\n\n// callbacks.\nclient.listAccounts(params, (err, data) => {\n  // process err and data.\n});\n```\n\n### Troubleshooting\n\nWhen the service returns an exception, the error will include the exception information,\nas well as response metadata (e.g. request id).\n\n```js\ntry {\n  const data = await client.send(command);\n  // process data.\n} catch (error) {\n  const { requestId, cfId, extendedRequestId } = error.$metadata;\n  console.log({ requestId, cfId, extendedRequestId });\n  /**\n   * The keys within exceptions are also parsed.\n   * You can access them by specifying exception names:\n   * if (error.name === 'SomeServiceException') {\n   *     const value = error.specialKeyInException;\n   * }\n   */\n}\n```\n\n## Getting Help\n\nPlease use these community resources for getting help.\nWe use the GitHub issues for tracking bugs and feature requests, but have limited bandwidth to address them.\n\n- Visit [Developer Guide](https://docs.aws.amazon.com/sdk-for-javascript/v3/developer-guide/welcome.html)\n  or [API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/index.html).\n- Check out the blog posts tagged with [`aws-sdk-js`](https://aws.amazon.com/blogs/developer/tag/aws-sdk-js/)\n  on AWS Developer Blog.\n- Ask a question on [StackOverflow](https://stackoverflow.com/questions/tagged/aws-sdk-js) and tag it with `aws-sdk-js`.\n- Join the AWS JavaScript community on [gitter](https://gitter.im/aws/aws-sdk-js-v3).\n- If it turns out that you may have found a bug, please [open an issue](https://github.com/aws/aws-sdk-js-v3/issues/new/choose).\n\nTo test your universal JavaScript code in Node.js, browser and react-native environments,\nvisit our [code samples repo](https://github.com/aws-samples/aws-sdk-js-tests).\n\n## Contributing\n\nThis client code is generated automatically. Any modifications will be overwritten the next time the `@aws-sdk/client-sso` package is updated.\nTo contribute to client you can check our [generate clients scripts](https://github.com/aws/aws-sdk-js-v3/tree/main/scripts/generate-clients).\n\n## License\n\nThis SDK is distributed under the\n[Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0),\nsee LICENSE for more information.\n\n## Client Commands (Operations List)\n\n<details>\n<summary>\nGetRoleCredentials\n</summary>\n\n[Command API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/sso/command/GetRoleCredentialsCommand/) / [Input](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-sso/Interface/GetRoleCredentialsCommandInput/) / [Output](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-sso/Interface/GetRoleCredentialsCommandOutput/)\n</details>\n<details>\n<summary>\nListAccountRoles\n</summary>\n\n[Command API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/sso/command/ListAccountRolesCommand/) / [Input](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-sso/Interface/ListAccountRolesCommandInput/) / [Output](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-sso/Interface/ListAccountRolesCommandOutput/)\n</details>\n<details>\n<summary>\nListAccounts\n</summary>\n\n[Command API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/sso/command/ListAccountsCommand/) / [Input](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-sso/Interface/ListAccountsCommandInput/) / [Output](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-sso/Interface/ListAccountsCommandOutput/)\n</details>\n<details>\n<summary>\nLogout\n</summary>\n\n[Command API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/sso/command/LogoutCommand/) / [Input](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-sso/Interface/LogoutCommandInput/) / [Output](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-sso/Interface/LogoutCommandOutput/)\n</details>",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{31/4e/22a2cf27c1e6b742b20ca946999019f1814d6db4c4f4dd488bc8caea51fda03c5d92c1e96ccb4a2ba9147eb283d4ecff556c610d15fb12f4df4bed03ae10 → 05/78/115897739f0338ec1280c94ee0afad2cd236030cd861d733343682c01865419cb04603953e4a2c545c74a1d9d082c5aec9fee786596edaf1dab8f414790e}

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

package/npm-cache/_cacache/content-v2/sha512/{f7/b4/6f49dc2727ef3ce0d9043e096216a4c40bd7c30769eb480ac951beae6bf0ad174c90dbd4ca5f673e47595d6a0bfbccef329c8c2addf9b35b38605c79b216 → 05/bc/4689d57c07a9aaeb735256cb4fb3216efcf0762a2fffa7cb5aff172bb03b44420325033dec1847f1b4948bb6287824c29b704552a1e219440d1784cbc8b1}

@@ -15525,7 +15525,7 @@
     "legacy-v10": "10.5.0",
     "legacy-v9": "9.3.5"
   },
-  "_rev": "4627-2f84765d9431ea90",
+  "_rev": "4697-13e9ade8f7cd57f9",
   "_id": "glob",
   "readme": "# Glob\n\nMatch files using the patterns the shell uses.\n\nThe most correct and second fastest glob implementation in\nJavaScript. (See [**Comparison to Other JavaScript Glob\nImplementations**](#comparisons-to-other-fnmatchglob-implementations)\nat the bottom of this readme.)\n\n![a fun cartoon logo made of glob\ncharacters](https://github.com/isaacs/node-glob/raw/main/logo/glob.png)\n\n## Usage\n\nInstall with npm\n\n```\nnpm i glob\n```\n\n> [!NOTE]\n> The npm package name is _not_ `node-glob` that's a\n> different thing that was abandoned years ago. Just `glob`.\n\n```js\n// load using import\nimport { glob, globSync, globStream, globStreamSync, Glob } from 'glob'\n// or using commonjs, that's fine, too\nconst {\n  glob,\n  globSync,\n  globStream,\n  globStreamSync,\n  Glob,\n} = require('glob')\n\n// the main glob() and globSync() resolve/return array of filenames\n\n// all js files, but don't look in node_modules\nconst jsfiles = await glob('**/*.js', { ignore: 'node_modules/**' })\n\n// pass in a signal to cancel the glob walk\nconst stopAfter100ms = await glob('**/*.css', {\n  signal: AbortSignal.timeout(100),\n})\n\n// multiple patterns supported as well\nconst images = await glob(['css/*.{png,jpeg}', 'public/*.{png,jpeg}'])\n\n// but of course you can do that with the glob pattern also\n// the sync function is the same, just returns a string[] instead\n// of Promise<string[]>\nconst imagesAlt = globSync('{css,public}/*.{png,jpeg}')\n\n// you can also stream them, this is a Minipass stream\nconst filesStream = globStream(['**/*.dat', 'logs/**/*.log'])\n\n// construct a Glob object if you wanna do it that way, which\n// allows for much faster walks if you have to look in the same\n// folder multiple times.\nconst g = new Glob('**/foo', {})\n// glob objects are async iterators, can also do globIterate() or\n// g.iterate(), same deal\nfor await (const file of g) {\n  console.log('found a foo file:', file)\n}\n// pass a glob as the glob options to reuse its settings and caches\nconst g2 = new Glob('**/bar', g)\n// sync iteration works as well\nfor (const file of g2) {\n  console.log('found a bar file:', file)\n}\n\n// you can also pass withFileTypes: true to get Path objects\n// these are like a fs.Dirent, but with some more added powers\n// check out https://isaacs.github.io/path-scurry/classes/PathBase.html\n// for more info on their API\nconst g3 = new Glob('**/baz/**', { withFileTypes: true })\ng3.stream().on('data', path => {\n  console.log(\n    'got a path object',\n    path.fullpath(),\n    path.isDirectory(),\n    path.readdirSync().map(e => e.name),\n  )\n})\n\n// if you use stat:true and withFileTypes, you can sort results\n// by things like modified time, filter by permission mode, etc.\n// All Stats fields will be available in that case. Slightly\n// slower, though.\n// For example:\nconst results = await glob('**', { stat: true, withFileTypes: true })\n\nconst timeSortedFiles = results\n  .sort((a, b) => a.mtimeMs - b.mtimeMs)\n  .map(path => path.fullpath())\n\nconst groupReadableFiles = results\n  .filter(path => path.mode & 0o040)\n  .map(path => path.fullpath())\n\n// custom ignores can be done like this, for example by saying\n// you'll ignore all markdown files, and all folders named 'docs'\nconst customIgnoreResults = await glob('**', {\n  ignore: {\n    ignored: p => /\\.md$/.test(p.name),\n    childrenIgnored: p => p.isNamed('docs'),\n  },\n})\n\n// another fun use case, only return files with the same name as\n// their parent folder, plus either `.ts` or `.js`\nconst folderNamedModules = await glob('**/*.{ts,js}', {\n  ignore: {\n    ignored: p => {\n      const pp = p.parent\n      return !(p.isNamed(pp.name + '.ts') || p.isNamed(pp.name + '.js'))\n    },\n  },\n})\n\n// find all files edited in the last hour, to do this, we ignore\n// all of them that are more than an hour old\nconst newFiles = await glob('**', {\n  // need stat so we have mtime\n  stat: true,\n  // only want the files, not the dirs\n  nodir: true,\n  ignore: {\n    ignored: p => {\n      return new Date() - p.mtime > 60 * 60 * 1000\n    },\n    // could add similar childrenIgnored here as well, but\n    // directory mtime is inconsistent across platforms, so\n    // probably better not to, unless you know the system\n    // tracks this reliably.\n  },\n})\n```\n\n> [!NOTE]\n> Glob patterns should always use `/` as a path separator,\n> even on Windows systems, as `\\` is used to escape glob\n> characters. If you wish to use `\\` as a path separator _instead\n> of_ using it as an escape character on Windows platforms, you may\n> set `windowsPathsNoEscape:true` in the options. In this mode,\n> special glob characters cannot be escaped, making it impossible\n> to match a literal `*` `?` and so on in filenames.\n\n## Command Line Interface\n\nThe glob CLI has been moved to the `glob-bin` package, and must\nbe installed separately, as of version 13.\n\n```\nnpm install glob-bin\n```\n\n## `glob(pattern: string | string[], options?: GlobOptions) => Promise<string[] | Path[]>`\n\nPerform an asynchronous glob search for the pattern(s) specified.\nReturns\n[Path](https://isaacs.github.io/path-scurry/classes/PathBase)\nobjects if the `withFileTypes` option is set to `true`. See below\nfor full options field desciptions.\n\n## `globSync(pattern: string | string[], options?: GlobOptions) => string[] | Path[]`\n\nSynchronous form of `glob()`.\n\nAlias: `glob.sync()`\n\n## `globIterate(pattern: string | string[], options?: GlobOptions) => AsyncGenerator<string>`\n\nReturn an async iterator for walking glob pattern matches.\n\nAlias: `glob.iterate()`\n\n## `globIterateSync(pattern: string | string[], options?: GlobOptions) => Generator<string>`\n\nReturn a sync iterator for walking glob pattern matches.\n\nAlias: `glob.iterate.sync()`, `glob.sync.iterate()`\n\n## `globStream(pattern: string | string[], options?: GlobOptions) => Minipass<string | Path>`\n\nReturn a stream that emits all the strings or `Path` objects and\nthen emits `end` when completed.\n\nAlias: `glob.stream()`\n\n## `globStreamSync(pattern: string | string[], options?: GlobOptions) => Minipass<string | Path>`\n\nSyncronous form of `globStream()`. Will read all the matches as\nfast as you consume them, even all in a single tick if you\nconsume them immediately, but will still respond to backpressure\nif they're not consumed immediately.\n\nAlias: `glob.stream.sync()`, `glob.sync.stream()`\n\n## `hasMagic(pattern: string | string[], options?: GlobOptions) => boolean`\n\nReturns `true` if the provided pattern contains any \"magic\" glob\ncharacters, given the options provided.\n\nBrace expansion is not considered \"magic\" unless the\n`magicalBraces` option is set, as brace expansion just turns one\nstring into an array of strings. So a pattern like `'x{a,b}y'`\nwould return `false`, because `'xay'` and `'xby'` both do not\ncontain any magic glob characters, and it's treated the same as\nif you had called it on `['xay', 'xby']`. When\n`magicalBraces:true` is in the options, brace expansion _is_\ntreated as a pattern having magic.\n\n## `escape(pattern: string, options?: GlobOptions) => string`\n\nEscape all magic characters in a glob pattern, so that it will\nonly ever match literal strings\n\nIf the `windowsPathsNoEscape` option is used, then characters are\nescaped by wrapping in `[]`, because a magic character wrapped in\na character class can only be satisfied by that exact character.\n\nSlashes (and backslashes in `windowsPathsNoEscape` mode) cannot\nbe escaped or unescaped.\n\n## `unescape(pattern: string, options?: GlobOptions) => string`\n\nUn-escape a glob string that may contain some escaped characters.\n\nIf the `windowsPathsNoEscape` option is used, then square-brace\nescapes are removed, but not backslash escapes. For example, it\nwill turn the string `'[*]'` into `*`, but it will not turn\n`'\\\\*'` into `'*'`, because `\\` is a path separator in\n`windowsPathsNoEscape` mode.\n\nWhen `windowsPathsNoEscape` is not set, then both brace escapes\nand backslash escapes are removed.\n\nSlashes (and backslashes in `windowsPathsNoEscape` mode) cannot\nbe escaped or unescaped.\n\n## Class `Glob`\n\nAn object that can perform glob pattern traversals.\n\n### `const g = new Glob(pattern: string | string[], options: GlobOptions)`\n\nOptions object is required.\n\nSee full options descriptions below.\n\n> [!NOTE]\n> A previous `Glob` object can be passed as the\n> `GlobOptions` to another `Glob` instantiation to re-use settings\n> and caches with a new pattern.\n\nTraversal functions can be called multiple times to run the walk\nagain.\n\n### `g.stream()`\n\nStream results asynchronously.\n\n### `g.streamSync()`\n\nStream results synchronously.\n\n### `g.iterate()`\n\nDefault async iteration function. Returns an AsyncGenerator that\niterates over the results.\n\n### `g.iterateSync()`\n\nDefault sync iteration function. Returns a Generator that\niterates over the results.\n\n### `g.walk()`\n\nReturns a Promise that resolves to the results array.\n\n### `g.walkSync()`\n\nReturns a results array.\n\n### Properties\n\nAll options are stored as properties on the `Glob` object.\n\n- `opts` The options provided to the constructor.\n- `patterns` An array of parsed immutable `Pattern` objects.\n\n## Options\n\nExported as `GlobOptions` TypeScript interface. A `GlobOptions`\nobject may be provided to any of the exported methods, and must\nbe provided to the `Glob` constructor.\n\nAll options are optional, boolean, and false by default, unless\notherwise noted.\n\nAll resolved options are added to the Glob object as properties.\n\nIf you are running many `glob` operations, you can pass a Glob\nobject as the `options` argument to a subsequent operation to\nshare the previously loaded cache.\n\n- `cwd` String path or `file://` string or URL object. The\n  current working directory in which to search. Defaults to\n  `process.cwd()`. See also: \"Windows, CWDs, Drive Letters, and\n  UNC Paths\", below.\n\n  This option may be either a string path or a `file://` URL\n  object or string.\n\n- `root` A string path resolved against the `cwd` option, which\n  is used as the starting point for absolute patterns that start\n  with `/`, (but not drive letters or UNC paths on Windows).\n\n  To start absolute and non-absolute patterns in the same path,\n  you can use `{root:''}`. However, be aware that on Windows\n  systems, a pattern like `x:/*` or `//host/share/*` will\n  _always_ start in the `x:/` or `//host/share` directory,\n  regardless of the `root` setting.\n\n> [!NOTE] This _doesn't_ necessarily limit the walk to the\n> `root` directory, and doesn't affect the cwd starting point\n> for non-absolute patterns. A pattern containing `..` will\n> still be able to traverse out of the root directory, if it\n> is not an actual root directory on the filesystem, and any\n> non-absolute patterns will be matched in the `cwd`. For\n> example, the pattern `/../*` with `{root:'/some/path'}`\n> will return all files in `/some`, not all files in\n> `/some/path`. The pattern `*` with `{root:'/some/path'}`\n> will return all the entries in the cwd, not the entries in\n> `/some/path`.\n\n- `windowsPathsNoEscape` Use `\\\\` as a path separator _only_, and\n  _never_ as an escape character. If set, all `\\\\` characters are\n  replaced with `/` in the pattern.\n\n> [!NOTE]\n> This makes it **impossible** to match against paths\n> containing literal glob pattern characters, but allows matching\n> with patterns constructed using `path.join()` and\n> `path.resolve()` on Windows platforms, mimicking the (buggy!)\n> behavior of Glob v7 and before on Windows. Please use with\n> caution, and be mindful of [the caveat below about Windows\n> paths](#windows). (For legacy reasons, this is also set if\n> `allowWindowsEscape` is set to the exact value `false`.)\n\n- `dot` Include `.dot` files in normal matches and `globstar`\n  matches. Note that an explicit dot in a portion of the pattern\n  will always match dot files.\n\n- `magicalBraces` Treat brace expansion like `{a,b}` as a \"magic\"\n  pattern. Has no effect if {@link nobrace} is set.\n\n  Only has effect on the {@link hasMagic} function, no effect on\n  glob pattern matching itself.\n\n- `dotRelative` Prepend all relative path strings with `./` (or\n  `.\\` on Windows).\n\n  Without this option, returned relative paths are \"bare\", so\n  instead of returning `'./foo/bar'`, they are returned as\n  `'foo/bar'`.\n\n  Relative patterns starting with `'../'` are not prepended with\n  `./`, even if this option is set.\n\n- `mark` Add a `/` character to directory matches. Note that this\n  requires additional stat calls.\n\n- `nobrace` Do not expand `{a,b}` and `{1..3}` brace sets.\n\n- `noglobstar` Do not match `**` against multiple filenames. (Ie,\n  treat it as a normal `*` instead.)\n\n- `noext` Do not match \"extglob\" patterns such as `+(a|b)`.\n\n- `nocase` Perform a case-insensitive match. This defaults to\n  `true` on macOS and Windows systems, and `false` on all others.\n\n> [!NOTE]\n> `nocase` should only be explicitly set when it is known that\n> the filesystem's case sensitivity differs from the platform\n> default. If set `true` on case-sensitive file systems, or\n> `false` on case-insensitive file systems, then the walk may\n> return more or less results than expected.\n>\n> As a shortcut to avoid excessive `RegExp` creations, `Glob`\n> will use string portions as-is to `readdir()` calls while doing\n> its traversal. If you are setting a `nocase: true` match on a\n> file system that is in fact case sensitive, then this will\n> result in matches not being found that you might expect,\n> because for example the pattern `Foo/*` will fail to read the\n> `FOO/` or `foo/` directories.\n>\n> On the other hand, if you set `nocase: false` on a\n> case-_insensitive_ system, then the opposite problem occurs:\n> `Foo/*` will match `foo/bar`, but because we only detect the\n> existence of the `foo/` folder by successfully performing a\n> `readdir`, there's no way to know what the \"real\" case is, and\n> the match will be reported as `Foo/bar`, using the case of the\n> string portion of the glob pattern.\n>\n> The default is usually correct, however it _is_ possible to\n> mount file systems with a different case-sensitivity from the\n> host system. If you know this is the case, set this flag\n> appropriately to the file system you are searching.\n\n- `maxDepth` Specify a number to limit the depth of the directory\n  traversal to this many levels below the `cwd`.\n\n- `matchBase` Perform a basename-only match if the pattern does\n  not contain any slash characters. That is, `*.js` would be\n  treated as equivalent to `**/*.js`, matching all js files in\n  all directories.\n\n- `nodir` Do not match directories, only files. (Note: to match\n  _only_ directories, put a `/` at the end of the pattern.)\n\n> [!NOTE]\n> When `follow` and `nodir` are both set, then symbolic\n> links to directories are also omitted.\n\n- `stat` Call `lstat()` on all entries, whether required or not\n  to determine whether it's a valid match. When used with\n  `withFileTypes`, this means that matches will include data such\n  as modified time, permissions, and so on. Note that this will\n  incur a performance cost due to the added system calls.\n\n- `ignore` string or string[], or an object with `ignored` and\n  `childrenIgnored` methods.\n\n  If a string or string[] is provided, then this is treated as\n  a glob pattern or array of glob patterns to exclude from\n  matches. To ignore all children within a directory, as well\n  as the entry itself, append `'/**'` to the ignore pattern.\n\n  If an object is provided that has `ignored(path)` and/or\n  `childrenIgnored(path)` methods, then these methods will be\n  called to determine whether any Path is a match or if its\n  children should be traversed, respectively.\n\n  The `path` argument to the methods will be a\n  [`path-scurry`](https://isaacs.github.io/path-scurry/index.html)\n  [`Path`](https://isaacs.github.io/path-scurry/classes/PathBase)\n  object, which extends\n  [`fs.Dirent`](https://nodejs.org/docs/latest/api/fs.html#class-fsdirent)\n  with additional useful methods like\n  [`.fullpath()`](https://isaacs.github.io/path-scurry/classes/PathBase.html#fullpath),\n  [`.relative()`](https://isaacs.github.io/path-scurry/classes/PathBase.html#relative),\n  and more.\n\n> [!NOTE]\n> `ignore` patterns are _always_ in `dot:true` mode,\n> regardless of any other settings.\n\n- `follow` Follow symlinked directories when expanding `**`\n  patterns. This can result in a lot of duplicate references in\n  the presence of cyclic links, and make performance quite bad.\n\n  By default, a `**` in a pattern will follow 1 symbolic link if\n  it is not the first item in the pattern, or none if it is the\n  first item in the pattern, following the same behavior as Bash.\n\n> [!NOTE]\n> When `follow` and `nodir` are both set, then symbolic\n> links to directories are also omitted.\n\n- `realpath` Set to true to call `fs.realpath` on all of the\n  results. In the case of an entry that cannot be resolved, the\n  entry is omitted. This incurs a slight performance penalty, of\n  course, because of the added system calls.\n\n- `absolute` Set to true to always receive absolute paths for\n  matched files. Set to `false` to always receive relative paths\n  for matched files.\n\n  By default, when this option is not set, absolute paths are\n  returned for patterns that are absolute, and otherwise paths\n  are returned that are relative to the `cwd` setting.\n\n  This does _not_ make an extra system call to get the realpath,\n  it only does string path resolution.\n\n  `absolute` may not be used along with `withFileTypes`.\n\n- `posix` Set to true to use `/` as the path separator in\n  returned results. On POSIX systems, this has no effect. On\n  Windows systems, this will return `/` delimited path results,\n  and absolute paths will be returned in their fully resolved UNC\n  path form, e.g. instead of `'C:\\\\foo\\\\bar'`, it will return\n  `//?/C:/foo/bar`.\n\n- `platform` Defaults to the value of `process.platform` if\n  available, or `'linux'` if not. Setting `platform:'win32'` on\n  non-Windows systems may cause strange behavior.\n\n- `withFileTypes` Return\n  [`path-scurry`](http://npm.im/path-scurry)\n  [`Path`](https://isaacs.github.io/path-scurry/classes/PathBase.html)\n  objects instead of strings. These are similar to a NodeJS\n  `fs.Dirent` object, but with additional methods and properties.\n\n  `withFileTypes` may not be used along with `absolute`.\n\n- `signal` An AbortSignal which will cancel the Glob walk when\n  triggered.\n\n- `fs` An override object to pass in custom filesystem methods.\n  See [`path-scurry`\n  docs](https://isaacs.github.io/path-scurry/interfaces/FSOption.html)\n  for what can be overridden.\n\n- `scurry` A\n  [`PathScurry`](https://isaacs.github.io/path-scurry/classes/PathScurryBase.html)\n  object used to traverse the file system. If the `nocase` option\n  is set explicitly, then any provided `scurry` object must match\n  this setting.\n\n- `includeChildMatches` boolean, default `true`. Do not match any\n  children of any matches. For example, the pattern `**\\/foo`\n  would match `a/foo`, but not `a/foo/b/foo` in this mode.\n\n  This is especially useful for cases like \"find all\n  `node_modules` folders, but not the ones in `node_modules`\".\n\n  In order to support this, the `Ignore` implementation must\n  support an `add(pattern: string)` method. If using the default\n  `Ignore` class, then this is fine, but if this is set to\n  `false`, and a custom `Ignore` is provided that does not have\n  an `add()` method, then it will throw an error.\n\n  For example:\n\n  ```js\n  const results = await glob(\n    [\n      // likely to match first, since it's just a stat\n      'a/b/c/d/e/f',\n\n      // this pattern is more complicated! It must to various readdir()\n      // calls and test the results against a regular expression, and that\n      // is certainly going to take a little bit longer.\n      //\n      // So, later on, it encounters a match at 'a/b/c/d/e', but it's too\n      // late to ignore a/b/c/d/e/f, because it's already been emitted.\n      'a/[bdf]/?/[a-z]/*',\n    ],\n    { includeChildMatches: false },\n  )\n  ```\n\n  It's best to only set this to `false` if you can be reasonably\n  sure that no components of the pattern will potentially match\n  one another's file system descendants, or if the occasional\n  included child entry will not cause problems.\n\n> [!NOTE]\n> It _only_ ignores matches that would be a descendant\n> of a previous match, and only if that descendant is matched\n> _after_ the ancestor is encountered. Since the file system walk\n> happens in indeterminate order, it's possible that a match will\n> already be added before its ancestor, if multiple or braced\n> patterns are used.\n\n- `braceExpandMax` number, defaults to `10_000`. This is the\n  maximum number of `{x,y,...}` patterns to expand. It is very\n  unlikely that you'll need more than this, and setting it higher\n  exposes the system to out-of-memory errors.\n\n## Glob Primer\n\nMuch more information about glob pattern expansion can be found\nby running `man bash` and searching for `Pattern Matching`.\n\n\"Globs\" are the patterns you type when you do stuff like `ls\n*.js` on the command line, or put `build/*` in a `.gitignore`\nfile.\n\nBefore parsing the path part patterns, braced sections are\nexpanded into a set. Braced sections start with `{` and end with\n`}`, with 2 or more comma-delimited sections within. Braced\nsections may contain slash characters, so `a{/b/c,bcd}` would\nexpand into `a/b/c` and `abcd`.\n\nThe following characters have special magic meaning when used in\na path portion. With the exception of `**`, none of these match\npath separators (ie, `/` on all platforms, and `\\` on Windows).\n\n- `*` Matches 0 or more characters in a single path portion.\n  When alone in a path portion, it must match at least 1\n  character. If `dot:true` is not specified, then `*` will not\n  match against a `.` character at the start of a path portion.\n- `?` Matches 1 character. If `dot:true` is not specified, then\n  `?` will not match against a `.` character at the start of a\n  path portion.\n- `[...]` Matches a range of characters, similar to a RegExp\n  range. If the first character of the range is `!` or `^` then\n  it matches any character not in the range. If the first\n  character is `]`, then it will be considered the same as `\\]`,\n  rather than the end of the character class.\n- `!(pattern|pattern|pattern)` Matches anything that does not\n  match any of the patterns provided. May _not_ contain `/`\n  characters. Similar to `*`, if alone in a path portion, then\n  the path portion must have at least one character.\n- `?(pattern|pattern|pattern)` Matches zero or one occurrence of\n  the patterns provided. May _not_ contain `/` characters.\n- `+(pattern|pattern|pattern)` Matches one or more occurrences of\n  the patterns provided. May _not_ contain `/` characters.\n- `*(a|b|c)` Matches zero or more occurrences of the patterns\n  provided. May _not_ contain `/` characters.\n- `@(pattern|pat*|pat?erN)` Matches exactly one of the patterns\n  provided. May _not_ contain `/` characters.\n- `**` If a \"globstar\" is alone in a path portion, then it\n  matches zero or more directories and subdirectories searching\n  for matches. It does not crawl symlinked directories, unless\n  `{follow:true}` is passed in the options object. A pattern\n  like `a/b/**` will only match `a/b` if it is a directory.\n  Follows 1 symbolic link if not the first item in the pattern,\n  or 0 if it is the first item, unless `follow:true` is set, in\n  which case it follows all symbolic links.\n\n`[:class:]` patterns are supported by this implementation, but\n`[=c=]` and `[.symbol.]` style class patterns are not.\n\n### Dots\n\nIf a file or directory path portion has a `.` as the first\ncharacter, then it will not match any glob pattern unless that\npattern's corresponding path part also has a `.` as its first\ncharacter.\n\nFor example, the pattern `a/.*/c` would match the file at\n`a/.b/c`. However the pattern `a/*/c` would not, because `*` does\nnot start with a dot character.\n\nYou can make glob treat dots as normal characters by setting\n`dot:true` in the options.\n\n### Basename Matching\n\nIf you set `matchBase:true` in the options, and the pattern has\nno slashes in it, then it will seek for any file anywhere in the\ntree with a matching basename. For example, `*.js` would match\n`test/simple/basic.js`.\n\n### Empty Sets\n\nIf no matching files are found, then an empty array is returned.\nThis differs from the shell, where the pattern itself is\nreturned. For example:\n\n```sh\n$ echo a*s*d*f\na*s*d*f\n```\n\n## Comparisons to other fnmatch/glob implementations\n\nWhile strict compliance with the existing standards is a\nworthwhile goal, some discrepancies exist between node-glob and\nother implementations, and are intentional.\n\nThe double-star character `**` is supported by default, unless\nthe `noglobstar` flag is set. This is supported in the manner of\nbsdglob and bash 5, where `**` only has special significance if\nit is the only thing in a path part. That is, `a/**/b` will match\n`a/x/y/b`, but `a/**b` will not.\n\n> [!NOTE]\n> Symlinked directories are not traversed as part of a\n> `**`, though their contents may match against subsequent portions\n> of the pattern. This prevents infinite loops and duplicates and\n> the like. You can force glob to traverse symlinks with `**` by\n> setting `{follow:true}` in the options.\n\nThere is no equivalent of the `nonull` option. A pattern that\ndoes not find any matches simply resolves to nothing. (An empty\narray, immediately ended stream, etc.)\n\nIf brace expansion is not disabled, then it is performed before\nany other interpretation of the glob pattern. Thus, a pattern\nlike `+(a|{b),c)}`, which would not be valid in bash or zsh, is\nexpanded **first** into the set of `+(a|b)` and `+(a|c)`, and\nthose patterns are checked for validity. Since those two are\nvalid, matching proceeds.\n\nThe character class patterns `[:class:]` (POSIX standard named\nclasses) style class patterns are supported and Unicode-aware,\nbut `[=c=]` (locale-specific character collation weight), and\n`[.symbol.]` (collating symbol), are not.\n\n### Repeated Slashes\n\nUnlike Bash and zsh, repeated `/` are always coalesced into a\nsingle path separator.\n\n### Comments and Negation\n\nPreviously, this module let you mark a pattern as a \"comment\" if\nit started with a `#` character, or a \"negated\" pattern if it\nstarted with a `!` character.\n\nThese options were deprecated in version 5, and removed in\nversion 6.\n\nTo specify things that should not match, use the `ignore` option.\n\n## Windows\n\n**Please only use forward-slashes in glob expressions.**\n\nThough Windows uses either `/` or `\\` as its path separator, only\n`/` characters are used by this glob implementation. You must use\nforward-slashes **only** in glob expressions. Back-slashes will\nalways be interpreted as escape characters, not path separators.\n\nResults from absolute patterns such as `/foo/*` are mounted onto\nthe root setting using `path.join`. On Windows, this will by\ndefault result in `/foo/*` matching `C:\\foo\\bar.txt`.\n\nTo automatically coerce all `\\` characters to `/` in pattern\nstrings, **thus making it impossible to escape literal glob\ncharacters**, you may set the `windowsPathsNoEscape` option to\n`true`.\n\n### Windows, CWDs, Drive Letters, and UNC Paths\n\nOn POSIX systems, when a pattern starts with `/`, any `cwd`\noption is ignored, and the traversal starts at `/`, plus any\nnon-magic path portions specified in the pattern.\n\nOn Windows systems, the behavior is similar, but the concept of\nan \"absolute path\" is somewhat more involved.\n\n#### UNC Paths\n\nA UNC path may be used as the start of a pattern on Windows\nplatforms. For example, a pattern like: `//?/x:/*` will return\nall file entries in the root of the `x:` drive. A pattern like\n`//ComputerName/Share/*` will return all files in the associated\nshare.\n\nUNC path roots are always compared case insensitively.\n\n#### Drive Letters\n\nA pattern starting with a drive letter, like `c:/*`, will search\nin that drive, regardless of any `cwd` option provided.\n\nIf the pattern starts with `/`, and is not a UNC path, and there\nis an explicit `cwd` option set with a drive letter, then the\ndrive letter in the `cwd` is used as the root of the directory\ntraversal.\n\nFor example, `glob('/tmp', { cwd: 'c:/any/thing' })` will return\n`['c:/tmp']` as the result.\n\nIf an explicit `cwd` option is not provided, and the pattern\nstarts with `/`, then the traversal will run on the root of the\ndrive provided as the `cwd` option. (That is, it is the result of\n`path.resolve('/')`.)\n\n## Race Conditions\n\nGlob searching, by its very nature, is susceptible to race\nconditions, since it relies on directory walking.\n\nAs a result, it is possible that a file that exists when glob\nlooks for it may have been deleted or modified by the time it\nreturns the result.\n\nBy design, this implementation caches all readdir calls that it\nmakes, in order to cut down on system overhead. However, this\nalso makes it even more susceptible to races, especially if the\ncache object is reused between glob calls.\n\nUsers are thus advised not to use a glob result as a guarantee of\nfilesystem state in the face of rapid changes. For the vast\nmajority of operations, this is never a problem.\n\n### See Also:\n\n- `man sh`\n- `man bash` [Pattern\n  Matching](https://www.gnu.org/software/bash/manual/html_node/Pattern-Matching.html)\n- `man 3 fnmatch`\n- `man 5 gitignore`\n- [minimatch documentation](https://github.com/isaacs/minimatch)\n\n## Glob Logo\n\nGlob's logo was created by [Tanya\nBrassie](http://tanyabrassie.com/). Logo files can be found\n[here](https://github.com/isaacs/node-glob/tree/master/logo).\n\nThe logo is licensed under a [Creative Commons\nAttribution-ShareAlike 4.0 International\nLicense](https://creativecommons.org/licenses/by-sa/4.0/).\n\n## Contributing\n\nAny change to behavior (including bugfixes) must come with a\ntest.\n\nPatches that fail tests or reduce performance will be rejected.\n\n```sh\n# to run tests\nnpm test\n\n# to re-generate test fixtures\nnpm run test-regen\n\n# run the benchmarks\nnpm run bench\n\n# to profile javascript\nnpm run prof\n```\n\n## Comparison to Other JavaScript Glob Implementations\n\n**tl;dr**\n\n- If you want glob matching that is as faithful as possible to\n  Bash pattern expansion semantics, and as fast as possible\n  within that constraint, _use this module_.\n- If you are reasonably sure that the patterns you will encounter\n  are relatively simple, and want the absolutely fastest glob\n  matcher out there, _use [fast-glob](http://npm.im/fast-glob)_.\n- If you are reasonably sure that the patterns you will encounter\n  are relatively simple, and want the convenience of\n  automatically respecting `.gitignore` files, _use\n  [globby](http://npm.im/globby)_.\n\nThere are some other glob matcher libraries on npm, but these\nthree are (in my opinion, as of 2023) the best.\n\n---\n\n**full explanation**\n\nEvery library reflects a set of opinions and priorities in the\ntrade-offs it makes. Other than this library, I can personally\nrecommend both [globby](http://npm.im/globby) and\n[fast-glob](http://npm.im/fast-glob), though they differ in their\nbenefits and drawbacks.\n\nBoth have very nice APIs and are reasonably fast.\n\n`fast-glob` is, as far as I am aware, the fastest glob\nimplementation in JavaScript today. However, there are many\ncases where the choices that `fast-glob` makes in pursuit of\nspeed mean that its results differ from the results returned by\nBash and other sh-like shells, which may be surprising.\n\nIn my testing, `fast-glob` is around 10-20% faster than this\nmodule when walking over 200k files nested 4 directories\ndeep[1](#fn-webscale). However, there are some inconsistencies\nwith Bash matching behavior that this module does not suffer\nfrom:\n\n- `**` only matches files, not directories\n- `..` path portions are not handled unless they appear at the\n  start of the pattern\n- `./!(<pattern>)` will not match any files that _start_ with\n  `<pattern>`, even if they do not match `<pattern>`. For\n  example, `!(9).txt` will not match `9999.txt`.\n- Some brace patterns in the middle of a pattern will result in\n  failing to find certain matches.\n- Extglob patterns are allowed to contain `/` characters.\n\nGlobby exhibits all of the same pattern semantics as fast-glob,\n(as it is a wrapper around fast-glob) and is slightly slower than\nnode-glob (by about 10-20% in the benchmark test set, or in other\nwords, anywhere from 20-50% slower than fast-glob). However, it\nadds some API conveniences that may be worth the costs.\n\n- Support for `.gitignore` and other ignore files.\n- Support for negated globs (ie, patterns starting with `!`\n  rather than using a separate `ignore` option).\n\nThe priority of this module is \"correctness\" in the sense of\nperforming a glob pattern expansion as faithfully as possible to\nthe behavior of Bash and other sh-like shells, with as much speed\nas possible.\n\n> [!NOTE]\n> Prior versions of `node-glob` are _not_ on this list.\n> Former versions of this module are far too slow for any cases\n> where performance matters at all, and were designed with APIs\n> that are extremely dated by current JavaScript standards.\n\n---\n\n<small id=\"fn-webscale\">[1]: In the cases where this module\nreturns results and `fast-glob` doesn't, it's even faster, of\ncourse.</small>\n\n![lumpy space princess saying 'oh my GLOB'](https://github.com/isaacs/node-glob/raw/main/oh-my-glob.gif)\n\n### Benchmark Results\n\nThe first number is time, smaller is better.\n\nThe second number is the count of results returned.\n\n```\n--- pattern: '**' ---\n~~ sync ~~\nnode fast-glob sync             0m0.598s  200364\nnode globby sync                0m0.765s  200364\nnode current globSync mjs       0m0.683s  222656\nnode current glob syncStream    0m0.649s  222656\n~~ async ~~\nnode fast-glob async            0m0.350s  200364\nnode globby async               0m0.509s  200364\nnode current glob async mjs     0m0.463s  222656\nnode current glob stream        0m0.411s  222656\n\n--- pattern: '**/..' ---\n~~ sync ~~\nnode fast-glob sync             0m0.486s  0\nnode globby sync                0m0.769s  200364\nnode current globSync mjs       0m0.564s  2242\nnode current glob syncStream    0m0.583s  2242\n~~ async ~~\nnode fast-glob async            0m0.283s  0\nnode globby async               0m0.512s  200364\nnode current glob async mjs     0m0.299s  2242\nnode current glob stream        0m0.312s  2242\n\n--- pattern: './**/0/**/0/**/0/**/0/**/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.490s  10\nnode globby sync                0m0.517s  10\nnode current globSync mjs       0m0.540s  10\nnode current glob syncStream    0m0.550s  10\n~~ async ~~\nnode fast-glob async            0m0.290s  10\nnode globby async               0m0.296s  10\nnode current glob async mjs     0m0.278s  10\nnode current glob stream        0m0.302s  10\n\n--- pattern: './**/[01]/**/[12]/**/[23]/**/[45]/**/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.500s  160\nnode globby sync                0m0.528s  160\nnode current globSync mjs       0m0.556s  160\nnode current glob syncStream    0m0.573s  160\n~~ async ~~\nnode fast-glob async            0m0.283s  160\nnode globby async               0m0.301s  160\nnode current glob async mjs     0m0.306s  160\nnode current glob stream        0m0.322s  160\n\n--- pattern: './**/0/**/0/**/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.502s  5230\nnode globby sync                0m0.527s  5230\nnode current globSync mjs       0m0.544s  5230\nnode current glob syncStream    0m0.557s  5230\n~~ async ~~\nnode fast-glob async            0m0.285s  5230\nnode globby async               0m0.305s  5230\nnode current glob async mjs     0m0.304s  5230\nnode current glob stream        0m0.310s  5230\n\n--- pattern: '**/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.580s  200023\nnode globby sync                0m0.771s  200023\nnode current globSync mjs       0m0.685s  200023\nnode current glob syncStream    0m0.649s  200023\n~~ async ~~\nnode fast-glob async            0m0.349s  200023\nnode globby async               0m0.509s  200023\nnode current glob async mjs     0m0.427s  200023\nnode current glob stream        0m0.388s  200023\n\n--- pattern: '{**/*.txt,**/?/**/*.txt,**/?/**/?/**/*.txt,**/?/**/?/**/?/**/*.txt,**/?/**/?/**/?/**/?/**/*.txt}' ---\n~~ sync ~~\nnode fast-glob sync             0m0.589s  200023\nnode globby sync                0m0.771s  200023\nnode current globSync mjs       0m0.716s  200023\nnode current glob syncStream    0m0.684s  200023\n~~ async ~~\nnode fast-glob async            0m0.351s  200023\nnode globby async               0m0.518s  200023\nnode current glob async mjs     0m0.462s  200023\nnode current glob stream        0m0.468s  200023\n\n--- pattern: '**/5555/0000/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.496s  1000\nnode globby sync                0m0.519s  1000\nnode current globSync mjs       0m0.539s  1000\nnode current glob syncStream    0m0.567s  1000\n~~ async ~~\nnode fast-glob async            0m0.285s  1000\nnode globby async               0m0.299s  1000\nnode current glob async mjs     0m0.305s  1000\nnode current glob stream        0m0.301s  1000\n\n--- pattern: './**/0/**/../[01]/**/0/../**/0/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.484s  0\nnode globby sync                0m0.507s  0\nnode current globSync mjs       0m0.577s  4880\nnode current glob syncStream    0m0.586s  4880\n~~ async ~~\nnode fast-glob async            0m0.280s  0\nnode globby async               0m0.298s  0\nnode current glob async mjs     0m0.327s  4880\nnode current glob stream        0m0.324s  4880\n\n--- pattern: '**/????/????/????/????/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.547s  100000\nnode globby sync                0m0.673s  100000\nnode current globSync mjs       0m0.626s  100000\nnode current glob syncStream    0m0.618s  100000\n~~ async ~~\nnode fast-glob async            0m0.315s  100000\nnode globby async               0m0.414s  100000\nnode current glob async mjs     0m0.366s  100000\nnode current glob stream        0m0.345s  100000\n\n--- pattern: './{**/?{/**/?{/**/?{/**/?,,,,},,,,},,,,},,,}/**/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.588s  100000\nnode globby sync                0m0.670s  100000\nnode current globSync mjs       0m0.717s  200023\nnode current glob syncStream    0m0.687s  200023\n~~ async ~~\nnode fast-glob async            0m0.343s  100000\nnode globby async               0m0.418s  100000\nnode current glob async mjs     0m0.519s  200023\nnode current glob stream        0m0.451s  200023\n\n--- pattern: '**/!(0|9).txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.573s  160023\nnode globby sync                0m0.731s  160023\nnode current globSync mjs       0m0.680s  180023\nnode current glob syncStream    0m0.659s  180023\n~~ async ~~\nnode fast-glob async            0m0.345s  160023\nnode globby async               0m0.476s  160023\nnode current glob async mjs     0m0.427s  180023\nnode current glob stream        0m0.388s  180023\n\n--- pattern: './{*/**/../{*/**/../{*/**/../{*/**/../{*/**,,,,},,,,},,,,},,,,},,,,}/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.483s  0\nnode globby sync                0m0.512s  0\nnode current globSync mjs       0m0.811s  200023\nnode current glob syncStream    0m0.773s  200023\n~~ async ~~\nnode fast-glob async            0m0.280s  0\nnode globby async               0m0.299s  0\nnode current glob async mjs     0m0.617s  200023\nnode current glob stream        0m0.568s  200023\n\n--- pattern: './*/**/../*/**/../*/**/../*/**/../*/**/../*/**/../*/**/../*/**/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.485s  0\nnode globby sync                0m0.507s  0\nnode current globSync mjs       0m0.759s  200023\nnode current glob syncStream    0m0.740s  200023\n~~ async ~~\nnode fast-glob async            0m0.281s  0\nnode globby async               0m0.297s  0\nnode current glob async mjs     0m0.544s  200023\nnode current glob stream        0m0.464s  200023\n\n--- pattern: './*/**/../*/**/../*/**/../*/**/../*/**/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.486s  0\nnode globby sync                0m0.513s  0\nnode current globSync mjs       0m0.734s  200023\nnode current glob syncStream    0m0.696s  200023\n~~ async ~~\nnode fast-glob async            0m0.286s  0\nnode globby async               0m0.296s  0\nnode current glob async mjs     0m0.506s  200023\nnode current glob stream        0m0.483s  200023\n\n--- pattern: './0/**/../1/**/../2/**/../3/**/../4/**/../5/**/../6/**/../7/**/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.060s  0\nnode globby sync                0m0.074s  0\nnode current globSync mjs       0m0.067s  0\nnode current glob syncStream    0m0.066s  0\n~~ async ~~\nnode fast-glob async            0m0.060s  0\nnode globby async               0m0.075s  0\nnode current glob async mjs     0m0.066s  0\nnode current glob stream        0m0.067s  0\n\n--- pattern: './**/?/**/?/**/?/**/?/**/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.568s  100000\nnode globby sync                0m0.651s  100000\nnode current globSync mjs       0m0.619s  100000\nnode current glob syncStream    0m0.617s  100000\n~~ async ~~\nnode fast-glob async            0m0.332s  100000\nnode globby async               0m0.409s  100000\nnode current glob async mjs     0m0.372s  100000\nnode current glob stream        0m0.351s  100000\n\n--- pattern: '**/*/**/*/**/*/**/*/**' ---\n~~ sync ~~\nnode fast-glob sync             0m0.603s  200113\nnode globby sync                0m0.798s  200113\nnode current globSync mjs       0m0.730s  222137\nnode current glob syncStream    0m0.693s  222137\n~~ async ~~\nnode fast-glob async            0m0.356s  200113\nnode globby async               0m0.525s  200113\nnode current glob async mjs     0m0.508s  222137\nnode current glob stream        0m0.455s  222137\n\n--- pattern: './**/*/**/*/**/*/**/*/**/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.622s  200000\nnode globby sync                0m0.792s  200000\nnode current globSync mjs       0m0.722s  200000\nnode current glob syncStream    0m0.695s  200000\n~~ async ~~\nnode fast-glob async            0m0.369s  200000\nnode globby async               0m0.527s  200000\nnode current glob async mjs     0m0.502s  200000\nnode current glob stream        0m0.481s  200000\n\n--- pattern: '**/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.588s  200023\nnode globby sync                0m0.771s  200023\nnode current globSync mjs       0m0.684s  200023\nnode current glob syncStream    0m0.658s  200023\n~~ async ~~\nnode fast-glob async            0m0.352s  200023\nnode globby async               0m0.516s  200023\nnode current glob async mjs     0m0.432s  200023\nnode current glob stream        0m0.384s  200023\n\n--- pattern: './**/**/**/**/**/**/**/**/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.589s  200023\nnode globby sync                0m0.766s  200023\nnode current globSync mjs       0m0.682s  200023\nnode current glob syncStream    0m0.652s  200023\n~~ async ~~\nnode fast-glob async            0m0.352s  200023\nnode globby async               0m0.523s  200023\nnode current glob async mjs     0m0.436s  200023\nnode current glob stream        0m0.380s  200023\n\n--- pattern: '**/*/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.592s  200023\nnode globby sync                0m0.776s  200023\nnode current globSync mjs       0m0.691s  200023\nnode current glob syncStream    0m0.659s  200023\n~~ async ~~\nnode fast-glob async            0m0.357s  200023\nnode globby async               0m0.513s  200023\nnode current glob async mjs     0m0.471s  200023\nnode current glob stream        0m0.424s  200023\n\n--- pattern: '**/*/**/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.585s  200023\nnode globby sync                0m0.766s  200023\nnode current globSync mjs       0m0.694s  200023\nnode current glob syncStream    0m0.664s  200023\n~~ async ~~\nnode fast-glob async            0m0.350s  200023\nnode globby async               0m0.514s  200023\nnode current glob async mjs     0m0.472s  200023\nnode current glob stream        0m0.424s  200023\n\n--- pattern: '**/[0-9]/**/*.txt' ---\n~~ sync ~~\nnode fast-glob sync             0m0.544s  100000\nnode globby sync                0m0.636s  100000\nnode current globSync mjs       0m0.626s  100000\nnode current glob syncStream    0m0.621s  100000\n~~ async ~~\nnode fast-glob async            0m0.322s  100000\nnode globby async               0m0.404s  100000\nnode current glob async mjs     0m0.360s  100000\nnode current glob stream        0m0.352s  100000\n```",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{9d/91/705b2e1d8e9970cb9f4bfb0021e28b799cc4cb0c1d0e8f67fc5eb9c27666d146fdf3f07d7effb6c54e3734148b1429030eb59f9a3e59793488a51dfa4452 → 0f/2c/b2916fa52fea11bb6d59230e422750f488f741ccdc96583b409805a6ddb8373d01d2d499e2b4da1e1bb9b3000a6e3f871323d924d4d1b46a7b929a857a4c}

@@ -15079,7 +15079,7 @@
     "v7.4-backport": "7.4.5",
     "legacy-v10": "10.4.3"
   },
-  "_rev": "2672-94a9d4da30c4e6a5",
+  "_rev": "2702-6f4c229ce9732af6",
   "_id": "lru-cache",
   "readme": "# lru-cache\n\nA cache object that deletes the least-recently-used items.\n\nSpecify a max number of the most recently used items that you\nwant to keep, and this cache will keep that many of the most\nrecently accessed items.\n\nThis is not primarily a TTL cache, and does not make strong TTL\nguarantees. There is no preemptive pruning of expired items by\ndefault, but you _may_ set a TTL on the cache or on a single\n`set`. If you do so, it will treat expired items as missing, and\ndelete them when fetched. If you are more interested in TTL\ncaching than LRU caching, check out\n[@isaacs/ttlcache](http://npm.im/@isaacs/ttlcache).\n\nAs of version 7, this is one of the most performant LRU\nimplementations available in JavaScript, and supports a wide\ndiversity of use cases. However, note that using some of the\nfeatures will necessarily impact performance, by causing the\ncache to have to do more work. See the \"Performance\" section\nbelow.\n\n## Installation\n\n```bash\nnpm install lru-cache --save\n```\n\n## Usage\n\n```js\n// hybrid module, either works\nimport { LRUCache } from 'lru-cache'\n// or:\nconst { LRUCache } = require('lru-cache')\n// or in minified form for web browsers:\nimport { LRUCache } from 'http://unpkg.com/lru-cache@9/dist/mjs/index.min.mjs'\n\n// At least one of 'max', 'ttl', or 'maxSize' is required, to prevent\n// unsafe unbounded storage.\n//\n// In most cases, it's best to specify a max for performance, so all\n// the required memory allocation is done up-front.\n//\n// All the other options are optional, see the sections below for\n// documentation on what each one does.  Most of them can be\n// overridden for specific items in get()/set()\nconst options = {\n  max: 500,\n\n  // for use with tracking overall storage size\n  maxSize: 5000,\n  sizeCalculation: (value, key) => {\n    return 1\n  },\n\n  // for use when you need to clean up something when objects\n  // are evicted from the cache\n  dispose: (value, key, reason) => {\n    freeFromMemoryOrWhatever(value)\n  },\n\n  // for use when you need to know that an item is being inserted\n  // note that this does NOT allow you to prevent the insertion,\n  // it just allows you to know about it.\n  onInsert: (value, key, reason) => {\n    logInsertionOrWhatever(key, value)\n  },\n\n  // how long to live in ms\n  ttl: 1000 * 60 * 5,\n\n  // return stale items before removing from cache?\n  allowStale: false,\n\n  updateAgeOnGet: false,\n  updateAgeOnHas: false,\n\n  // async method to use for cache.fetch(), for\n  // stale-while-revalidate type of behavior\n  fetchMethod: async (key, staleValue, { options, signal, context }) => {},\n}\n\nconst cache = new LRUCache(options)\n\ncache.set('key', 'value')\ncache.get('key') // \"value\"\n\n// non-string keys ARE fully supported\n// but note that it must be THE SAME object, not\n// just a JSON-equivalent object.\nvar someObject = { a: 1 }\ncache.set(someObject, 'a value')\n// Object keys are not toString()-ed\ncache.set('[object Object]', 'a different value')\nassert.equal(cache.get(someObject), 'a value')\n// A similar object with same keys/values won't work,\n// because it's a different object identity\nassert.equal(cache.get({ a: 1 }), undefined)\n\ncache.clear() // empty the cache\n```\n\nIf you put more stuff in the cache, then less recently used items\nwill fall out. That's what an LRU cache is.\n\nFor full description of the API and all options, please see [the\nLRUCache typedocs](https://isaacs.github.io/node-lru-cache/)\n\n## Storage Bounds Safety\n\nThis implementation aims to be as flexible as possible, within\nthe limits of safe memory consumption and optimal performance.\n\nAt initial object creation, storage is allocated for `max` items.\nIf `max` is set to zero, then some performance is lost, and item\ncount is unbounded. Either `maxSize` or `ttl` _must_ be set if\n`max` is not specified.\n\nIf `maxSize` is set, then this creates a safe limit on the\nmaximum storage consumed, but without the performance benefits of\npre-allocation. When `maxSize` is set, every item _must_ provide\na size, either via the `sizeCalculation` method provided to the\nconstructor, or via a `size` or `sizeCalculation` option provided\nto `cache.set()`. The size of every item _must_ be a positive\ninteger.\n\nIf neither `max` nor `maxSize` are set, then `ttl` tracking must\nbe enabled. Note that, even when tracking item `ttl`, items are\n_not_ preemptively deleted when they become stale, unless\n`ttlAutopurge` is enabled. Instead, they are only purged the\nnext time the key is requested. Thus, if `ttlAutopurge`, `max`,\nand `maxSize` are all not set, then the cache will potentially\ngrow unbounded.\n\nIn this case, a warning is printed to standard error. Future\nversions may require the use of `ttlAutopurge` if `max` and\n`maxSize` are not specified.\n\nIf you truly wish to use a cache that is bound _only_ by TTL\nexpiration, consider using a `Map` object, and calling\n`setTimeout` to delete entries when they expire. It will perform\nmuch better than an LRU cache.\n\nHere is an implementation you may use, under the same\n[license](./LICENSE) as this package:\n\n```js\n// a storage-unbounded ttl cache that is not an lru-cache\nconst cache = {\n  data: new Map(),\n  timers: new Map(),\n  set: (k, v, ttl) => {\n    if (cache.timers.has(k)) {\n      clearTimeout(cache.timers.get(k))\n    }\n    cache.timers.set(\n      k,\n      setTimeout(() => cache.delete(k), ttl),\n    )\n    cache.data.set(k, v)\n  },\n  get: k => cache.data.get(k),\n  has: k => cache.data.has(k),\n  delete: k => {\n    if (cache.timers.has(k)) {\n      clearTimeout(cache.timers.get(k))\n    }\n    cache.timers.delete(k)\n    return cache.data.delete(k)\n  },\n  clear: () => {\n    cache.data.clear()\n    for (const v of cache.timers.values()) {\n      clearTimeout(v)\n    }\n    cache.timers.clear()\n  },\n}\n```\n\nIf that isn't to your liking, check out\n[@isaacs/ttlcache](http://npm.im/@isaacs/ttlcache).\n\n## Storing Undefined Values\n\nThis cache never stores undefined values, as `undefined` is used\ninternally in a few places to indicate that a key is not in the\ncache.\n\nYou may call `cache.set(key, undefined)`, but this is just\nan alias for `cache.delete(key)`. Note that this has the effect\nthat `cache.has(key)` will return _false_ after setting it to\nundefined.\n\n```js\ncache.set(myKey, undefined)\ncache.has(myKey) // false!\n```\n\nIf you need to track `undefined` values, and still note that the\nkey is in the cache, an easy workaround is to use a sigil object\nof your own.\n\n```js\nimport { LRUCache } from 'lru-cache'\nconst undefinedValue = Symbol('undefined')\nconst cache = new LRUCache(...)\nconst mySet = (key, value) =>\n  cache.set(key, value === undefined ? undefinedValue : value)\nconst myGet = (key, value) => {\n  const v = cache.get(key)\n  return v === undefinedValue ? undefined : v\n}\n```\n\n## Performance\n\nAs of January 2022, version 7 of this library is one of the most\nperformant LRU cache implementations in JavaScript.\n\nBenchmarks can be extremely difficult to get right. In\nparticular, the performance of set/get/delete operations on\nobjects will vary _wildly_ depending on the type of key used. V8\nis highly optimized for objects with keys that are short strings,\nespecially integer numeric strings. Thus any benchmark which\ntests _solely_ using numbers as keys will tend to find that an\nobject-based approach performs the best.\n\nNote that coercing _anything_ to strings to use as object keys is\nunsafe, unless you can be 100% certain that no other type of\nvalue will be used. For example:\n\n```js\nconst myCache = {}\nconst set = (k, v) => (myCache[k] = v)\nconst get = k => myCache[k]\n\nset({}, 'please hang onto this for me')\nset('[object Object]', 'oopsie')\n```\n\nAlso beware of \"Just So\" stories regarding performance. Garbage\ncollection of large (especially: deep) object graphs can be\nincredibly costly, with several \"tipping points\" where it\nincreases exponentially. As a result, putting that off until\nlater can make it much worse, and less predictable. If a library\nperforms well, but only in a scenario where the object graph is\nkept shallow, then that won't help you if you are using large\nobjects as keys.\n\nIn general, when attempting to use a library to improve\nperformance (such as a cache like this one), it's best to choose\nan option that will perform well in the sorts of scenarios where\nyou'll actually use it.\n\nThis library is optimized for repeated gets and minimizing\neviction time, since that is the expected need of a LRU. Set\noperations are somewhat slower on average than a few other\noptions, in part because of that optimization. It is assumed\nthat you'll be caching some costly operation, ideally as rarely\nas possible, so optimizing set over get would be unwise.\n\nIf performance matters to you:\n\n1. If it's at all possible to use small integer values as keys,\n   and you can guarantee that no other types of values will be\n   used as keys, then do that, and use a cache such as\n   [lru-fast](https://npmjs.com/package/lru-fast), or\n   [mnemonist's\n   LRUCache](https://yomguithereal.github.io/mnemonist/lru-cache)\n   which uses an Object as its data store.\n\n2. Failing that, if at all possible, use short non-numeric\n   strings (ie, less than 256 characters) as your keys, and use\n   [mnemonist's\n   LRUCache](https://yomguithereal.github.io/mnemonist/lru-cache).\n\n3. If the types of your keys will be anything else, especially\n   long strings, strings that look like floats, objects, or some\n   mix of types, or if you aren't sure, then this library will\n   work well for you.\n\n   If you do not need the features that this library provides\n   (like asynchronous fetching, a variety of TTL staleness\n   options, and so on), then [mnemonist's\n   LRUMap](https://yomguithereal.github.io/mnemonist/lru-map) is\n   a very good option, and just slightly faster than this module\n   (since it does considerably less).\n\n4. Do not use a `dispose` function, size tracking, or especially\n   ttl behavior, unless absolutely needed. These features are\n   convenient, and necessary in some use cases, and every attempt\n   has been made to make the performance impact minimal, but it\n   isn't nothing.\n\n## Testing\n\nWhen writing tests that involve TTL-related functionality, note\nthat this module creates an internal reference to the global\n`performance` or `Date` objects at import time. If you import it\nstatically at the top level, those references cannot be mocked or\noverridden in your test environment.\n\nTo avoid this, dynamically import the package within your tests\nso that the references are captured after your mocks are applied.\nFor example:\n\n```ts\n// ❌ Not recommended\nimport { LRUCache } from 'lru-cache'\n// mocking timers, e.g. jest.useFakeTimers()\n\n// ✅ Recommended for TTL tests\n// mocking timers, e.g. jest.useFakeTimers()\nconst { LRUCache } = await import('lru-cache')\n```\n\nThis ensures that your mocked timers or time sources are\nrespected when testing TTL behavior.\n\nAdditionally, you can pass in a `perf` option when creating your\nLRUCache instance. This option accepts any object with a `now`\nmethod that returns a number.\n\nFor example, this would be a very bare-bones time-mocking system\nyou could use in your tests, without any particular test\nframework:\n\n```ts\nimport { LRUCache } from 'lru-cache'\n\nlet myClockTime = 0\n\nconst cache = new LRUCache<string>({\n  max: 10,\n  ttl: 1000,\n  perf: {\n    now: () => myClockTime,\n  },\n})\n\n// run tests, updating myClockTime as needed\n```\n\n## Breaking Changes in Version 7\n\nThis library changed to a different algorithm and internal data\nstructure in version 7, yielding significantly better\nperformance, albeit with some subtle changes as a result.\n\nIf you were relying on the internals of LRUCache in version 6 or\nbefore, it probably will not work in version 7 and above.\n\n## Breaking Changes in Version 8\n\n- The `fetchContext` option was renamed to `context`, and may no\n  longer be set on the cache instance itself.\n- Rewritten in TypeScript, so pretty much all the types moved\n  around a lot.\n- The AbortController/AbortSignal polyfill was removed. For this\n  reason, **Node version 16.14.0 or higher is now required**.\n- Internal properties were moved to actual private class\n  properties.\n- Keys and values must not be `null` or `undefined`.\n- Minified export available at `'lru-cache/min'`, for both CJS\n  and MJS builds.\n\n## Breaking Changes in Version 9\n\n- Named export only, no default export.\n- AbortController polyfill returned, albeit with a warning when\n  used.\n\n## Breaking Changes in Version 10\n\n- `cache.fetch()` return type is now `Promise<V | undefined>`\n  instead of `Promise<V | void>`. This is an irrelevant change\n  practically speaking, but can require changes for TypeScript\n  users.\n\nFor more info, see the [change log](CHANGELOG.md).",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{4b/f3/ccdb5ad9794147e445af60ac586e43cf6de20f578e320115c49fa7296c958c64d210380cd9108b0f3dbee3bd6313d90321ccf574fc9eef284f147abd89b9 → 0f/f3/8d5d281fb49e342644220e9902fd21994ee0a7a5a91ced96ee1e206de8375da808072f25287e9ab5e1ea44dd034f2d030377da70f024b52415241b60f8eb}

@@ -1386,7 +1386,7 @@
   "dist-tags": {
     "latest": "5.2.1"
   },
-  "_rev": "205-62b4c0f53b8ed42c",
+  "_rev": "213-a835888717fa1b2a",
   "_id": "@smithy/chunked-blob-reader",
   "readme": "# @smithy/chunked-blob-reader\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/chunked-blob-reader/latest.svg)](https://www.npmjs.com/package/@smithy/chunked-blob-reader)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/chunked-blob-reader.svg)](https://www.npmjs.com/package/@smithy/chunked-blob-reader)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{de/c0/e17116c7604124e163b796879fb34f057272ab09dd40612115d5d9f8f18924dcdd6aa4f226914e969867414567c2b07c3078069faa397925c9521a878eb6 → 12/1d/14730d55f5abe4b0829170933694d4cff27d0c603dc071fc77499d307455b64e4ebcf1246121901afd779a43eeb9d65f2ed42bfa03e4b89b66db809b5ab6}

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

package/npm-cache/_cacache/content-v2/sha512/{27/41/bf534ac3e032d3a58088d06dabfa6470559d406519225b2c5730ef68ebc650b4571f8b68c661266648eb20d1387608f6e46e19af623eeb9fbdcb007f7b2c → 13/68/68fef47ba1093283b497c50597d0d6f1aa9628a006333eaeede9140168e13d66abcd436b74bec0ae4aec47a68d0ca4dfea137f30fd04fa204f41c6d1a483}

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

package/npm-cache/_cacache/content-v2/sha512/{f6/e6/141779abaf2e1a6b498283ef8221ff718be4a338a28c1ca7cd45f9c4c65cc924b00401445a945b1e70424503b5b01e17aeb69e557e8eeff2c2d1c4e5c2f4 → 14/c6/9c50e62f34493fce9fc9f467c967e38a9d5f30ad8413478c61aa371b2c716816c2baefe5c8189f66cb7c571c99eb18a133779e9e11c855c377e43c904b6f}

@@ -2263,7 +2263,7 @@
   "dist-tags": {
     "latest": "1.8.0"
   },
-  "_rev": "707-7e5679acc36ae191",
+  "_rev": "718-c881a190ef7f9076",
   "_id": "b4a",
   "readme": "# Buffer for Array\n\nBuffer for Array (B4A) provides a set of functions for bridging the gap between the Node.js `Buffer` class and the `Uint8Array` class. A browser compatibility layer is also included, making it possible to use B4A in both Node.js and browsers without having to worry about whether you're dealing with buffers or typed arrays.\n\n## Installation\n\n```sh\nnpm i b4a\n```\n\n### React Native\n\nWhen imported from React Native `b4a` will make use of `react-native-b4a` for optimised buffer operations when available. All you need to do is install it:\n\n```sh\nnpm i react-native-b4a\n```\n\n## API\n\n#### `b4a.isBuffer(value)`\n\nSee https://nodejs.org/api/buffer.html#static-method-bufferisbufferobj\n\nThis will also return `true` when passed a `Uint8Array`.\n\n#### `b4a.isEncoding(encoding)`\n\nSee https://nodejs.org/api/buffer.html#static-method-bufferisencodingencoding\n\n#### `b4a.alloc(size[, fill[, encoding]])`\n\nSee https://nodejs.org/api/buffer.html#static-method-bufferallocsize-fill-encoding\n\n#### `b4a.allocUnsafe(size)`\n\nSee https://nodejs.org/api/buffer.html#static-method-bufferallocunsafesize\n\n#### `b4a.allocUnsafeSlow(size)`\n\nSee https://nodejs.org/api/buffer.html#static-method-bufferallocunsafeslowsize\n\n#### `b4a.byteLength(string)`\n\nSee https://nodejs.org/api/buffer.html#static-method-bufferbytelengthstring-encoding\n\n#### `b4a.compare(buf1, buf2)`\n\nSee https://nodejs.org/api/buffer.html#static-method-buffercomparebuf1-buf2\n\n#### `b4a.concat(buffers[, totalLength])`\n\nSee https://nodejs.org/api/buffer.html#static-method-bufferconcatlist-totallength\n\n#### `b4a.copy(source, target[, targetStart[, sourceStart[, sourceEnd]]])`\n\nSee https://nodejs.org/api/buffer.html#bufcopytarget-targetstart-sourcestart-sourceend\n\n#### `b4a.equals(buf1, buf2)`\n\nSee https://nodejs.org/api/buffer.html#bufequalsotherbuffer\n\n#### `b4a.fill(buffer, value[, offset[, end]][, encoding])`\n\nSee https://nodejs.org/api/buffer.html#buffillvalue-offset-end-encoding\n\n#### `b4a.from(array)`\n\nSee https://nodejs.org/api/buffer.html#static-method-bufferfromarray\n\n#### `b4a.from(arrayBuffer[, byteOffset[, length]])`\n\nSee https://nodejs.org/api/buffer.html#static-method-bufferfromarraybuffer-byteoffset-length\n\n#### `b4a.from(buffer)`\n\nSee https://nodejs.org/api/buffer.html#static-method-bufferfrombuffer\n\n#### `b4a.from(string[, encoding])`\n\nSee https://nodejs.org/api/buffer.html#static-method-bufferfromstring-encoding\n\n#### `b4a.includes(buffer, value[, byteOffset][, encoding])`\n\nSee https://nodejs.org/api/buffer.html#bufincludesvalue-byteoffset-encoding\n\n#### `b4a.indexOf(buffer, value[, byteOffset][, encoding])`\n\nSee https://nodejs.org/api/buffer.html#bufindexofvalue-byteoffset-encoding\n\n#### `b4a.lastIndexOf(buffer, value[, byteOffset][, encoding])`\n\nSee https://nodejs.org/api/buffer.html#buflastindexofvalue-byteoffset-encoding\n\n#### `b4a.swap16(buffer)`\n\nSee https://nodejs.org/api/buffer.html#bufswap16\n\n#### `b4a.swap32(buffer)`\n\nSee https://nodejs.org/api/buffer.html#bufswap32\n\n#### `b4a.swap64(buffer)`\n\nSee https://nodejs.org/api/buffer.html#bufswap64\n\n#### `b4a.toBuffer(buffer)`\n\nConvert a buffer to its canonical representation. In Node.js, the canonical representation is a `Buffer`. In the browser, the canonical representation is a `Uint8Array`.\n\n#### `b4a.toString(buffer, [encoding[, start[, end]]])`\n\nSee https://nodejs.org/api/buffer.html#buftostringencoding-start-end\n\n#### `b4a.write(buffer, string[, offset[, length]][, encoding])`\n\nSee https://nodejs.org/api/buffer.html#bufwritestring-offset-length-encoding\n\n#### `b4a.writeDoubleLE(buffer, value[, offset])`\n\nSee https://nodejs.org/api/buffer.html#bufwritedoublelevalue-offset\n\n#### `b4a.writeFloatLE(buffer, value[, offset])`\n\nSee https://nodejs.org/api/buffer.html#bufwritefloatlevalue-offset\n\n#### `b4a.writeUInt32LE(buffer, value[, offset])`\n\nhttps://nodejs.org/api/buffer.html#bufwriteuint32levalue-offset\n\n#### `b4a.writeInt32LE(buffer, value[, offset])`\n\nSee https://nodejs.org/api/buffer.html#bufwriteint32levalue-offset\n\n#### `b4a.readDoubleLE(buffer[, offset])`\n\nSee https://nodejs.org/api/buffer.html#bufreaddoubleleoffset\n\n#### `b4a.readFloatLE(buffer[, offset])`\n\nSee https://nodejs.org/api/buffer.html#bufreadfloatleoffset\n\n#### `b4a.readUInt32LE(buffer[, offset])`\n\nSee https://nodejs.org/api/buffer.html#bufreaduint32leoffset\n\n#### `b4a.readInt32LE(buffer[, offset])`\n\nSee https://nodejs.org/api/buffer.html#bufreadint32leoffset\n\n## License\n\nApache 2.0",
   "_attachments": {}