mrs-toolbox-cli 9.0.3 → 9.0.5

package/kotlinx-coroutines-core.js

@@ -275,7 +275,7 @@
   initMetadataForClass(Symbol, 'Symbol');
   initMetadataForInterface(SelectInstance, 'SelectInstance');
   initMetadataForClass(ClauseData, 'ClauseData', VOID, VOID, VOID, [1]);
-  initMetadataForClass(SelectImplementation, 'SelectImplementation', VOID, VOID, [CancelHandler, SelectInstance, Waiter], [0, 2]);
+  initMetadataForClass(SelectImplementation, 'SelectImplementation', VOID, VOID, [CancelHandler, Waiter, SelectInstance], [0, 2]);
   initMetadataForClass(TrySelectDetailedResult, 'TrySelectDetailedResult', VOID, Enum);
   initMetadataForClass(SemaphoreAndMutexImpl, 'SemaphoreAndMutexImpl', VOID, VOID, VOID, [0]);
   initMetadataForClass(SemaphoreImpl, 'SemaphoreImpl', VOID, SemaphoreAndMutexImpl, VOID, [0]);

package/npm-cache/_cacache/content-v2/sha512/{2e/e1/5d3b56088a34d7fa1c8ed429876494487a1902b6304c659db6afaaa7c557f985b8f1964e81ff186a6822e14924f299d043e5f7833115a7e774bd9d09ee03 → 01/0c/c890acc95c6e8ce68ec80b6e325887fbac70200633dc691cfad93a53e680cec993f00a398f339b3215a123b399231b6e20ee198daecce36e301934de7ad7}

@@ -1934,7 +1934,7 @@
   "dist-tags": {
     "latest": "2.8.2"
   },
-  "_rev": "630-9bc1d91ce053353a",
+  "_rev": "641-494c60d461929b21",
   "_id": "bare-events",
   "readme": "# bare-events\n\nEvent emitters for JavaScript.\n\n```\nnpm install bare-events\n```\n\n## Usage\n\n```js\nconst EventEmitter = require('bare-events')\n\nconst e = new EventEmitter()\n\ne.on('hello', function (data) {\n  console.log(data)\n})\n\ne.emit('hello', 'world')\n```\n\n## License\n\nApache-2.0",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{63/0f/3b47ef1af897eb9824d2fb1b26501616ac88a9a23bd75a5cb84ede3ff0d2fcdb84d4aaea2d11977083cac6ada2a810bed7bb5efbd798109e913ac1f6f2af → 02/04/bf7717e55687777c3a9943198147201659d5154b26421698cff5266493f19dc4a03c390d048bb42f5aecbb5eb5826827a20936e6952fbadd897991636c7b}

@@ -228,7 +228,7 @@
   "dist-tags": {
     "latest": "1.1.0"
   },
-  "_rev": "124-523fbc7ff06c3ff8",
+  "_rev": "135-dafd028f34e74fe5",
   "_id": "@smithy/uuid",
   "readme": "# @smithy/uuid\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/uuid/latest.svg)](https://www.npmjs.com/package/@smithy/uuid)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/uuid.svg)](https://www.npmjs.com/package/@smithy/uuid)\n\n> An internal package\n\n## Usage\n\nThis is an internal `@smithy` package. You should not install it as a direct dependency in your applications.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{9a/d9/dd0b4af9aa451375453474c1e2ee9a2658d24cd9c54b5cc70cb298e2566a02025c4d37fbd90b247d5c4b2c5fd7bb7ea9eea507d3dccdb491cc7c889c25de → 03/02/aa0dc5b3860694f446d55955fbb5700439279d099a03b6e4eaddb9a3bb6587bc740d55972a0ea00b85b546cd46daeb7daa0690b47c085855c95bbbeaa5b4}

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

package/npm-cache/_cacache/content-v2/sha512/{cd/cb/122fbb0e248076a6e0fcf479de28bb1610efa26f7ccc0b0f2542b9c760827d9ff818155294719f6677e91b62bd8935b376e57dd4bd640128cd9a706a2595 → 04/96/b58c69afed2294d915fa2681f71ae07fd1dc508be207a140a44965a55189bded808e4314e65ddc753def8ac30c4b64ce9563fcd9a479efc9d0ff1a4993bc}

@@ -5794,7 +5794,7 @@
   "dist-tags": {
     "latest": "4.2.8"
   },
-  "_rev": "177-0d5086e032bc6a4c",
+  "_rev": "188-7162f196a5c93637",
   "_id": "@smithy/querystring-parser",
   "readme": "# @smithy/querystring-parser\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/querystring-parser/latest.svg)](https://www.npmjs.com/package/@smithy/querystring-parser)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/querystring-parser.svg)](https://www.npmjs.com/package/@smithy/querystring-parser)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{d7/62/c1343137a179248d316663afc6d71cc57c838cb257ebbc36c877ccc44dd9197130f923563815e1c62e03d07656016f90ee924cd0948ff995636dcbcbc76d → 04/9a/775d3502a3d4176fdb73282c760957610493eaf018e7e9ba7c26fd13796bb6ccae5ec878cf4613cde970ff3c97fee4b1006e679083bfafbb15a84c4f00ca}

@@ -14702,7 +14702,7 @@
   "dist-tags": {
     "latest": "4.3.23"
   },
-  "_rev": "200-f5194787678c9b49",
+  "_rev": "211-6ab82860a0a9976a",
   "_id": "@smithy/util-defaults-mode-browser",
   "readme": "# @smithy/util-defaults-mode-browser\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/util-defaults-mode-browser/latest.svg)](https://www.npmjs.com/package/@smithy/util-defaults-mode-browser)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/util-defaults-mode-browser.svg)](https://www.npmjs.com/package/@smithy/util-defaults-mode-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/{36/64/80227c2b830de1528d29885ef7a9517175cdaabd388ac4c2eeff26004a1ae245177a920c9ad97c9b65b44aef96832dd995c647abd404a6826c69b0f2ee37 → 05/53/2d41a824b41676c32dc411aac7a050c03a1b0ee67ce6aeadce7850558ed7ad2bbd7dbb5932b9e110f9e2630e045b43532327bbd18a1f7f9f2a989b6ec15d}

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

package/npm-cache/_cacache/content-v2/sha512/{6c/ea/de4710a71281a6b9abe1c9e7a3a6263ede8f7a138fb0ecef4e0d9dc25067ae939faec56e6b2d450f95d29ddd6a35c284bfa4b78e9abcb997cd33886aae7e → 08/90/dc77edc91db5d283ea5e28219ebcbb6c3255f96a4d9022b096facff25c0246ef603351cbe8005caeb83b53612cf4778eb41fc1a0e4ca602d17af72392af7}

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

package/npm-cache/_cacache/content-v2/sha512/{b7/5e/24b192db3251059db0b6545e9c81ab6b9b5d06a97f3d8f9dc18098ccb6c4f7efb8bbd02204be499c9135af1abf444aa574145d4e4fa6967b1fd2381984f0 → 09/fe/0d79f6bc392a1a12a1806ef6846922fa58773ea5b3b3fe72317530e671547d9bce574b5331e914449124ad02ea15879f432dc2c3e06481bc87f3a8d54287}

@@ -1186,7 +1186,7 @@
   "dist-tags": {
     "latest": "0.11.10"
   },
-  "_rev": "813-aab20a919e5109e3",
+  "_rev": "824-16600d0a7a231fed",
   "_id": "process",
   "readme": "# process\n\n```require('process');``` just like any other module.\n\nWorks in node.js and browsers via the browser.js shim provided with the module.\n\n## browser implementation\n\nThe goal of this module is not to be a full-fledged alternative to the builtin process module. This module mostly exists to provide the nextTick functionality and little more. We keep this module lean because it will often be included by default by tools like browserify when it detects a module has used the `process` global.\n\nIt also exposes a \"browser\" member (i.e. `process.browser`) which is `true` in this implementation but `undefined` in node. This can be used in isomorphic code that adjusts it's behavior depending on which environment it's running in. \n\nIf you are looking to provide other process methods, I suggest you monkey patch them onto the process global in your app. A list of user created patches is below.\n\n* [hrtime](https://github.com/kumavis/browser-process-hrtime)\n* [stdout](https://github.com/kumavis/browser-stdout)\n\n## package manager notes\n\nIf you are writing a bundler to package modules for client side use, make sure you use the ```browser``` field hint in package.json.\n\nSee https://gist.github.com/4339901 for details.\n\nThe [browserify](https://github.com/substack/node-browserify) module will properly handle this field when bundling your files.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{6b/df/6aa5ca90cae64f3e3703bb270e59d448f854134ba23fa25c3560c93d52256cd15b62bba3a243edcc63d926dae84914517999a825b22426aa8d632e9ce75a → 0a/5d/dac9994df361294ddb93a51bf24a6d64b5203b28adc895265d0c2a7650ba45e3ce1f80b81d877997a27857095066b2620feda6d3c781619c0f2bf31d5369}

@@ -1533,7 +1533,7 @@
   "dist-tags": {
     "latest": "4.2.1"
   },
-  "_rev": "168-a865437701674de8",
+  "_rev": "179-68bd96abfeb2c8fd",
   "_id": "@smithy/util-body-length-node",
   "readme": "# @smithy/util-body-length-node\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/util-body-length-node/latest.svg)](https://www.npmjs.com/package/@smithy/util-body-length-node)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/util-body-length-node.svg)](https://www.npmjs.com/package/@smithy/util-body-length-node)\n\nDetermines the length of a request body in node.js\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{d2/dc/6eda561a77f6048f313a1b991bf6ba392198e765d5b9273ad9d9923c946473c09c836a016202434f755091c0a3ce4533feec1237004442f1ff919a5cb662 → 0c/cf/678189ae3aafe500bb90ac395fd1e4ea9aeceec0205fd117d0ce2847bb8dc001c735ddc5e3fee2ce13484ae7c36b918317cb150b8992f4a5583bb161af28}

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

package/npm-cache/_cacache/content-v2/sha512/{a1/e6/fcd7060516a1090f98607a95d7634fea669280f0349728417f181fa49bc3ae249555de3c8f1164248c4c4972e321ea5bac95174a0bccf61757c0e14b3400 → 0d/2a/34f1da6ed865c7abefdd68684bf6f5ce6cd14460e310b83a8161cc17fd943b5b0c48a4885f7c349ca5475a6bd74c59219339e0e062ac00d0833c993fbc49}

@@ -2702,7 +2702,7 @@
     "latest": "6.0.6",
     "n-api": "4.0.0-napi"
   },
-  "_rev": "312-fa2497c76e4a2986",
+  "_rev": "323-3ff4801f4e67b7a1",
   "_id": "utf-8-validate",
   "readme": "# utf-8-validate\n\n[![Version npm](https://img.shields.io/npm/v/utf-8-validate.svg?logo=npm)](https://www.npmjs.com/package/utf-8-validate)\n[![Linux/macOS/Windows Build](https://img.shields.io/github/actions/workflow/status/websockets/utf-8-validate/ci.yml?branch=master&label=build&logo=github)](https://github.com/websockets/utf-8-validate/actions?query=workflow%3ACI+branch%3Amaster)\n\nCheck if a buffer contains valid UTF-8 encoded text.\n\n## Installation\n\n```\nnpm install utf-8-validate --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 a single function that takes one argument. To maximize\nperformance, the argument is not validated. It is the caller's responsibility to\nensure that it is correct.\n\n### `isValidUTF8(buffer)`\n\nChecks whether a buffer contains valid UTF-8.\n\n#### Arguments\n\n- `buffer` - The buffer to check.\n\n#### Return value\n\n`true` if the buffer contains only correct UTF-8, else `false`.\n\n#### Example\n\n```js\n'use strict';\n\nconst isValidUTF8 = require('utf-8-validate');\n\nconst buf = Buffer.from([0xf0, 0x90, 0x80, 0x80]);\n\nconsole.log(isValidUTF8(buf));\n// => true\n```\n\n## License\n\n[MIT](LICENSE)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{a6/9d/85b48d1e4f7d8c65f33a99c55ff9e8f41d43afad311973f9231a41672c02a57b4d9da2bd3fe3147113a9916faf4a9330864d49a8484d504e179472d8b12c → 0f/d7/630ec545402f6f8f14a15d275e0f7d865ee25bb646600ceb3d49bf22f5b44c4339dce9acfad7e76799f25804084ef7631890e6c2e3c2e93a00052fea45d3}

@@ -16391,7 +16391,7 @@
   "dist-tags": {
     "latest": "3.970.0"
   },
-  "_rev": "169-abd88a615dbc96dd",
+  "_rev": "181-976128fdceb63dc3",
   "_id": "@aws-sdk/credential-provider-http",
   "readme": "# @aws-sdk/credential-provider-http\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/credential-provider-http/latest.svg)](https://www.npmjs.com/package/@aws-sdk/credential-provider-http)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/credential-provider-http.svg)](https://www.npmjs.com/package/@aws-sdk/credential-provider-http)\n\n> An internal transitively required package.\n\n## Usage\n\nSee https://www.npmjs.com/package/@aws-sdk/credential-providers",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{32/be/2e959a72db7864add3e3fd5313085cb172d2bc46db73c50e24054653233fbcce62438bf8dbd402e349f02397e743989156fdf1e7e9d972ba89eb0b052920 → 10/c5/5bba840563f1b7a4a50c1b79ec242fd91ba98f9792d8efc49acfe79666cff0d818c4a3218a17e8542fa95dd25d4f24d3bddb7c8fccf6315d64cf8e6d6400}

@@ -15233,7 +15233,7 @@
   "dist-tags": {
     "latest": "3.20.7"
   },
-  "_rev": "191-bb5abd364e44e530",
+  "_rev": "204-a3c3c3393e1bae84",
   "_id": "@smithy/core",
   "readme": "# @smithy/core\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/core/latest.svg)](https://www.npmjs.com/package/@smithy/core)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/core.svg)](https://www.npmjs.com/package/@smithy/core)\n\n> An internal package. You probably shouldn't use this package, at least directly.\n\nThis package provides common or core functionality for generic Smithy clients.\n\nYou do not need to explicitly install this package, since it will be installed during code generation if used.\n\n## Development of `@smithy/core` submodules\n\nCore submodules are organized for distribution via the `package.json` `exports` field.\n\n`exports` is supported by default by the latest Node.js, webpack, and esbuild. For react-native, it can be\nenabled via instructions found at [reactnative.dev/blog](https://reactnative.dev/blog/2023/06/21/package-exports-support), but we also provide a compatibility redirect.\n\nThink of `@smithy/core` as a mono-package within the monorepo.\nIt preserves the benefits of modularization, for example to optimize Node.js initialization speed,\nwhile making it easier to have a consistent version of core dependencies, reducing package sprawl when\ninstalling a Smithy runtime client.\n\n### Guide for submodules\n\n- Each `index.ts` file corresponding to the pattern `./src/submodules/<MODULE_NAME>/index.ts` will be\n  published as a separate `dist-cjs` bundled submodule index using the `Inliner.js` build script.\n- create a folder as `./src/submodules/<SUBMODULE>` including an `index.ts` file and a `README.md` file.\n  - The linter will throw an error on missing submodule metadata in `package.json` and the various `tsconfig.json` files, but it will automatically fix them if possible.\n- a submodule is equivalent to a standalone `@smithy/<pkg>` package in that importing it in Node.js will resolve a separate bundle.\n- submodules may not relatively import files from other submodules. Instead, directly use the `@scope/pkg/submodule` name as the import.\n  - The linter will check for this and throw an error.\n- To the extent possible, correctly declaring submodule metadata is validated by the linter in `@smithy/core`.\n  The linter runs during `yarn build` and also as `yarn lint`.\n\n### When should I create an `@smithy/core/submodule` vs. `@smithy/new-package`?\n\nKeep in mind that the core package is installed by all downstream clients.\n\nIf the component functionality is upstream of multiple clients, it is\na good candidate for a core submodule. For example, if `middleware-retry` had been written\nafter the support for submodules was added, it would have been a submodule.\n\nIf the component's functionality is downstream of a client (rare), or only expected to be used by a very small\nsubset of clients, it could be written as a standalone package.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{ce/89/06f5f89c0551558cfdd07880e7b7bc0a39ea8124ac6384943831e0280ae5f542b5074f3cfe95eef5959c5626b697387fc591ef59cd5437d5bb13777e9e8a → 11/2e/e355a2d677e8b13158632c0abaa75c7e5b126111c7a072ed1a3035f8a4732ccf686c8f409e1f3ec5727f4ce1cfcff6918715d8d7b570a354d1b006a73a6a}

@@ -4551,7 +4551,7 @@
     "latest": "7.0.6",
     "6x": "6.0.6"
   },
-  "_rev": "3694-96c2672af1a6f122",
+  "_rev": "3716-81e5810499801735",
   "_id": "cross-spawn",
   "readme": "",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{f1/5c/c21ac902e43185351da324eb65b42e9aebc62308b609be02a041f6cf5f6a29d2b83f8b4ffabc4ae04ba3d631d7eee8b3438b18e79881951c76ada2ec4e49 → 11/fc/5e494141cd3d9077b10bcb6a0aaa8b4884a8d0702a156ed4cc4a9325c54678a0fb4fdab8212492854625c5d0a811d7e087b71e53726e60a5f483021c2795}

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

package/npm-cache/_cacache/content-v2/sha512/{79/80/b5b2da0fb481f9466aee16b766f83e99399effa8bf734c1ffc15fb000457f9e52083383cb9df7c04f588e21a58a069e0b04944691e653320e91ad1dfa349 → 12/7c/67dc380e2767488005a05eec2fba4abf27eb987da25cc99573142fba6d7c8525badcb83fc1f6ca90e8d129d262d0fd6947eaa96f6b5b8d72a245d7085208}

@@ -2011,7 +2011,7 @@
   "dist-tags": {
     "latest": "1.7.3"
   },
-  "_rev": "627-d951f9c0ee15428a",
+  "_rev": "638-2b0a10719ce3d76b",
   "_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": {}

package/npm-cache/_cacache/content-v2/sha512/{da/70/4deb4f0ea557dc9de570b9927d6abc358a1caaccca612e45371abdbd9f026a66a8c7f92db08577d90bd186fffb9466b1cfa8bcc251f8579a5e9b2194caef → 12/da/cc2e9f7ffb63af3acf252b496567b0ca69940dc8f04cb797d37f25f5598c21cd7ea137e409c47a3e956f7b0091d2afa2807198882d73c5f23a66e1240267}

@@ -350,7 +350,7 @@
   "dist-tags": {
     "latest": "1.0.1"
   },
-  "_rev": "280-4c7ed4de6b15f6d7",
+  "_rev": "291-92c31b0f27f166c3",
   "_id": "lazystream",
   "readme": "# Lazy Streams\n\n> *Create streams lazily when they are read from or written to.*  \n> `lazystream: 1.0.1`  \n\n## Why?\n\nSometimes you feel the itch to open *all the files* at once. You want to pass a bunch of streams around, so the consumer does not need to worry where the data comes from.\nFrom a software design point-of-view this sounds entirely reasonable. Then there is that neat little function `fs.createReadStream()` that opens a file and gives you a nice `fs.ReadStream` to pass around, so you use what the mighty creator deities of node bestowed upon you.\n\n> `Error: EMFILE, too many open files`  \n> ─ *node*\n\nThis package provides two classes based on the node's Streams3 API (courtesy of `readable-stream` to ensure a stable version).\n\n## Class: lazystream.Readable\n\nA wrapper for readable streams. Extends [`stream.PassThrough`](http://nodejs.org/api/stream.html#stream_class_stream_passthrough).\n\n### new lazystream.Readable(fn [, options])\n\n* `fn` *{Function}*  \n  The function that the lazy stream will call to obtain the stream to actually read from.\n* `options` *{Object}*  \n  Options for the underlying `PassThrough` stream, accessible by `fn`.\n\nCreates a new readable stream. Once the stream is accessed (for example when you call its `read()` method, or attach a `data`-event listener) the `fn` function is called with the outer `lazystream.Readable` instance bound to `this`.\n\nIf you pass an `options` object to the constuctor, you can access it in your `fn` function.\n\n```javascript\nnew lazystream.Readable(function (options) {\n  return fs.createReadStream('/dev/urandom');\n});\n```\n\n## Class: lazystream.Writable\n\nA wrapper for writable streams. Extends [`stream.PassThrough`](http://nodejs.org/api/stream.html#stream_class_stream_passthrough).\n\n### new lazystream.Writable(fn [, options])\n\n* `fn` *{Function}*  \n  The function that the lazy stream will call to obtain the stream to actually write to.\n* `options` *{Object}*  \n  Options for the underlying `PassThrough` stream, accessible by `fn`.\n\nCreates a new writable stream. Just like the one above but for writable streams.\n\n```javascript\nnew lazystream.Writable(function () {\n  return fs.createWriteStream('/dev/null');\n});\n```\n\n## Install\n\n```console\n$ npm install lazystream --save\nlazystream@1.0.1 node_modules/lazystream\n└── readable-stream@2.0.5\n```\n\n## Changelog\n\n### v1.0.1\n\n- [#3](https://github.com/jpommerening/node-lazystream/issues/3): (finally) fixed a long-standing publishing error\n\n### v1.0.0\n\n- [#2](https://github.com/jpommerening/node-lazystream/issues/2): [unconditionally](https://r.va.gg/2014/06/why-i-dont-use-nodes-core-stream-module.html) use `readable-stream` _2.x_.\n\n### v0.2.0\n\n- [#1](https://github.com/jpommerening/node-lazystream/pull/1): error events are now propagated\n\n### v0.1.0\n\n- _(this was the first release)_\n\n## Contributing\n\nFork it, branch it, send me a pull request. We'll work out the rest together.\n\n## Credits\n\n[Chris Talkington](https://github.com/ctalkington) and his [node-archiver](https://github.com/ctalkington/node-archiver) for providing a use-case.\n\n## [License](LICENSE)\n\nCopyright (c) 2013 J. Pommerening, contributors.\n\nPermission is hereby granted, free of charge, to any person\nobtaining a copy of this software and associated documentation\nfiles (the \"Software\"), to deal in the Software without\nrestriction, including without limitation the rights to use,\ncopy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the\nSoftware is furnished to do so, subject to the following\nconditions:\n\nThe above copyright notice and this permission notice shall be\nincluded in all copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND,\nEXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES\nOF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND\nNONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT\nHOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,\nWHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING\nFROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR\nOTHER DEALINGS IN THE SOFTWARE.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{08/24/4285f028138be241f0c8cced898c3b2868a5e85063817743beb96926c74faa98236c9414152de23ef177aeeab3b2eb3cc7a8be9b8d99287f59ea2914e241 → 16/e3/b9dd192132ffd72ac779ef618de02d70b8a414c1a43691ee4718e674d69ca241fe3ce3a48beac27b870ecc53e3a1ec155f05c944fb3a5d4b67d72ee04357}

@@ -826,7 +826,7 @@
   "dist-tags": {
     "latest": "5.2.0"
   },
-  "_rev": "263-787961bd3c816eec",
+  "_rev": "274-ebbca97acdc07728",
   "_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/{dc/9b/9370a125f546f7bf1cc96ef92cadc4f4ea39f0d5c0ccb94596ba6780fc26b19841e136946204447d76943f61755c568167c3b93c3340510b5f72246e29dc → 17/72/68c2d40f63020d32364af4785bcb1cb5bf2d7fba6b7b239e527d45ad25dcea652ca840186de0db1fa584fe057295ef2c4140d9c4a6b23a358584de43d1dd}

@@ -758,7 +758,7 @@
   "dist-tags": {
     "latest": "5.2.1"
   },
-  "_rev": "3539-24def3aaa91d670a",
+  "_rev": "3561-02af7ea1a74d6e47",
   "_id": "safe-buffer",
   "readme": "# safe-buffer [![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/safe-buffer/master.svg\n[travis-url]: https://travis-ci.org/feross/safe-buffer\n[npm-image]: https://img.shields.io/npm/v/safe-buffer.svg\n[npm-url]: https://npmjs.org/package/safe-buffer\n[downloads-image]: https://img.shields.io/npm/dm/safe-buffer.svg\n[downloads-url]: https://npmjs.org/package/safe-buffer\n[standard-image]: https://img.shields.io/badge/code_style-standard-brightgreen.svg\n[standard-url]: https://standardjs.com\n\n#### Safer Node.js Buffer API\n\n**Use the new Node.js Buffer APIs (`Buffer.from`, `Buffer.alloc`,\n`Buffer.allocUnsafe`, `Buffer.allocUnsafeSlow`) in all versions of Node.js.**\n\n**Uses the built-in implementation when available.**\n\n## install\n\n```\nnpm install safe-buffer\n```\n\n## usage\n\nThe goal of this package is to provide a safe replacement for the node.js `Buffer`.\n\nIt's a drop-in replacement for `Buffer`. You can use it by adding one `require` line to\nthe top of your node.js modules:\n\n```js\nvar Buffer = require('safe-buffer').Buffer\n\n// Existing buffer code will continue to work without issues:\n\nnew Buffer('hey', 'utf8')\nnew Buffer([1, 2, 3], 'utf8')\nnew Buffer(obj)\nnew Buffer(16) // create an uninitialized buffer (potentially unsafe)\n\n// But you can use these new explicit APIs to make clear what you want:\n\nBuffer.from('hey', 'utf8') // convert from many types to a Buffer\nBuffer.alloc(16) // create a zero-filled buffer (safe)\nBuffer.allocUnsafe(16) // create an uninitialized buffer (potentially unsafe)\n```\n\n## api\n\n### Class Method: Buffer.from(array)\n<!-- YAML\nadded: v3.0.0\n-->\n\n* `array` {Array}\n\nAllocates a new `Buffer` using an `array` of octets.\n\n```js\nconst buf = Buffer.from([0x62,0x75,0x66,0x66,0x65,0x72]);\n  // creates a new Buffer containing ASCII bytes\n  // ['b','u','f','f','e','r']\n```\n\nA `TypeError` will be thrown if `array` is not an `Array`.\n\n### Class Method: Buffer.from(arrayBuffer[, byteOffset[, length]])\n<!-- YAML\nadded: v5.10.0\n-->\n\n* `arrayBuffer` {ArrayBuffer} The `.buffer` property of a `TypedArray` or\n  a `new ArrayBuffer()`\n* `byteOffset` {Number} Default: `0`\n* `length` {Number} Default: `arrayBuffer.length - byteOffset`\n\nWhen passed a reference to the `.buffer` property of a `TypedArray` instance,\nthe newly created `Buffer` will share the same allocated memory as the\nTypedArray.\n\n```js\nconst arr = new Uint16Array(2);\narr[0] = 5000;\narr[1] = 4000;\n\nconst buf = Buffer.from(arr.buffer); // shares the memory with arr;\n\nconsole.log(buf);\n  // Prints: <Buffer 88 13 a0 0f>\n\n// changing the TypedArray changes the Buffer also\narr[1] = 6000;\n\nconsole.log(buf);\n  // Prints: <Buffer 88 13 70 17>\n```\n\nThe optional `byteOffset` and `length` arguments specify a memory range within\nthe `arrayBuffer` that will be shared by the `Buffer`.\n\n```js\nconst ab = new ArrayBuffer(10);\nconst buf = Buffer.from(ab, 0, 2);\nconsole.log(buf.length);\n  // Prints: 2\n```\n\nA `TypeError` will be thrown if `arrayBuffer` is not an `ArrayBuffer`.\n\n### Class Method: Buffer.from(buffer)\n<!-- YAML\nadded: v3.0.0\n-->\n\n* `buffer` {Buffer}\n\nCopies the passed `buffer` data onto a new `Buffer` instance.\n\n```js\nconst buf1 = Buffer.from('buffer');\nconst buf2 = Buffer.from(buf1);\n\nbuf1[0] = 0x61;\nconsole.log(buf1.toString());\n  // 'auffer'\nconsole.log(buf2.toString());\n  // 'buffer' (copy is not changed)\n```\n\nA `TypeError` will be thrown if `buffer` is not a `Buffer`.\n\n### Class Method: Buffer.from(str[, encoding])\n<!-- YAML\nadded: v5.10.0\n-->\n\n* `str` {String} String to encode.\n* `encoding` {String} Encoding to use, Default: `'utf8'`\n\nCreates a new `Buffer` containing the given JavaScript string `str`. If\nprovided, the `encoding` parameter identifies the character encoding.\nIf not provided, `encoding` defaults to `'utf8'`.\n\n```js\nconst buf1 = Buffer.from('this is a tést');\nconsole.log(buf1.toString());\n  // prints: this is a tést\nconsole.log(buf1.toString('ascii'));\n  // prints: this is a tC)st\n\nconst buf2 = Buffer.from('7468697320697320612074c3a97374', 'hex');\nconsole.log(buf2.toString());\n  // prints: this is a tést\n```\n\nA `TypeError` will be thrown if `str` is not a string.\n\n### Class Method: Buffer.alloc(size[, fill[, encoding]])\n<!-- YAML\nadded: v5.10.0\n-->\n\n* `size` {Number}\n* `fill` {Value} Default: `undefined`\n* `encoding` {String} Default: `utf8`\n\nAllocates a new `Buffer` of `size` bytes. If `fill` is `undefined`, the\n`Buffer` will be *zero-filled*.\n\n```js\nconst buf = Buffer.alloc(5);\nconsole.log(buf);\n  // <Buffer 00 00 00 00 00>\n```\n\nThe `size` must be less than or equal to the value of\n`require('buffer').kMaxLength` (on 64-bit architectures, `kMaxLength` is\n`(2^31)-1`). Otherwise, a [`RangeError`][] is thrown. A zero-length Buffer will\nbe created if a `size` less than or equal to 0 is specified.\n\nIf `fill` is specified, the allocated `Buffer` will be initialized by calling\n`buf.fill(fill)`. See [`buf.fill()`][] for more information.\n\n```js\nconst buf = Buffer.alloc(5, 'a');\nconsole.log(buf);\n  // <Buffer 61 61 61 61 61>\n```\n\nIf both `fill` and `encoding` are specified, the allocated `Buffer` will be\ninitialized by calling `buf.fill(fill, encoding)`. For example:\n\n```js\nconst buf = Buffer.alloc(11, 'aGVsbG8gd29ybGQ=', 'base64');\nconsole.log(buf);\n  // <Buffer 68 65 6c 6c 6f 20 77 6f 72 6c 64>\n```\n\nCalling `Buffer.alloc(size)` can be significantly slower than the alternative\n`Buffer.allocUnsafe(size)` but ensures that the newly created `Buffer` instance\ncontents will *never contain sensitive data*.\n\nA `TypeError` will be thrown if `size` is not a number.\n\n### Class Method: Buffer.allocUnsafe(size)\n<!-- YAML\nadded: v5.10.0\n-->\n\n* `size` {Number}\n\nAllocates a new *non-zero-filled* `Buffer` of `size` bytes.  The `size` must\nbe less than or equal to the value of `require('buffer').kMaxLength` (on 64-bit\narchitectures, `kMaxLength` is `(2^31)-1`). Otherwise, a [`RangeError`][] is\nthrown. A zero-length Buffer will be created if a `size` less than or equal to\n0 is specified.\n\nThe underlying memory for `Buffer` instances created in this way is *not\ninitialized*. The contents of the newly created `Buffer` are unknown and\n*may contain sensitive data*. Use [`buf.fill(0)`][] to initialize such\n`Buffer` instances to zeroes.\n\n```js\nconst buf = Buffer.allocUnsafe(5);\nconsole.log(buf);\n  // <Buffer 78 e0 82 02 01>\n  // (octets will be different, every time)\nbuf.fill(0);\nconsole.log(buf);\n  // <Buffer 00 00 00 00 00>\n```\n\nA `TypeError` will be thrown if `size` is not a number.\n\nNote that the `Buffer` module pre-allocates an internal `Buffer` instance of\nsize `Buffer.poolSize` that is used as a pool for the fast allocation of new\n`Buffer` instances created using `Buffer.allocUnsafe(size)` (and the deprecated\n`new Buffer(size)` constructor) only when `size` is less than or equal to\n`Buffer.poolSize >> 1` (floor of `Buffer.poolSize` divided by two). The default\nvalue of `Buffer.poolSize` is `8192` but can be modified.\n\nUse of this pre-allocated internal memory pool is a key difference between\ncalling `Buffer.alloc(size, fill)` vs. `Buffer.allocUnsafe(size).fill(fill)`.\nSpecifically, `Buffer.alloc(size, fill)` will *never* use the internal Buffer\npool, while `Buffer.allocUnsafe(size).fill(fill)` *will* use the internal\nBuffer pool if `size` is less than or equal to half `Buffer.poolSize`. The\ndifference is subtle but can be important when an application requires the\nadditional performance that `Buffer.allocUnsafe(size)` provides.\n\n### Class Method: Buffer.allocUnsafeSlow(size)\n<!-- YAML\nadded: v5.10.0\n-->\n\n* `size` {Number}\n\nAllocates a new *non-zero-filled* and non-pooled `Buffer` of `size` bytes.  The\n`size` must be less than or equal to the value of\n`require('buffer').kMaxLength` (on 64-bit architectures, `kMaxLength` is\n`(2^31)-1`). Otherwise, a [`RangeError`][] is thrown. A zero-length Buffer will\nbe created if a `size` less than or equal to 0 is specified.\n\nThe underlying memory for `Buffer` instances created in this way is *not\ninitialized*. The contents of the newly created `Buffer` are unknown and\n*may contain sensitive data*. Use [`buf.fill(0)`][] to initialize such\n`Buffer` instances to zeroes.\n\nWhen using `Buffer.allocUnsafe()` to allocate new `Buffer` instances,\nallocations under 4KB are, by default, sliced from a single pre-allocated\n`Buffer`. This allows applications to avoid the garbage collection overhead of\ncreating many individually allocated Buffers. This approach improves both\nperformance and memory usage by eliminating the need to track and cleanup as\nmany `Persistent` objects.\n\nHowever, in the case where a developer may need to retain a small chunk of\nmemory from a pool for an indeterminate amount of time, it may be appropriate\nto create an un-pooled Buffer instance using `Buffer.allocUnsafeSlow()` then\ncopy out the relevant bits.\n\n```js\n// need to keep around a few small chunks of memory\nconst store = [];\n\nsocket.on('readable', () => {\n  const data = socket.read();\n  // allocate for retained data\n  const sb = Buffer.allocUnsafeSlow(10);\n  // copy the data into the new allocation\n  data.copy(sb, 0, 0, 10);\n  store.push(sb);\n});\n```\n\nUse of `Buffer.allocUnsafeSlow()` should be used only as a last resort *after*\na developer has observed undue memory retention in their applications.\n\nA `TypeError` will be thrown if `size` is not a number.\n\n### All the Rest\n\nThe rest of the `Buffer` API is exactly the same as in node.js.\n[See the docs](https://nodejs.org/api/buffer.html).\n\n\n## Related links\n\n- [Node.js issue: Buffer(number) is unsafe](https://github.com/nodejs/node/issues/4660)\n- [Node.js Enhancement Proposal: Buffer.from/Buffer.alloc/Buffer.zalloc/Buffer() soft-deprecate](https://github.com/nodejs/node-eps/pull/4)\n\n## Why is `Buffer` unsafe?\n\nToday, the node.js `Buffer` constructor is overloaded to handle many different argument\ntypes like `String`, `Array`, `Object`, `TypedArrayView` (`Uint8Array`, etc.),\n`ArrayBuffer`, and also `Number`.\n\nThe API is optimized for convenience: you can throw any type at it, and it will try to do\nwhat you want.\n\nBecause the Buffer constructor is so powerful, you often see code like this:\n\n```js\n// Convert UTF-8 strings to hex\nfunction toHex (str) {\n  return new Buffer(str).toString('hex')\n}\n```\n\n***But what happens if `toHex` is called with a `Number` argument?***\n\n### Remote Memory Disclosure\n\nIf an attacker can make your program call the `Buffer` constructor with a `Number`\nargument, then they can make it allocate uninitialized memory from the node.js process.\nThis could potentially disclose TLS private keys, user data, or database passwords.\n\nWhen the `Buffer` constructor is passed a `Number` argument, it returns an\n**UNINITIALIZED** block of memory of the specified `size`. When you create a `Buffer` like\nthis, you **MUST** overwrite the contents before returning it to the user.\n\nFrom the [node.js docs](https://nodejs.org/api/buffer.html#buffer_new_buffer_size):\n\n> `new Buffer(size)`\n>\n> - `size` Number\n>\n> The underlying memory for `Buffer` instances created in this way is not initialized.\n> **The contents of a newly created `Buffer` are unknown and could contain sensitive\n> data.** Use `buf.fill(0)` to initialize a Buffer to zeroes.\n\n(Emphasis our own.)\n\nWhenever the programmer intended to create an uninitialized `Buffer` you often see code\nlike this:\n\n```js\nvar buf = new Buffer(16)\n\n// Immediately overwrite the uninitialized buffer with data from another buffer\nfor (var i = 0; i < buf.length; i++) {\n  buf[i] = otherBuf[i]\n}\n```\n\n\n### Would this ever be a problem in real code?\n\nYes. It's surprisingly common to forget to check the type of your variables in a\ndynamically-typed language like JavaScript.\n\nUsually the consequences of assuming the wrong type is that your program crashes with an\nuncaught exception. But the failure mode for forgetting to check the type of arguments to\nthe `Buffer` constructor is more catastrophic.\n\nHere's an example of a vulnerable service that takes a JSON payload and converts it to\nhex:\n\n```js\n// Take a JSON payload {str: \"some string\"} and convert it to hex\nvar server = http.createServer(function (req, res) {\n  var data = ''\n  req.setEncoding('utf8')\n  req.on('data', function (chunk) {\n    data += chunk\n  })\n  req.on('end', function () {\n    var body = JSON.parse(data)\n    res.end(new Buffer(body.str).toString('hex'))\n  })\n})\n\nserver.listen(8080)\n```\n\nIn this example, an http client just has to send:\n\n```json\n{\n  \"str\": 1000\n}\n```\n\nand it will get back 1,000 bytes of uninitialized memory from the server.\n\nThis is a very serious bug. It's similar in severity to the\n[the Heartbleed bug](http://heartbleed.com/) that allowed disclosure of OpenSSL process\nmemory by remote attackers.\n\n\n### Which real-world packages were vulnerable?\n\n#### [`bittorrent-dht`](https://www.npmjs.com/package/bittorrent-dht)\n\n[Mathias Buus](https://github.com/mafintosh) and I\n([Feross Aboukhadijeh](http://feross.org/)) found this issue in one of our own packages,\n[`bittorrent-dht`](https://www.npmjs.com/package/bittorrent-dht). The bug would allow\nanyone on the internet to send a series of messages to a user of `bittorrent-dht` and get\nthem to reveal 20 bytes at a time of uninitialized memory from the node.js process.\n\nHere's\n[the commit](https://github.com/feross/bittorrent-dht/commit/6c7da04025d5633699800a99ec3fbadf70ad35b8)\nthat fixed it. We released a new fixed version, created a\n[Node Security Project disclosure](https://nodesecurity.io/advisories/68), and deprecated all\nvulnerable versions on npm so users will get a warning to upgrade to a newer version.\n\n#### [`ws`](https://www.npmjs.com/package/ws)\n\nThat got us wondering if there were other vulnerable packages. Sure enough, within a short\nperiod of time, we found the same issue in [`ws`](https://www.npmjs.com/package/ws), the\nmost popular WebSocket implementation in node.js.\n\nIf certain APIs were called with `Number` parameters instead of `String` or `Buffer` as\nexpected, then uninitialized server memory would be disclosed to the remote peer.\n\nThese were the vulnerable methods:\n\n```js\nsocket.send(number)\nsocket.ping(number)\nsocket.pong(number)\n```\n\nHere's a vulnerable socket server with some echo functionality:\n\n```js\nserver.on('connection', function (socket) {\n  socket.on('message', function (message) {\n    message = JSON.parse(message)\n    if (message.type === 'echo') {\n      socket.send(message.data) // send back the user's message\n    }\n  })\n})\n```\n\n`socket.send(number)` called on the server, will disclose server memory.\n\nHere's [the release](https://github.com/websockets/ws/releases/tag/1.0.1) where the issue\nwas fixed, with a more detailed explanation. Props to\n[Arnout Kazemier](https://github.com/3rd-Eden) for the quick fix. Here's the\n[Node Security Project disclosure](https://nodesecurity.io/advisories/67).\n\n\n### What's the solution?\n\nIt's important that node.js offers a fast way to get memory otherwise performance-critical\napplications would needlessly get a lot slower.\n\nBut we need a better way to *signal our intent* as programmers. **When we want\nuninitialized memory, we should request it explicitly.**\n\nSensitive functionality should not be packed into a developer-friendly API that loosely\naccepts many different types. This type of API encourages the lazy practice of passing\nvariables in without checking the type very carefully.\n\n#### A new API: `Buffer.allocUnsafe(number)`\n\nThe functionality of creating buffers with uninitialized memory should be part of another\nAPI. We propose `Buffer.allocUnsafe(number)`. This way, it's not part of an API that\nfrequently gets user input of all sorts of different types passed into it.\n\n```js\nvar buf = Buffer.allocUnsafe(16) // careful, uninitialized memory!\n\n// Immediately overwrite the uninitialized buffer with data from another buffer\nfor (var i = 0; i < buf.length; i++) {\n  buf[i] = otherBuf[i]\n}\n```\n\n\n### How do we fix node.js core?\n\nWe sent [a PR to node.js core](https://github.com/nodejs/node/pull/4514) (merged as\n`semver-major`) which defends against one case:\n\n```js\nvar str = 16\nnew Buffer(str, 'utf8')\n```\n\nIn this situation, it's implied that the programmer intended the first argument to be a\nstring, since they passed an encoding as a second argument. Today, node.js will allocate\nuninitialized memory in the case of `new Buffer(number, encoding)`, which is probably not\nwhat the programmer intended.\n\nBut this is only a partial solution, since if the programmer does `new Buffer(variable)`\n(without an `encoding` parameter) there's no way to know what they intended. If `variable`\nis sometimes a number, then uninitialized memory will sometimes be returned.\n\n### What's the real long-term fix?\n\nWe could deprecate and remove `new Buffer(number)` and use `Buffer.allocUnsafe(number)` when\nwe need uninitialized memory. But that would break 1000s of packages.\n\n~~We believe the best solution is to:~~\n\n~~1. Change `new Buffer(number)` to return safe, zeroed-out memory~~\n\n~~2. Create a new API for creating uninitialized Buffers. We propose: `Buffer.allocUnsafe(number)`~~\n\n#### Update\n\nWe now support adding three new APIs:\n\n- `Buffer.from(value)` - convert from any type to a buffer\n- `Buffer.alloc(size)` - create a zero-filled buffer\n- `Buffer.allocUnsafe(size)` - create an uninitialized buffer with given size\n\nThis solves the core problem that affected `ws` and `bittorrent-dht` which is\n`Buffer(variable)` getting tricked into taking a number argument.\n\nThis way, existing code continues working and the impact on the npm ecosystem will be\nminimal. Over time, npm maintainers can migrate performance-critical code to use\n`Buffer.allocUnsafe(number)` instead of `new Buffer(number)`.\n\n\n### Conclusion\n\nWe think there's a serious design issue with the `Buffer` API as it exists today. It\npromotes insecure software by putting high-risk functionality into a convenient API\nwith friendly \"developer ergonomics\".\n\nThis wasn't merely a theoretical exercise because we found the issue in some of the\nmost popular npm packages.\n\nFortunately, there's an easy fix that can be applied today. Use `safe-buffer` in place of\n`buffer`.\n\n```js\nvar Buffer = require('safe-buffer').Buffer\n```\n\nEventually, we hope that node.js core can switch to this new, safer behavior. We believe\nthe impact on the ecosystem would be minimal since it's not a breaking change.\nWell-maintained, popular packages would be updated to use `Buffer.alloc` quickly, while\nolder, insecure packages would magically become safe from this attack vector.\n\n\n## links\n\n- [Node.js PR: buffer: throw if both length and enc are passed](https://github.com/nodejs/node/pull/4514)\n- [Node Security Project disclosure for `ws`](https://nodesecurity.io/advisories/67)\n- [Node Security Project disclosure for`bittorrent-dht`](https://nodesecurity.io/advisories/68)\n\n\n## credit\n\nThe original issues in `bittorrent-dht`\n([disclosure](https://nodesecurity.io/advisories/68)) and\n`ws` ([disclosure](https://nodesecurity.io/advisories/67)) were discovered by\n[Mathias Buus](https://github.com/mafintosh) and\n[Feross Aboukhadijeh](http://feross.org/).\n\nThanks to [Adam Baldwin](https://github.com/evilpacket) for helping disclose these issues\nand for his work running the [Node Security Project](https://nodesecurity.io/).\n\nThanks to [John Hiesey](https://github.com/jhiesey) for proofreading this README and\nauditing the code.\n\n\n## license\n\nMIT. Copyright (C) [Feross Aboukhadijeh](http://feross.org)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{7d/9c/67b237daaa38e11f0dd0f5d723cb9f9a858cbe748f9f9abaf3228c7804aaa67e34e621583f6a5b2e98044742cbc4a3460372e25b9d5134af97d7b6e1636f → 1b/5a/bb9bb6d8dcb2a2f8b62ade03b8f2b350d03c3b0fffc173a5d758bf1f52d721feae8726b8187feb929b5b6f84b93655b7c628b9e3afebe63531add55885cc}

@@ -9287,7 +9287,7 @@
   "dist-tags": {
     "latest": "4.17.21"
   },
-  "_rev": "2707-aedc1fc510b4a453",
+  "_rev": "2729-052ed65b2c517b7d",
   "_id": "lodash",
   "readme": "# lodash v4.17.21\n\nThe [Lodash](https://lodash.com/) library exported as [Node.js](https://nodejs.org/) modules.\n\n## Installation\n\nUsing npm:\n```shell\n$ npm i -g npm\n$ npm i --save lodash\n```\n\nIn Node.js:\n```js\n// Load the full build.\nvar _ = require('lodash');\n// Load the core build.\nvar _ = require('lodash/core');\n// Load the FP build for immutable auto-curried iteratee-first data-last methods.\nvar fp = require('lodash/fp');\n\n// Load method categories.\nvar array = require('lodash/array');\nvar object = require('lodash/fp/object');\n\n// Cherry-pick methods for smaller browserify/rollup/webpack bundles.\nvar at = require('lodash/at');\nvar curryN = require('lodash/fp/curryN');\n```\n\nSee the [package source](https://github.com/lodash/lodash/tree/4.17.21-npm) for more details.\n\n**Note:**<br>\nInstall [n_](https://www.npmjs.com/package/n_) for Lodash use in the Node.js < 6 REPL.\n\n## Support\n\nTested in Chrome 74-75, Firefox 66-67, IE 11, Edge 18, Safari 11-12, & Node.js 8-12.<br>\nAutomated [browser](https://saucelabs.com/u/lodash) & [CI](https://travis-ci.org/lodash/lodash/) test runs are available.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{7a/9f/22eef7ec0ad9a6a16102e450c20a77f880e118fae9044a9ab82ecc9845ec6bbd3cf862dc04b060cd87862ca076c099b7dbdb0f1f3d4db67be7ef05650925 → 1c/d0/6d922213a31ae19ca90f4193752dd53fb3f2423dc8720c0a947809ec2f32adc8865c70ec0034f0a1d1920fc98c4186a7081fd4d5da967b645f45d17c40c9}

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

package/npm-cache/_cacache/content-v2/sha512/{5f/96/965cf8a9bd863bdb31b1b9d99e52290a0dd56ddba1053ffc99a7501acb68e1771b205018891c033ec3557cf12c4c00132b809eebd95f32f75c645ca23016 → 1c/d5/e4cafa86ce88488c544f0885815cc63e3cf02f95471fc6dc499c058bd951e5678a96fd90e8f7f05b00e3d3ad550f3a52e1094da25f7d49baa189fc46cc16}

@@ -10224,7 +10224,7 @@
     "legacy-v4": "4.2.3",
     "legacy-v7": "7.4.6"
   },
-  "_rev": "3814-3cb695f3403e99eb",
+  "_rev": "3838-9c07b942017882fe",
   "_id": "minimatch",
   "readme": "# minimatch\n\nA minimal matching utility.\n\nThis is the matching library used internally by npm.\n\nIt works by converting glob expressions into JavaScript `RegExp`\nobjects.\n\n## Usage\n\n```js\n// hybrid module, load with require() or import\nimport { minimatch } from 'minimatch'\n// or:\nconst { minimatch } = require('minimatch')\n\nminimatch('bar.foo', '*.foo') // true!\nminimatch('bar.foo', '*.bar') // false!\nminimatch('bar.foo', '*.+(bar|foo)', { debug: true }) // true, and noisy!\n```\n\n## Features\n\nSupports these glob features:\n\n- Brace Expansion\n- Extended glob matching\n- \"Globstar\" `**` matching\n- [Posix character\n  classes](https://www.gnu.org/software/bash/manual/html_node/Pattern-Matching.html),\n  like `[[:alpha:]]`, supporting the full range of Unicode\n  characters. For example, `[[:alpha:]]` will match against\n  `'é'`, though `[a-zA-Z]` will not. Collating symbol and set\n  matching is not supported, so `[[=e=]]` will _not_ match `'é'`\n  and `[[.ch.]]` will not match `'ch'` in locales where `ch` is\n  considered a single character.\n\nSee:\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\n## Windows\n\n**Please only use forward-slashes in glob expressions.**\n\nThough windows uses either `/` or `\\` as its path separator, only `/`\ncharacters are used by this glob implementation. You must use\nforward-slashes **only** in glob expressions. Back-slashes in patterns\nwill always be interpreted as escape characters, not path separators.\n\nNote that `\\` or `/` _will_ be interpreted as path separators in paths on\nWindows, and will match against `/` in glob expressions.\n\nSo just always use `/` in patterns.\n\n### UNC Paths\n\nOn Windows, UNC paths like `//?/c:/...` or\n`//ComputerName/Share/...` are handled specially.\n\n- Patterns starting with a double-slash followed by some\n  non-slash characters will preserve their double-slash. As a\n  result, a pattern like `//*` will match `//x`, but not `/x`.\n- Patterns staring with `//?/<drive letter>:` will _not_ treat\n  the `?` as a wildcard character. Instead, it will be treated\n  as a normal string.\n- Patterns starting with `//?/<drive letter>:/...` will match\n  file paths starting with `<drive letter>:/...`, and vice versa,\n  as if the `//?/` was not present. This behavior only is\n  present when the drive letters are a case-insensitive match to\n  one another. The remaining portions of the path/pattern are\n  compared case sensitively, unless `nocase:true` is set.\n\nNote that specifying a UNC path using `\\` characters as path\nseparators is always allowed in the file path argument, but only\nallowed in the pattern argument when `windowsPathsNoEscape: true`\nis set in the options.\n\n## Minimatch Class\n\nCreate a minimatch object by instantiating the `minimatch.Minimatch` class.\n\n```javascript\nvar Minimatch = require('minimatch').Minimatch\nvar mm = new Minimatch(pattern, options)\n```\n\n### Properties\n\n- `pattern` The original pattern the minimatch object represents.\n- `options` The options supplied to the constructor.\n- `set` A 2-dimensional array of regexp or string expressions.\n  Each row in the\n  array corresponds to a brace-expanded pattern. Each item in the row\n  corresponds to a single path-part. For example, the pattern\n  `{a,b/c}/d` would expand to a set of patterns like:\n\n        [ [ a, d ]\n        , [ b, c, d ] ]\n\n  If a portion of the pattern doesn't have any \"magic\" in it\n  (that is, it's something like `\"foo\"` rather than `fo*o?`), then it\n  will be left as a string rather than converted to a regular\n  expression.\n\n- `regexp` Created by the `makeRe` method. A single regular expression\n  expressing the entire pattern. This is useful in cases where you wish\n  to use the pattern somewhat like `fnmatch(3)` with `FNM_PATH` enabled.\n- `negate` True if the pattern is negated.\n- `comment` True if the pattern is a comment.\n- `empty` True if the pattern is `\"\"`.\n\n### Methods\n\n- `makeRe()` Generate the `regexp` member if necessary, and return it.\n  Will return `false` if the pattern is invalid.\n- `match(fname)` Return true if the filename matches the pattern, or\n  false otherwise.\n- `matchOne(fileArray, patternArray, partial)` Take a `/`-split\n  filename, and match it against a single row in the `regExpSet`. This\n  method is mainly for internal use, but is exposed so that it can be\n  used by a glob-walker that needs to avoid excessive filesystem calls.\n- `hasMagic()` Returns true if the parsed pattern contains any\n  magic characters. Returns false if all comparator parts are\n  string literals. If the `magicalBraces` option is set on the\n  constructor, then it will consider brace expansions which are\n  not otherwise magical to be magic. If not set, then a pattern\n  like `a{b,c}d` will return `false`, because neither `abd` nor\n  `acd` contain any special glob characters.\n\n  This does **not** mean that the pattern string can be used as a\n  literal filename, as it may contain magic glob characters that\n  are escaped. For example, the pattern `\\\\*` or `[*]` would not\n  be considered to have magic, as the matching portion parses to\n  the literal string `'*'` and would match a path named `'*'`,\n  not `'\\\\*'` or `'[*]'`. The `minimatch.unescape()` method may\n  be used to remove escape characters.\n\nAll other methods are internal, and will be called as necessary.\n\n### minimatch(path, pattern, options)\n\nMain export. Tests a path against the pattern using the options.\n\n```javascript\nvar isJS = minimatch(file, '*.js', { matchBase: true })\n```\n\n### minimatch.filter(pattern, options)\n\nReturns a function that tests its\nsupplied argument, suitable for use with `Array.filter`. Example:\n\n```javascript\nvar javascripts = fileList.filter(minimatch.filter('*.js', { matchBase: true }))\n```\n\n### minimatch.escape(pattern, options = {})\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### minimatch.unescape(pattern, options = {})\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### minimatch.match(list, pattern, options)\n\nMatch against the list of\nfiles, in the style of fnmatch or glob. If nothing is matched, and\noptions.nonull is set, then return a list containing the pattern itself.\n\n```javascript\nvar javascripts = minimatch.match(fileList, '*.js', { matchBase: true })\n```\n\n### minimatch.makeRe(pattern, options)\n\nMake a regular expression object from the pattern.\n\n## Options\n\nAll options are `false` by default.\n\n### debug\n\nDump a ton of stuff to stderr.\n\n### nobrace\n\nDo not expand `{a,b}` and `{1..3}` brace sets.\n\n### noglobstar\n\nDisable `**` matching against multiple folder names.\n\n### dot\n\nAllow patterns to match filenames starting with a period, even if\nthe pattern does not explicitly have a period in that spot.\n\nNote that by default, `a/**/b` will **not** match `a/.d/b`, unless `dot`\nis set.\n\n### noext\n\nDisable \"extglob\" style patterns like `+(a|b)`.\n\n### nocase\n\nPerform a case-insensitive match.\n\n### nocaseMagicOnly\n\nWhen used with `{nocase: true}`, create regular expressions that\nare case-insensitive, but leave string match portions untouched.\nHas no effect when used without `{nocase: true}`.\n\nUseful when some other form of case-insensitive matching is used,\nor if the original string representation is useful in some other\nway.\n\n### nonull\n\nWhen a match is not found by `minimatch.match`, return a list containing\nthe pattern itself if this option is set. When not set, an empty list\nis returned if there are no matches.\n\n### magicalBraces\n\nThis only affects the results of the `Minimatch.hasMagic` method.\n\nIf the pattern contains brace expansions, such as `a{b,c}d`, but\nno other magic characters, then the `Minimatch.hasMagic()` method\nwill return `false` by default. When this option set, it will\nreturn `true` for brace expansion as well as other magic glob\ncharacters.\n\n### matchBase\n\nIf set, then patterns without slashes will be matched\nagainst the basename of the path if it contains slashes. For example,\n`a?b` would match the path `/xyz/123/acb`, but not `/xyz/acb/123`.\n\n### nocomment\n\nSuppress the behavior of treating `#` at the start of a pattern as a\ncomment.\n\n### nonegate\n\nSuppress the behavior of treating a leading `!` character as negation.\n\n### flipNegate\n\nReturns from negate expressions the same as if they were not negated.\n(Ie, true on a hit, false on a miss.)\n\n### partial\n\nCompare a partial path to a pattern. As long as the parts of the path that\nare present are not contradicted by the pattern, it will be treated as a\nmatch. This is useful in applications where you're walking through a\nfolder structure, and don't yet have the full path, but want to ensure that\nyou do not walk down paths that can never be a match.\n\nFor example,\n\n```js\nminimatch('/a/b', '/a/*/c/d', { partial: true }) // true, might be /a/b/c/d\nminimatch('/a/b', '/**/d', { partial: true }) // true, might be /a/b/.../d\nminimatch('/x/y/z', '/a/**/z', { partial: true }) // false, because x !== a\n```\n\n### windowsPathsNoEscape\n\nUse `\\\\` as a path separator _only_, and _never_ as an escape\ncharacter. If set, all `\\\\` characters are replaced with `/` in\nthe pattern. Note that this makes it **impossible** to match\nagainst paths containing literal glob pattern characters, but\nallows matching with patterns constructed using `path.join()` and\n`path.resolve()` on Windows platforms, mimicking the (buggy!)\nbehavior of earlier versions on Windows. Please use with\ncaution, and be mindful of [the caveat about Windows\npaths](#windows).\n\nFor legacy reasons, this is also set if\n`options.allowWindowsEscape` is set to the exact value `false`.\n\n### windowsNoMagicRoot\n\nWhen a pattern starts with a UNC path or drive letter, and in\n`nocase:true` mode, do not convert the root portions of the\npattern into a case-insensitive regular expression, and instead\nleave them as strings.\n\nThis is the default when the platform is `win32` and\n`nocase:true` is set.\n\n### preserveMultipleSlashes\n\nBy default, multiple `/` characters (other than the leading `//`\nin a UNC path, see \"UNC Paths\" above) are treated as a single\n`/`.\n\nThat is, a pattern like `a///b` will match the file path `a/b`.\n\nSet `preserveMultipleSlashes: true` to suppress this behavior.\n\n### optimizationLevel\n\nA number indicating the level of optimization that should be done\nto the pattern prior to parsing and using it for matches.\n\nGlobstar parts `**` are always converted to `*` when `noglobstar`\nis set, and multiple adjacent `**` parts are converted into a\nsingle `**` (ie, `a/**/**/b` will be treated as `a/**/b`, as this\nis equivalent in all cases).\n\n- `0` - Make no further changes. In this mode, `.` and `..` are\n  maintained in the pattern, meaning that they must also appear\n  in the same position in the test path string. Eg, a pattern\n  like `a/*/../c` will match the string `a/b/../c` but not the\n  string `a/c`.\n- `1` - (default) Remove cases where a double-dot `..` follows a\n  pattern portion that is not `**`, `.`, `..`, or empty `''`. For\n  example, the pattern `./a/b/../*` is converted to `./a/*`, and\n  so it will match the path string `./a/c`, but not the path\n  string `./a/b/../c`. Dots and empty path portions in the\n  pattern are preserved.\n- `2` (or higher) - Much more aggressive optimizations, suitable\n  for use with file-walking cases:\n  - Remove cases where a double-dot `..` follows a pattern\n    portion that is not `**`, `.`, or empty `''`. Remove empty\n    and `.` portions of the pattern, where safe to do so (ie,\n    anywhere other than the last position, the first position, or\n    the second position in a pattern starting with `/`, as this\n    may indicate a UNC path on Windows).\n  - Convert patterns containing `<pre>/**/../<p>/<rest>` into the\n    equivalent `<pre>/{..,**}/<p>/<rest>`, where `<p>` is a\n    a pattern portion other than `.`, `..`, `**`, or empty\n    `''`.\n  - Dedupe patterns where a `**` portion is present in one and\n    omitted in another, and it is not the final path portion, and\n    they are otherwise equivalent. So `{a/**/b,a/b}` becomes\n    `a/**/b`, because `**` matches against an empty path portion.\n  - Dedupe patterns where a `*` portion is present in one, and a\n    non-dot pattern other than `**`, `.`, `..`, or `''` is in the\n    same position in the other. So `a/{*,x}/b` becomes `a/*/b`,\n    because `*` can match against `x`.\n\n  While these optimizations improve the performance of\n  file-walking use cases such as [glob](http://npm.im/glob) (ie,\n  the reason this module exists), there are cases where it will\n  fail to match a literal string that would have been matched in\n  optimization level 1 or 0.\n\n  Specifically, while the `Minimatch.match()` method will\n  optimize the file path string in the same ways, resulting in\n  the same matches, it will fail when tested with the regular\n  expression provided by `Minimatch.makeRe()`, unless the path\n  string is first processed with\n  `minimatch.levelTwoFileOptimize()` or similar.\n\n### platform\n\nWhen set to `win32`, this will trigger all windows-specific\nbehaviors (special handling for UNC paths, and treating `\\` as\nseparators in file paths for comparison.)\n\nDefaults to the value of `process.platform`.\n\n## Comparisons to other fnmatch/glob implementations\n\nWhile strict compliance with the existing standards is a\nworthwhile goal, some discrepancies exist between minimatch and\nother implementations. Some are intentional, and some are\nunavoidable.\n\nIf the pattern starts with a `!` character, then it is negated. Set the\n`nonegate` flag to suppress this behavior, and treat leading `!`\ncharacters normally. This is perhaps relevant if you wish to start the\npattern with a negative extglob pattern like `!(a|B)`. Multiple `!`\ncharacters at the start of a pattern will negate the pattern multiple\ntimes.\n\nIf a pattern starts with `#`, then it is treated as a comment, and\nwill not match anything. Use `\\#` to match a literal `#` at the\nstart of a line, or set the `nocomment` flag to suppress this behavior.\n\nThe double-star character `**` is supported by default, unless the\n`noglobstar` flag is set. This is supported in the manner of bsdglob\nand bash 4.1, where `**` only has special significance if it is the only\nthing in a path part. That is, `a/**/b` will match `a/x/y/b`, but\n`a/**b` will not.\n\nIf an escaped pattern has no matches, and the `nonull` flag is set,\nthen minimatch.match returns the pattern as-provided, rather than\ninterpreting the character escapes. For example,\n`minimatch.match([], \"\\\\*a\\\\?\")` will return `\"\\\\*a\\\\?\"` rather than\n`\"*a?\"`. This is akin to setting the `nullglob` option in bash, except\nthat it does not resolve escaped pattern characters.\n\nIf brace expansion is not disabled, then it is performed before any\nother interpretation of the glob pattern. Thus, a pattern like\n`+(a|{b),c)}`, which would not be valid in bash or zsh, is expanded\n**first** into the set of `+(a|b)` and `+(a|c)`, and those patterns are\nchecked for validity. Since those two are valid, matching proceeds.\n\nNegated extglob patterns are handled as closely as possible to\nBash semantics, but there are some cases with negative extglobs\nwhich are exceedingly difficult to express in a JavaScript\nregular expression. In particular the negated pattern\n`<start>!(<pattern>*|)*` will in bash match anything that does\nnot start with `<start><pattern>`. However,\n`<start>!(<pattern>*)*` _will_ match paths starting with\n`<start><pattern>`, because the empty string can match against\nthe negated portion. In this library, `<start>!(<pattern>*|)*`\nwill _not_ match any pattern starting with `<start>`, due to a\ndifference in precisely which patterns are considered \"greedy\" in\nRegular Expressions vs bash path expansion. This may be fixable,\nbut not without incurring some complexity and performance costs,\nand the trade-off seems to not be worth pursuing.\n\nNote that `fnmatch(3)` in libc is an extremely naive string comparison\nmatcher, which does not do anything special for slashes. This library is\ndesigned to be used in glob searching and file walkers, and so it does do\nspecial things with `/`. Thus, `foo*` will not match `foo/bar` in this\nlibrary, even though it would in `fnmatch(3)`.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{8a/43/cd0246636445a6d95c2bd0e5771a9329901d468e931e49fa5b2401de4e8879a0c523053acc5c3941da210ab3807c47f6b2470fc617a3c02cff575c168946 → 1e/3e/daea216b238e1a4e589e31f1a471f01d3c245b3c85a4fb8aff8baa1d76f772ff905711e87b9b90f58321d2400c0316cd89f18b50a27a76fd718475b763b3}

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

package/npm-cache/_cacache/content-v2/sha512/{4b/3b/faf13407dd4684f3538992d4d5b9d19cc069958bd58ef8e6457d1dfe956f8edf25a084889c1c35c32d17c52a66e85ef072dd349309476258eea732ac7acc → 1e/ea/b9533c77badfddef59215fcd20ccc5c99293205c0790661fae93b5d609fb665f67237588c3ca91776337b98aef8a30152df81e3d4cd95cd60dead7020adb}

@@ -6200,7 +6200,7 @@
   "dist-tags": {
     "latest": "5.3.8"
   },
-  "_rev": "269-37af4611fc23a54f",
+  "_rev": "280-4270e59ab01ed6d1",
   "_id": "@smithy/protocol-http",
   "readme": "# @smithy/protocol-http\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/protocol-http/latest.svg)](https://www.npmjs.com/package/@smithy/protocol-http)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/protocol-http.svg)](https://www.npmjs.com/package/@smithy/protocol-http)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{0e/c9/2970444eb8ff77a8f46ea4fbe443bead51934795b0b2e1c351128c61d8acf5fd404fca538888419d35f9269eae484a38a7855f042a5fac7faab0ebbd4f7c → 1f/20/250da611cd9f4a29def29e70f9a51119b031395c8f4eb993d2b9a835512628ed809c4811612d3d90b7dfb8de999f535a866d085bba5cf60da84de3634ce4}

@@ -226,7 +226,7 @@
   "dist-tags": {
     "latest": "1.0.1"
   },
-  "_rev": "844-ea0988f745137d64",
+  "_rev": "862-c091ab63891327ef",
   "_id": "package-json-from-dist",
   "readme": "# package-json-from-dist\n\nSometimes you want to load the `package.json` into your\nTypeScript program, and it's tempting to just `import\n'../package.json'`, since that seems to work.\n\nHowever, this requires `tsc` to make an entire copy of your\n`package.json` file into the `dist` folder, which is a problem if\nyou're using something like\n[tshy](https://github.com/isaacs/tshy), which uses the\n`package.json` file in dist for another purpose. Even when that\ndoes work, it's asking the module system to do a bunch of extra\nfs system calls, just to load a version number or something. (See\n[this issue](https://github.com/isaacs/tshy/issues/61).)\n\nThis module helps by just finding the package.json file\nappropriately, and reading and parsing it in the most normal\nfashion.\n\n## Caveats\n\nThis _only_ works if your code builds into a target folder called\n`dist`, which is in the root of the package. It also requires\nthat you do not have a folder named `node_modules` anywhere\nwithin your dev environment, or else it'll get the wrong answers\nthere. (But, at least, that'll be in dev, so you're pretty likely\nto notice.)\n\nIf you build to some other location, then you'll need a different\napproach. (Feel free to fork this module and make it your own, or\njust put the code right inline, there's not much of it.)\n\n## USAGE\n\n```js\n// src/index.ts\nimport {\n  findPackageJson,\n  loadPackageJson,\n} from 'package-json-from-dist'\n\nconst pj = findPackageJson(import.meta.url)\nconsole.log(`package.json found at ${pj}`)\n\nconst pkg = loadPackageJson(import.meta.url)\nconsole.log(`Hello from ${pkg.name}@${pkg.version}`)\n```\n\nIf your module is not directly in the `./src` folder, then you need\nto specify the path that you would expect to find the\n`package.json` when it's _not_ built to the `dist` folder.\n\n```js\n// src/components/something.ts\nimport {\n  findPackageJson,\n  loadPackageJson,\n} from 'package-json-from-dist'\n\nconst pj = findPackageJson(import.meta.url, '../../package.json')\nconsole.log(`package.json found at ${pj}`)\n\nconst pkg = loadPackageJson(import.meta.url, '../../package.json')\nconsole.log(`Hello from ${pkg.name}@${pkg.version}`)\n```\n\nWhen running from CommmonJS, use `__filename` instead of\n`import.meta.url`.\n\n```js\n// src/index.cts\nimport {\n  findPackageJson,\n  loadPackageJson,\n} from 'package-json-from-dist'\n\nconst pj = findPackageJson(__filename)\nconsole.log(`package.json found at ${pj}`)\n\nconst pkg = loadPackageJson(__filename)\nconsole.log(`Hello from ${pkg.name}@${pkg.version}`)\n```\n\nSince [tshy](https://github.com/isaacs/tshy) builds _both_\nCommonJS and ESM by default, you may find that you need a\nCommonJS override and some `//@ts-ignore` magic to make it work.\n\n`src/pkg.ts`:\n\n```js\nimport {\n  findPackageJson,\n  loadPackageJson,\n} from 'package-json-from-dist'\n//@ts-ignore\nexport const pkg = loadPackageJson(import.meta.url)\n//@ts-ignore\nexport const pj = findPackageJson(import.meta.url)\n```\n\n`src/pkg-cjs.cts`:\n\n```js\nimport {\n  findPackageJson,\n  loadPackageJson,\n} from 'package-json-from-dist'\nexport const pkg = loadPackageJson(__filename)\nexport const pj = findPackageJson(__filename)\n```",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{cc/b5/51726bfae717fe00c755cec3601b228c4c89087c51cfa98d9dd01a5e0c3c513ba98a4b36eb964d5325ddc7fe66173ea73d2dcef4942b04b1295fb1537030 → 1f/58/4f59ec89927dd44240e7ad50dc6cfc3ae5a9120ae869801927fa09bc9d1370b02c9f6596fe71940885749848a54fed655fbf890c58c5bb29182bd021d0c9}

@@ -6333,7 +6333,7 @@
   "dist-tags": {
     "latest": "4.2.8"
   },
-  "_rev": "176-6fe4587a092ea347",
+  "_rev": "188-983478645620ce4d",
   "_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/{05/36/8aee1d83e463945db01ccab18bea16de071e218f531c2fcf0217e2ef53978d08028df68c78f428b3406f002616ca36b8c5d6694d613b696a5987e7e78a8e → 21/0a/bbde65edfd9efa6a56850559ae0439eea6e088b299abdcf08d485ae60353c2415ebdd738970c24090cb44b9e00344277ccf1745471868dbcc579cadda45a}

@@ -6564,7 +6564,7 @@
   "dist-tags": {
     "latest": "4.2.9"
   },
-  "_rev": "179-f6c47fbd2acaa43b",
+  "_rev": "190-85b124ede43b8dc3",
   "_id": "@smithy/middleware-serde",
   "readme": "# @smithy/middleware-serde\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/middleware-serde/latest.svg)](https://www.npmjs.com/package/@smithy/middleware-serde)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/middleware-serde.svg)](https://www.npmjs.com/package/@smithy/middleware-serde)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{3c/67/d3b36b5056becc0b726c375522c0d73bdf39b644e7fc5edd9acb54e0e7f9875f6770c419576f894a049b4de9e0224bda29a760111ed977a5c86d2bea8556 → 22/b2/6abbffd16ab81356a084516709d726ba8ea727558be2907430c3ccc85cf7a4d8c6b02645a25438014361401ef2b102446e837dbf7c7d321f7066462af875}

@@ -5844,7 +5844,7 @@
   "dist-tags": {
     "latest": "4.3.8"
   },
-  "_rev": "182-e6c98deca9c5dfde",
+  "_rev": "193-b9865f5ecd132608",
   "_id": "@smithy/eventstream-serde-config-resolver",
   "readme": "# @smithy/eventstream-serde-config-resolver\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/eventstream-serde-config-resolver/latest.svg)](https://www.npmjs.com/package/@smithy/eventstream-serde-config-resolver)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/eventstream-serde-config-resolver.svg)](https://www.npmjs.com/package/@smithy/eventstream-serde-config-resolver)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{fb/86/62fb79add1dbddc00e1bb586996f4826b16d7eeb0da71cb94ff3d768dfcca8f69e92485c308947f36a4a2dd1548f2f6c75461d56d0081cb486eaab35d81b → 26/51/93b8101b62820bd53964cee13c2d1636c6c5c4375d71762ed04a8e4355a42928ebdb1f712a4a4f89851a19466cbcf9d187c2f83f5570d26e794e1ed3ba64}

@@ -7605,7 +7605,7 @@
   "dist-tags": {
     "latest": "4.4.6"
   },
-  "_rev": "186-e89a673ee9f769ef",
+  "_rev": "197-5474d8535f13f3e5",
   "_id": "@smithy/config-resolver",
   "readme": "# @smithy/config-resolver\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/config-resolver/latest.svg)](https://www.npmjs.com/package/@smithy/config-resolver)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/config-resolver.svg)](https://www.npmjs.com/package/@smithy/config-resolver)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{83/ee/1d2a420faf48221ef62a08b5ab1108a9b92d1dad013d87d847be3cf756cb7766ba766b293fe1ec03845c9e09e3c2fa8a09102568cf61bd66bdec5766f01f → 26/b0/d99a8ae095f50713d976b79a4e93fdeda359b56635445243d8a329b77b4c3e6b6ae189db992e9948265c362218991d92f55b77f7c5e2305b911d5bffd782}

@@ -695,7 +695,7 @@
   "dist-tags": {
     "latest": "2.1.0"
   },
-  "_rev": "4183-f848bb6717329ab9",
+  "_rev": "4205-5f8ddd5bb4a04c9a",
   "_id": "color-name",
   "readme": "A JSON with color names and its values. Based on http://dev.w3.org/csswg/css-color/#named-colors.\n\n[![NPM](https://nodei.co/npm/color-name.png?mini=true)](https://nodei.co/npm/color-name/)\n\n\n```js\nimport colors from 'color-name';\ncolors.red // [255,0,0]\n```\n\n<a href=\"LICENSE\"><img src=\"https://upload.wikimedia.org/wikipedia/commons/0/0c/MIT_logo.svg\" width=\"120\"/></a>",
   "_attachments": {}