mrs-toolbox-cli 0.1.26 → 0.1.27

package/npm-cache/_cacache/content-v2/sha512/{70/55/c09464fb9d6690a93aef13cc78b7cfb38d57aaa780a5a55edd9e56f773e1ac370c1cec9d264889d265c0ffebc69acdac41116ca3f53512dc3c213f9413a6 → c2/92/13b5429036d92a9037923807f16ffd9f8e2755aa9c57d061ec0411254ac0cf9696175d6eb6eed9d80d9d4df587ea5c6b835bc2a0d239ef777492305ec322}

@@ -9286,7 +9286,7 @@
     "next": "3.3.5",
     "legacy-v4": "4.2.8"
   },
-  "_rev": "962-5a253666a8f6d60c",
+  "_rev": "966-aaad2a289ecbf2c7",
   "_id": "minipass",
   "readme": "# minipass\n\nA _very_ minimal implementation of a [PassThrough\nstream](https://nodejs.org/api/stream.html#stream_class_stream_passthrough)\n\n[It's very\nfast](https://docs.google.com/spreadsheets/d/1K_HR5oh3r80b8WVMWCPPjfuWXUgfkmhlX7FGI6JJ8tY/edit?usp=sharing)\nfor objects, strings, and buffers.\n\nSupports `pipe()`ing (including multi-`pipe()` and backpressure\ntransmission), buffering data until either a `data` event handler\nor `pipe()` is added (so you don't lose the first chunk), and\nmost other cases where PassThrough is a good idea.\n\nThere is a `read()` method, but it's much more efficient to\nconsume data from this stream via `'data'` events or by calling\n`pipe()` into some other stream. Calling `read()` requires the\nbuffer to be flattened in some cases, which requires copying\nmemory.\n\nIf you set `objectMode: true` in the options, then whatever is\nwritten will be emitted. Otherwise, it'll do a minimal amount of\nBuffer copying to ensure proper Streams semantics when `read(n)`\nis called.\n\n`objectMode` can only be set at instantiation. Attempting to\nwrite something other than a String or Buffer without having set\n`objectMode` in the options will throw an error.\n\nThis is not a `through` or `through2` stream. It doesn't\ntransform the data, it just passes it right through. If you want\nto transform the data, extend the class, and override the\n`write()` method. Once you're done transforming the data however\nyou want, call `super.write()` with the transform output.\n\nFor some examples of streams that extend Minipass in various\nways, check out:\n\n- [minizlib](http://npm.im/minizlib)\n- [fs-minipass](http://npm.im/fs-minipass)\n- [tar](http://npm.im/tar)\n- [minipass-collect](http://npm.im/minipass-collect)\n- [minipass-flush](http://npm.im/minipass-flush)\n- [minipass-pipeline](http://npm.im/minipass-pipeline)\n- [tap](http://npm.im/tap)\n- [tap-parser](http://npm.im/tap-parser)\n- [treport](http://npm.im/treport)\n- [minipass-fetch](http://npm.im/minipass-fetch)\n- [pacote](http://npm.im/pacote)\n- [make-fetch-happen](http://npm.im/make-fetch-happen)\n- [cacache](http://npm.im/cacache)\n- [ssri](http://npm.im/ssri)\n- [npm-registry-fetch](http://npm.im/npm-registry-fetch)\n- [minipass-json-stream](http://npm.im/minipass-json-stream)\n- [minipass-sized](http://npm.im/minipass-sized)\n\n## Usage in TypeScript\n\nThe `Minipass` class takes three type template definitions:\n\n- `RType` the type being read, which defaults to `Buffer`. If\n  `RType` is `string`, then the constructor _must_ get an options\n  object specifying either an `encoding` or `objectMode: true`.\n  If it's anything other than `string` or `Buffer`, then it\n  _must_ get an options object specifying `objectMode: true`.\n- `WType` the type being written. If `RType` is `Buffer` or\n  `string`, then this defaults to `ContiguousData` (Buffer,\n  string, ArrayBuffer, or ArrayBufferView). Otherwise, it\n  defaults to `RType`.\n- `Events` type mapping event names to the arguments emitted\n  with that event, which extends `Minipass.Events`.\n\nTo declare types for custom events in subclasses, extend the\nthird parameter with your own event signatures. For example:\n\n```js\nimport { Minipass } from 'minipass'\n\n// a NDJSON stream that emits 'jsonError' when it can't stringify\nexport interface Events extends Minipass.Events {\n  jsonError: [e: Error]\n}\n\nexport class NDJSONStream extends Minipass<string, any, Events> {\n  constructor() {\n    super({ objectMode: true })\n  }\n\n  // data is type `any` because that's WType\n  write(data, encoding, cb) {\n    try {\n      const json = JSON.stringify(data)\n      return super.write(json + '\\n', encoding, cb)\n    } catch (er) {\n      if (!er instanceof Error) {\n        er = Object.assign(new Error('json stringify failed'), {\n          cause: er,\n        })\n      }\n      // trying to emit with something OTHER than an error will\n      // fail, because we declared the event arguments type.\n      this.emit('jsonError', er)\n    }\n  }\n}\n\nconst s = new NDJSONStream()\ns.on('jsonError', e => {\n  // here, TS knows that e is an Error\n})\n```\n\nEmitting/handling events that aren't declared in this way is\nfine, but the arguments will be typed as `unknown`.\n\n## Differences from Node.js Streams\n\nThere are several things that make Minipass streams different\nfrom (and in some ways superior to) Node.js core streams.\n\nPlease read these caveats if you are familiar with node-core\nstreams and intend to use Minipass streams in your programs.\n\nYou can avoid most of these differences entirely (for a very\nsmall performance penalty) by setting `{async: true}` in the\nconstructor options.\n\n### Timing\n\nMinipass streams are designed to support synchronous use-cases.\nThus, data is emitted as soon as it is available, always. It is\nbuffered until read, but no longer. Another way to look at it is\nthat Minipass streams are exactly as synchronous as the logic\nthat writes into them.\n\nThis can be surprising if your code relies on\n`PassThrough.write()` always providing data on the next tick\nrather than the current one, or being able to call `resume()` and\nnot have the entire buffer disappear immediately.\n\nHowever, without this synchronicity guarantee, there would be no\nway for Minipass to achieve the speeds it does, or support the\nsynchronous use cases that it does. Simply put, waiting takes\ntime.\n\nThis non-deferring approach makes Minipass streams much easier to\nreason about, especially in the context of Promises and other\nflow-control mechanisms.\n\nExample:\n\n```js\n// hybrid module, either works\nimport { Minipass } from 'minipass'\n// or:\nconst { Minipass } = require('minipass')\n\nconst stream = new Minipass()\nstream.on('data', () => console.log('data event'))\nconsole.log('before write')\nstream.write('hello')\nconsole.log('after write')\n// output:\n// before write\n// data event\n// after write\n```\n\n### Exception: Async Opt-In\n\nIf you wish to have a Minipass stream with behavior that more\nclosely mimics Node.js core streams, you can set the stream in\nasync mode either by setting `async: true` in the constructor\noptions, or by setting `stream.async = true` later on.\n\n```js\n// hybrid module, either works\nimport { Minipass } from 'minipass'\n// or:\nconst { Minipass } = require('minipass')\n\nconst asyncStream = new Minipass({ async: true })\nasyncStream.on('data', () => console.log('data event'))\nconsole.log('before write')\nasyncStream.write('hello')\nconsole.log('after write')\n// output:\n// before write\n// after write\n// data event <-- this is deferred until the next tick\n```\n\nSwitching _out_ of async mode is unsafe, as it could cause data\ncorruption, and so is not enabled. Example:\n\n```js\nimport { Minipass } from 'minipass'\nconst stream = new Minipass({ encoding: 'utf8' })\nstream.on('data', chunk => console.log(chunk))\nstream.async = true\nconsole.log('before writes')\nstream.write('hello')\nsetStreamSyncAgainSomehow(stream) // <-- this doesn't actually exist!\nstream.write('world')\nconsole.log('after writes')\n// hypothetical output would be:\n// before writes\n// world\n// after writes\n// hello\n// NOT GOOD!\n```\n\nTo avoid this problem, once set into async mode, any attempt to\nmake the stream sync again will be ignored.\n\n```js\nconst { Minipass } = require('minipass')\nconst stream = new Minipass({ encoding: 'utf8' })\nstream.on('data', chunk => console.log(chunk))\nstream.async = true\nconsole.log('before writes')\nstream.write('hello')\nstream.async = false // <-- no-op, stream already async\nstream.write('world')\nconsole.log('after writes')\n// actual output:\n// before writes\n// after writes\n// hello\n// world\n```\n\n### No High/Low Water Marks\n\nNode.js core streams will optimistically fill up a buffer,\nreturning `true` on all writes until the limit is hit, even if\nthe data has nowhere to go. Then, they will not attempt to draw\nmore data in until the buffer size dips below a minimum value.\n\nMinipass streams are much simpler. The `write()` method will\nreturn `true` if the data has somewhere to go (which is to say,\ngiven the timing guarantees, that the data is already there by\nthe time `write()` returns).\n\nIf the data has nowhere to go, then `write()` returns false, and\nthe data sits in a buffer, to be drained out immediately as soon\nas anyone consumes it.\n\nSince nothing is ever buffered unnecessarily, there is much less\ncopying data, and less bookkeeping about buffer capacity levels.\n\n### Hazards of Buffering (or: Why Minipass Is So Fast)\n\nSince data written to a Minipass stream is immediately written\nall the way through the pipeline, and `write()` always returns\ntrue/false based on whether the data was fully flushed,\nbackpressure is communicated immediately to the upstream caller.\nThis minimizes buffering.\n\nConsider this case:\n\n```js\nconst { PassThrough } = require('stream')\nconst p1 = new PassThrough({ highWaterMark: 1024 })\nconst p2 = new PassThrough({ highWaterMark: 1024 })\nconst p3 = new PassThrough({ highWaterMark: 1024 })\nconst p4 = new PassThrough({ highWaterMark: 1024 })\n\np1.pipe(p2).pipe(p3).pipe(p4)\np4.on('data', () => console.log('made it through'))\n\n// this returns false and buffers, then writes to p2 on next tick (1)\n// p2 returns false and buffers, pausing p1, then writes to p3 on next tick (2)\n// p3 returns false and buffers, pausing p2, then writes to p4 on next tick (3)\n// p4 returns false and buffers, pausing p3, then emits 'data' and 'drain'\n// on next tick (4)\n// p3 sees p4's 'drain' event, and calls resume(), emitting 'resume' and\n// 'drain' on next tick (5)\n// p2 sees p3's 'drain', calls resume(), emits 'resume' and 'drain' on next tick (6)\n// p1 sees p2's 'drain', calls resume(), emits 'resume' and 'drain' on next\n// tick (7)\n\np1.write(Buffer.alloc(2048)) // returns false\n```\n\nAlong the way, the data was buffered and deferred at each stage,\nand multiple event deferrals happened, for an unblocked pipeline\nwhere it was perfectly safe to write all the way through!\n\nFurthermore, setting a `highWaterMark` of `1024` might lead\nsomeone reading the code to think an advisory maximum of 1KiB is\nbeing set for the pipeline. However, the actual advisory\nbuffering level is the _sum_ of `highWaterMark` values, since\neach one has its own bucket.\n\nConsider the Minipass case:\n\n```js\nconst m1 = new Minipass()\nconst m2 = new Minipass()\nconst m3 = new Minipass()\nconst m4 = new Minipass()\n\nm1.pipe(m2).pipe(m3).pipe(m4)\nm4.on('data', () => console.log('made it through'))\n\n// m1 is flowing, so it writes the data to m2 immediately\n// m2 is flowing, so it writes the data to m3 immediately\n// m3 is flowing, so it writes the data to m4 immediately\n// m4 is flowing, so it fires the 'data' event immediately, returns true\n// m4's write returned true, so m3 is still flowing, returns true\n// m3's write returned true, so m2 is still flowing, returns true\n// m2's write returned true, so m1 is still flowing, returns true\n// No event deferrals or buffering along the way!\n\nm1.write(Buffer.alloc(2048)) // returns true\n```\n\nIt is extremely unlikely that you _don't_ want to buffer any data\nwritten, or _ever_ buffer data that can be flushed all the way\nthrough. Neither node-core streams nor Minipass ever fail to\nbuffer written data, but node-core streams do a lot of\nunnecessary buffering and pausing.\n\nAs always, the faster implementation is the one that does less\nstuff and waits less time to do it.\n\n### Immediately emit `end` for empty streams (when not paused)\n\nIf a stream is not paused, and `end()` is called before writing\nany data into it, then it will emit `end` immediately.\n\nIf you have logic that occurs on the `end` event which you don't\nwant to potentially happen immediately (for example, closing file\ndescriptors, moving on to the next entry in an archive parse\nstream, etc.) then be sure to call `stream.pause()` on creation,\nand then `stream.resume()` once you are ready to respond to the\n`end` event.\n\nHowever, this is _usually_ not a problem because:\n\n### Emit `end` When Asked\n\nOne hazard of immediately emitting `'end'` is that you may not\nyet have had a chance to add a listener. In order to avoid this\nhazard, Minipass streams safely re-emit the `'end'` event if a\nnew listener is added after `'end'` has been emitted.\n\nIe, if you do `stream.on('end', someFunction)`, and the stream\nhas already emitted `end`, then it will call the handler right\naway. (You can think of this somewhat like attaching a new\n`.then(fn)` to a previously-resolved Promise.)\n\nTo prevent calling handlers multiple times who would not expect\nmultiple ends to occur, all listeners are removed from the\n`'end'` event whenever it is emitted.\n\n### Emit `error` When Asked\n\nThe most recent error object passed to the `'error'` event is\nstored on the stream. If a new `'error'` event handler is added,\nand an error was previously emitted, then the event handler will\nbe called immediately (or on `process.nextTick` in the case of\nasync streams).\n\nThis makes it much more difficult to end up trying to interact\nwith a broken stream, if the error handler is added after an\nerror was previously emitted.\n\n### Impact of \"immediate flow\" on Tee-streams\n\nA \"tee stream\" is a stream piping to multiple destinations:\n\n```js\nconst tee = new Minipass()\nt.pipe(dest1)\nt.pipe(dest2)\nt.write('foo') // goes to both destinations\n```\n\nSince Minipass streams _immediately_ process any pending data\nthrough the pipeline when a new pipe destination is added, this\ncan have surprising effects, especially when a stream comes in\nfrom some other function and may or may not have data in its\nbuffer.\n\n```js\n// WARNING! WILL LOSE DATA!\nconst src = new Minipass()\nsrc.write('foo')\nsrc.pipe(dest1) // 'foo' chunk flows to dest1 immediately, and is gone\nsrc.pipe(dest2) // gets nothing!\n```\n\nOne solution is to create a dedicated tee-stream junction that\npipes to both locations, and then pipe to _that_ instead.\n\n```js\n// Safe example: tee to both places\nconst src = new Minipass()\nsrc.write('foo')\nconst tee = new Minipass()\ntee.pipe(dest1)\ntee.pipe(dest2)\nsrc.pipe(tee) // tee gets 'foo', pipes to both locations\n```\n\nThe same caveat applies to `on('data')` event listeners. The\nfirst one added will _immediately_ receive all of the data,\nleaving nothing for the second:\n\n```js\n// WARNING! WILL LOSE DATA!\nconst src = new Minipass()\nsrc.write('foo')\nsrc.on('data', handler1) // receives 'foo' right away\nsrc.on('data', handler2) // nothing to see here!\n```\n\nUsing a dedicated tee-stream can be used in this case as well:\n\n```js\n// Safe example: tee to both data handlers\nconst src = new Minipass()\nsrc.write('foo')\nconst tee = new Minipass()\ntee.on('data', handler1)\ntee.on('data', handler2)\nsrc.pipe(tee)\n```\n\nAll of the hazards in this section are avoided by setting `{\nasync: true }` in the Minipass constructor, or by setting\n`stream.async = true` afterwards. Note that this does add some\noverhead, so should only be done in cases where you are willing\nto lose a bit of performance in order to avoid having to refactor\nprogram logic.\n\n## USAGE\n\nIt's a stream! Use it like a stream and it'll most likely do what\nyou want.\n\n```js\nimport { Minipass } from 'minipass'\nconst mp = new Minipass(options) // options is optional\nmp.write('foo')\nmp.pipe(someOtherStream)\nmp.end('bar')\n```\n\n### OPTIONS\n\n- `encoding` How would you like the data coming _out_ of the\n  stream to be encoded? Accepts any values that can be passed to\n  `Buffer.toString()`.\n- `objectMode` Emit data exactly as it comes in. This will be\n  flipped on by default if you write() something other than a\n  string or Buffer at any point. Setting `objectMode: true` will\n  prevent setting any encoding value.\n- `async` Defaults to `false`. Set to `true` to defer data\n  emission until next tick. This reduces performance slightly,\n  but makes Minipass streams use timing behavior closer to Node\n  core streams. See [Timing](#timing) for more details.\n- `signal` An `AbortSignal` that will cause the stream to unhook\n  itself from everything and become as inert as possible. Note\n  that providing a `signal` parameter will make `'error'` events\n  no longer throw if they are unhandled, but they will still be\n  emitted to handlers if any are attached.\n\n### API\n\nImplements the user-facing portions of Node.js's `Readable` and\n`Writable` streams.\n\n### Methods\n\n- `write(chunk, [encoding], [callback])` - Put data in. (Note\n  that, in the base Minipass class, the same data will come out.)\n  Returns `false` if the stream will buffer the next write, or\n  true if it's still in \"flowing\" mode.\n- `end([chunk, [encoding]], [callback])` - Signal that you have\n  no more data to write. This will queue an `end` event to be\n  fired when all the data has been consumed.\n- `pause()` - No more data for a while, please. This also\n  prevents `end` from being emitted for empty streams until the\n  stream is resumed.\n- `resume()` - Resume the stream. If there's data in the buffer,\n  it is all discarded. Any buffered events are immediately\n  emitted.\n- `pipe(dest)` - Send all output to the stream provided. When\n  data is emitted, it is immediately written to any and all pipe\n  destinations. (Or written on next tick in `async` mode.)\n- `unpipe(dest)` - Stop piping to the destination stream. This is\n  immediate, meaning that any asynchronously queued data will\n  _not_ make it to the destination when running in `async` mode.\n  - `options.end` - Boolean, end the destination stream when the\n    source stream ends. Default `true`.\n  - `options.proxyErrors` - Boolean, proxy `error` events from\n    the source stream to the destination stream. Note that errors\n    are _not_ proxied after the pipeline terminates, either due\n    to the source emitting `'end'` or manually unpiping with\n    `src.unpipe(dest)`. Default `false`.\n- `on(ev, fn)`, `emit(ev, fn)` - Minipass streams are\n  EventEmitters. Some events are given special treatment,\n  however. (See below under \"events\".)\n- `promise()` - Returns a Promise that resolves when the stream\n  emits `end`, or rejects if the stream emits `error`.\n- `collect()` - Return a Promise that resolves on `end` with an\n  array containing each chunk of data that was emitted, or\n  rejects if the stream emits `error`. Note that this consumes\n  the stream data.\n- `concat()` - Same as `collect()`, but concatenates the data\n  into a single Buffer object. Will reject the returned promise\n  if the stream is in objectMode, or if it goes into objectMode\n  by the end of the data.\n- `read(n)` - Consume `n` bytes of data out of the buffer. If `n`\n  is not provided, then consume all of it. If `n` bytes are not\n  available, then it returns null. **Note** consuming streams in\n  this way is less efficient, and can lead to unnecessary Buffer\n  copying.\n- `destroy([er])` - Destroy the stream. If an error is provided,\n  then an `'error'` event is emitted. If the stream has a\n  `close()` method, and has not emitted a `'close'` event yet,\n  then `stream.close()` will be called. Any Promises returned by\n  `.promise()`, `.collect()` or `.concat()` will be rejected.\n  After being destroyed, writing to the stream will emit an\n  error. No more data will be emitted if the stream is destroyed,\n  even if it was previously buffered.\n\n### Properties\n\n- `bufferLength` Read-only. Total number of bytes buffered, or in\n  the case of objectMode, the total number of objects.\n- `encoding` Read-only. The encoding that has been set.\n- `flowing` Read-only. Boolean indicating whether a chunk written\n  to the stream will be immediately emitted.\n- `emittedEnd` Read-only. Boolean indicating whether the end-ish\n  events (ie, `end`, `prefinish`, `finish`) have been emitted.\n  Note that listening on any end-ish event will immediateyl\n  re-emit it if it has already been emitted.\n- `writable` Whether the stream is writable. Default `true`. Set\n  to `false` when `end()`\n- `readable` Whether the stream is readable. Default `true`.\n- `pipes` An array of Pipe objects referencing streams that this\n  stream is piping into.\n- `destroyed` A getter that indicates whether the stream was\n  destroyed.\n- `paused` True if the stream has been explicitly paused,\n  otherwise false.\n- `objectMode` Indicates whether the stream is in `objectMode`.\n- `aborted` Readonly property set when the `AbortSignal`\n  dispatches an `abort` event.\n\n### Events\n\n- `data` Emitted when there's data to read. Argument is the data\n  to read. This is never emitted while not flowing. If a listener\n  is attached, that will resume the stream.\n- `end` Emitted when there's no more data to read. This will be\n  emitted immediately for empty streams when `end()` is called.\n  If a listener is attached, and `end` was already emitted, then\n  it will be emitted again. All listeners are removed when `end`\n  is emitted.\n- `prefinish` An end-ish event that follows the same logic as\n  `end` and is emitted in the same conditions where `end` is\n  emitted. Emitted after `'end'`.\n- `finish` An end-ish event that follows the same logic as `end`\n  and is emitted in the same conditions where `end` is emitted.\n  Emitted after `'prefinish'`.\n- `close` An indication that an underlying resource has been\n  released. Minipass does not emit this event, but will defer it\n  until after `end` has been emitted, since it throws off some\n  stream libraries otherwise.\n- `drain` Emitted when the internal buffer empties, and it is\n  again suitable to `write()` into the stream.\n- `readable` Emitted when data is buffered and ready to be read\n  by a consumer.\n- `resume` Emitted when stream changes state from buffering to\n  flowing mode. (Ie, when `resume` is called, `pipe` is called,\n  or a `data` event listener is added.)\n\n### Static Methods\n\n- `Minipass.isStream(stream)` Returns `true` if the argument is a\n  stream, and false otherwise. To be considered a stream, the\n  object must be either an instance of Minipass, or an\n  EventEmitter that has either a `pipe()` method, or both\n  `write()` and `end()` methods. (Pretty much any stream in\n  node-land will return `true` for this.)\n\n## EXAMPLES\n\nHere are some examples of things you can do with Minipass\nstreams.\n\n### simple \"are you done yet\" promise\n\n```js\nmp.promise().then(\n  () => {\n    // stream is finished\n  },\n  er => {\n    // stream emitted an error\n  }\n)\n```\n\n### collecting\n\n```js\nmp.collect().then(all => {\n  // all is an array of all the data emitted\n  // encoding is supported in this case, so\n  // so the result will be a collection of strings if\n  // an encoding is specified, or buffers/objects if not.\n  //\n  // In an async function, you may do\n  // const data = await stream.collect()\n})\n```\n\n### collecting into a single blob\n\nThis is a bit slower because it concatenates the data into one\nchunk for you, but if you're going to do it yourself anyway, it's\nconvenient this way:\n\n```js\nmp.concat().then(onebigchunk => {\n  // onebigchunk is a string if the stream\n  // had an encoding set, or a buffer otherwise.\n})\n```\n\n### iteration\n\nYou can iterate over streams synchronously or asynchronously in\nplatforms that support it.\n\nSynchronous iteration will end when the currently available data\nis consumed, even if the `end` event has not been reached. In\nstring and buffer mode, the data is concatenated, so unless\nmultiple writes are occurring in the same tick as the `read()`,\nsync iteration loops will generally only have a single iteration.\n\nTo consume chunks in this way exactly as they have been written,\nwith no flattening, create the stream with the `{ objectMode:\ntrue }` option.\n\n```js\nconst mp = new Minipass({ objectMode: true })\nmp.write('a')\nmp.write('b')\nfor (let letter of mp) {\n  console.log(letter) // a, b\n}\nmp.write('c')\nmp.write('d')\nfor (let letter of mp) {\n  console.log(letter) // c, d\n}\nmp.write('e')\nmp.end()\nfor (let letter of mp) {\n  console.log(letter) // e\n}\nfor (let letter of mp) {\n  console.log(letter) // nothing\n}\n```\n\nAsynchronous iteration will continue until the end event is reached,\nconsuming all of the data.\n\n```js\nconst mp = new Minipass({ encoding: 'utf8' })\n\n// some source of some data\nlet i = 5\nconst inter = setInterval(() => {\n  if (i-- > 0) mp.write(Buffer.from('foo\\n', 'utf8'))\n  else {\n    mp.end()\n    clearInterval(inter)\n  }\n}, 100)\n\n// consume the data with asynchronous iteration\nasync function consume() {\n  for await (let chunk of mp) {\n    console.log(chunk)\n  }\n  return 'ok'\n}\n\nconsume().then(res => console.log(res))\n// logs `foo\\n` 5 times, and then `ok`\n```\n\n### subclass that `console.log()`s everything written into it\n\n```js\nclass Logger extends Minipass {\n  write(chunk, encoding, callback) {\n    console.log('WRITE', chunk, encoding)\n    return super.write(chunk, encoding, callback)\n  }\n  end(chunk, encoding, callback) {\n    console.log('END', chunk, encoding)\n    return super.end(chunk, encoding, callback)\n  }\n}\n\nsomeSource.pipe(new Logger()).pipe(someDest)\n```\n\n### same thing, but using an inline anonymous class\n\n```js\n// js classes are fun\nsomeSource\n  .pipe(\n    new (class extends Minipass {\n      emit(ev, ...data) {\n        // let's also log events, because debugging some weird thing\n        console.log('EMIT', ev)\n        return super.emit(ev, ...data)\n      }\n      write(chunk, encoding, callback) {\n        console.log('WRITE', chunk, encoding)\n        return super.write(chunk, encoding, callback)\n      }\n      end(chunk, encoding, callback) {\n        console.log('END', chunk, encoding)\n        return super.end(chunk, encoding, callback)\n      }\n    })()\n  )\n  .pipe(someDest)\n```\n\n### subclass that defers 'end' for some reason\n\n```js\nclass SlowEnd extends Minipass {\n  emit(ev, ...args) {\n    if (ev === 'end') {\n      console.log('going to end, hold on a sec')\n      setTimeout(() => {\n        console.log('ok, ready to end now')\n        super.emit('end', ...args)\n      }, 100)\n      return true\n    } else {\n      return super.emit(ev, ...args)\n    }\n  }\n}\n```\n\n### transform that creates newline-delimited JSON\n\n```js\nclass NDJSONEncode extends Minipass {\n  write(obj, cb) {\n    try {\n      // JSON.stringify can throw, emit an error on that\n      return super.write(JSON.stringify(obj) + '\\n', 'utf8', cb)\n    } catch (er) {\n      this.emit('error', er)\n    }\n  }\n  end(obj, cb) {\n    if (typeof obj === 'function') {\n      cb = obj\n      obj = undefined\n    }\n    if (obj !== undefined) {\n      this.write(obj)\n    }\n    return super.end(cb)\n  }\n}\n```\n\n### transform that parses newline-delimited JSON\n\n```js\nclass NDJSONDecode extends Minipass {\n  constructor(options) {\n    // always be in object mode, as far as Minipass is concerned\n    super({ objectMode: true })\n    this._jsonBuffer = ''\n  }\n  write(chunk, encoding, cb) {\n    if (\n      typeof chunk === 'string' &&\n      typeof encoding === 'string' &&\n      encoding !== 'utf8'\n    ) {\n      chunk = Buffer.from(chunk, encoding).toString()\n    } else if (Buffer.isBuffer(chunk)) {\n      chunk = chunk.toString()\n    }\n    if (typeof encoding === 'function') {\n      cb = encoding\n    }\n    const jsonData = (this._jsonBuffer + chunk).split('\\n')\n    this._jsonBuffer = jsonData.pop()\n    for (let i = 0; i < jsonData.length; i++) {\n      try {\n        // JSON.parse can throw, emit an error on that\n        super.write(JSON.parse(jsonData[i]))\n      } catch (er) {\n        this.emit('error', er)\n        continue\n      }\n    }\n    if (cb) cb()\n  }\n}\n```",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{42/3e/3f7f4c825731391d9afca11c1cc728e83ef48566b99913b8f56e24f96c6d4cd285a311bb5eaf062257b1404f24a661f26741a3c1b910c15210a5dd629fec → c3/36/3e247533c8693b2fc2f0884060f91f911407242f273de09f2bafc373a5e7d9848d5678a1754ffe21ef84fa911f8c1779f5739742d657543395d9be93034f}

@@ -4012,7 +4012,7 @@
   "dist-tags": {
     "latest": "3.7.2"
   },
-  "_rev": "43-9008e9791924da1f",
+  "_rev": "44-aa40726410d3f02f",
   "_id": "@smithy/types",
   "readme": "# @smithy/types\n\n[![NPM version](https://img.shields.io/npm/v/@smithy/types/latest.svg)](https://www.npmjs.com/package/@smithy/types)\n[![NPM downloads](https://img.shields.io/npm/dm/@smithy/types.svg)](https://www.npmjs.com/package/@smithy/types)\n\n## Usage\n\nThis package is mostly used internally by generated clients.\nSome public components have independent applications.\n\n---\n\n### Scenario: Removing `| undefined` from input and output structures\n\nGenerated shapes' members are unioned with `undefined` for\ninput shapes, and are `?` (optional) for output shapes.\n\n- for inputs, this defers the validation to the service.\n- for outputs, this strongly suggests that you should runtime-check the output data.\n\nIf you would like to skip these steps, use the `AssertiveClient` or\n`UncheckedClient` type helpers.\n\nUsing AWS S3 as an example:\n\n```ts\nimport { S3 } from \"@aws-sdk/client-s3\";\nimport type { AssertiveClient, UncheckedClient } from \"@smithy/types\";\n\nconst s3a = new S3({}) as AssertiveClient<S3>;\nconst s3b = new S3({}) as UncheckedClient<S3>;\n\n// AssertiveClient enforces required inputs are not undefined\n// and required outputs are not undefined.\nconst get = await s3a.getObject({\n  Bucket: \"\",\n  // @ts-expect-error (undefined not assignable to string)\n  Key: undefined,\n});\n\n// UncheckedClient makes output fields non-nullable.\n// You should still perform type checks as you deem\n// necessary, but the SDK will no longer prompt you\n// with nullability errors.\nconst body = await (\n  await s3b.getObject({\n    Bucket: \"\",\n    Key: \"\",\n  })\n).Body.transformToString();\n```\n\nWhen using the transform on non-aggregated client with the `Command` syntax,\nthe input cannot be validated because it goes through another class.\n\n```ts\nimport { S3Client, ListBucketsCommand, GetObjectCommand, GetObjectCommandInput } from \"@aws-sdk/client-s3\";\nimport type { AssertiveClient, UncheckedClient, NoUndefined } from \"@smithy/types\";\n\nconst s3 = new S3Client({}) as UncheckedClient<S3Client>;\n\nconst list = await s3.send(\n  new ListBucketsCommand({\n    // command inputs are not validated by the type transform.\n    // because this is a separate class.\n  })\n);\n\n/**\n * Although less ergonomic, you can use the NoUndefined<T>\n * transform on the input type.\n */\nconst getObjectInput: NoUndefined<GetObjectCommandInput> = {\n  Bucket: \"undefined\",\n  // @ts-expect-error (undefined not assignable to string)\n  Key: undefined,\n  // optional params can still be undefined.\n  SSECustomerAlgorithm: undefined,\n};\n\nconst get = s3.send(new GetObjectCommand(getObjectInput));\n\n// outputs are still transformed.\nawait get.Body.TransformToString();\n```\n\n### Scenario: Narrowing a smithy-typescript generated client's output payload blob types\n\nThis is mostly relevant to operations with streaming bodies such as within\nthe S3Client in the AWS SDK for JavaScript v3.\n\nBecause blob payload types are platform dependent, you may wish to indicate in your application that a client is running in a specific\nenvironment. This narrows the blob payload types.\n\n```typescript\nimport { GetObjectCommand, S3Client } from \"@aws-sdk/client-s3\";\nimport type { NodeJsClient, SdkStream, StreamingBlobPayloadOutputTypes } from \"@smithy/types\";\nimport type { IncomingMessage } from \"node:http\";\n\n// default client init.\nconst s3Default = new S3Client({});\n\n// client init with type narrowing.\nconst s3NarrowType = new S3Client({}) as NodeJsClient<S3Client>;\n\n// The default type of blob payloads is a wide union type including multiple possible\n// request handlers.\nconst body1: StreamingBlobPayloadOutputTypes = (await s3Default.send(new GetObjectCommand({ Key: \"\", Bucket: \"\" })))\n  .Body!;\n\n// This is of the narrower type SdkStream<IncomingMessage> representing\n// blob payload responses using specifically the node:http request handler.\nconst body2: SdkStream<IncomingMessage> = (await s3NarrowType.send(new GetObjectCommand({ Key: \"\", Bucket: \"\" })))\n  .Body!;\n```",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{7c/c7/cc49e93959fb22dc9da402e3f9a8064c389a8aa254205acf3549136bf326c2d8371f25478c312fa857324f1917e6181c5f2ac200d34aaf0c096405dbc2cd → c3/b9/841151838790a23f72d9fa8540f5f69f4e0db527447c92c7091a09741225b1b83fe263e7d1e60ed6c45445927abdcc82887cf725450cdc90273d4cb2d291}

@@ -11391,7 +11391,7 @@
     "gamma": "1.0.0-gamma.8",
     "rc": "1.0.0-rc.10"
   },
-  "_rev": "63-da600d9a1c47cecd",
+  "_rev": "64-051a0d0790225590",
   "_id": "@aws-sdk/middleware-serde",
   "readme": "# @aws-sdk/middleware-serde\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/middleware-serde/latest.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-serde)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/middleware-serde.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-serde)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{cb/f3/764839a66d2be417471c24119536b01ecdb4d6d2840e95e835d6bde56d424d5908dbccc377a27efc053cf8a3b99d9e4df4e157c13870068a6fe0d7d6aa22 → c5/43/5ea8414f20503e63e5ef831619b34b424863f2bf20c6f1980fe638e109c37cae2dfd64ce5a767eeb7cf08c997d00389c7d847faba392962edb886da29ec4}

@@ -816,7 +816,7 @@
   "dist-tags": {
     "latest": "3.374.0"
   },
-  "_rev": "58-d9d8bbfaeaf88868",
+  "_rev": "59-d34ee9fe10f2acd5",
   "_id": "@aws-sdk/util-utf8",
   "readme": "# @aws-sdk/util-utf8\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/util-utf8/latest.svg)](https://www.npmjs.com/package/@aws-sdk/util-utf8)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/util-utf8.svg)](https://www.npmjs.com/package/@aws-sdk/util-utf8)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{da/98/82cce1f4b31b35fffbaf1a9c98068709f18ad99aedcd8e5e3051df8eab2f0fb162b50d7b4a9a491ad1aedf7b772f6115213b2643c8183c22d67226875094 → c5/bc/fb2026d12b2258222f7358ddb9ada54cccda09c9599a1d2830c3231db9ef7668140d118d8403b1c8f022390420740362fea73cfa706b0db02304009cc71f}

@@ -5304,7 +5304,7 @@
   "dist-tags": {
     "latest": "14.1.0"
   },
-  "_rev": "1138-cc9a8531035bffd6",
+  "_rev": "1139-04df44fb587439fa",
   "_id": "whatwg-url",
   "readme": "# whatwg-url\n\nwhatwg-url is a full implementation of the WHATWG [URL Standard](https://url.spec.whatwg.org/). It can be used standalone, but it also exposes a lot of the internal algorithms that are useful for integrating a URL parser into a project like [jsdom](https://github.com/jsdom/jsdom).\n\n## Specification conformance\n\nwhatwg-url is currently up to date with the URL spec up to commit [da212c9](https://github.com/whatwg/url/commit/da212c98f0bba9c35aec3728bbcc13f8f3a7eb52).\n\nFor `file:` URLs, whose [origin is left unspecified](https://url.spec.whatwg.org/#concept-url-origin), whatwg-url chooses to use a new opaque origin (which serializes to `\"null\"`).\n\nwhatwg-url does not yet implement any encoding handling beyond UTF-8. That is, the _encoding override_ parameter does not exist in our API.\n\n## API\n\n### The `URL` and `URLSearchParams` classes\n\nThe main API is provided by the [`URL`](https://url.spec.whatwg.org/#url-class) and [`URLSearchParams`](https://url.spec.whatwg.org/#interface-urlsearchparams) exports, which follows the spec's behavior in all ways (including e.g. `USVString` conversion). Most consumers of this library will want to use these.\n\n### Low-level URL Standard API\n\nThe following methods are exported for use by places like jsdom that need to implement things like [`HTMLHyperlinkElementUtils`](https://html.spec.whatwg.org/#htmlhyperlinkelementutils). They mostly operate on or return an \"internal URL\" or [\"URL record\"](https://url.spec.whatwg.org/#concept-url) type.\n\n- [URL parser](https://url.spec.whatwg.org/#concept-url-parser): `parseURL(input, { baseURL })`\n- [Basic URL parser](https://url.spec.whatwg.org/#concept-basic-url-parser): `basicURLParse(input, { baseURL, url, stateOverride })`\n- [URL serializer](https://url.spec.whatwg.org/#concept-url-serializer): `serializeURL(urlRecord, excludeFragment)`\n- [Host serializer](https://url.spec.whatwg.org/#concept-host-serializer): `serializeHost(hostFromURLRecord)`\n- [URL path serializer](https://url.spec.whatwg.org/#url-path-serializer): `serializePath(urlRecord)`\n- [Serialize an integer](https://url.spec.whatwg.org/#serialize-an-integer): `serializeInteger(number)`\n- [Origin](https://url.spec.whatwg.org/#concept-url-origin) [serializer](https://html.spec.whatwg.org/multipage/origin.html#ascii-serialisation-of-an-origin): `serializeURLOrigin(urlRecord)`\n- [Set the username](https://url.spec.whatwg.org/#set-the-username): `setTheUsername(urlRecord, usernameString)`\n- [Set the password](https://url.spec.whatwg.org/#set-the-password): `setThePassword(urlRecord, passwordString)`\n- [Has an opaque path](https://url.spec.whatwg.org/#url-opaque-path): `hasAnOpaquePath(urlRecord)`\n- [Cannot have a username/password/port](https://url.spec.whatwg.org/#cannot-have-a-username-password-port): `cannotHaveAUsernamePasswordPort(urlRecord)`\n- [Percent decode bytes](https://url.spec.whatwg.org/#percent-decode): `percentDecodeBytes(uint8Array)`\n- [Percent decode a string](https://url.spec.whatwg.org/#string-percent-decode): `percentDecodeString(string)`\n\nThe `stateOverride` parameter is one of the following strings:\n\n- [`\"scheme start\"`](https://url.spec.whatwg.org/#scheme-start-state)\n- [`\"scheme\"`](https://url.spec.whatwg.org/#scheme-state)\n- [`\"no scheme\"`](https://url.spec.whatwg.org/#no-scheme-state)\n- [`\"special relative or authority\"`](https://url.spec.whatwg.org/#special-relative-or-authority-state)\n- [`\"path or authority\"`](https://url.spec.whatwg.org/#path-or-authority-state)\n- [`\"relative\"`](https://url.spec.whatwg.org/#relative-state)\n- [`\"relative slash\"`](https://url.spec.whatwg.org/#relative-slash-state)\n- [`\"special authority slashes\"`](https://url.spec.whatwg.org/#special-authority-slashes-state)\n- [`\"special authority ignore slashes\"`](https://url.spec.whatwg.org/#special-authority-ignore-slashes-state)\n- [`\"authority\"`](https://url.spec.whatwg.org/#authority-state)\n- [`\"host\"`](https://url.spec.whatwg.org/#host-state)\n- [`\"hostname\"`](https://url.spec.whatwg.org/#hostname-state)\n- [`\"port\"`](https://url.spec.whatwg.org/#port-state)\n- [`\"file\"`](https://url.spec.whatwg.org/#file-state)\n- [`\"file slash\"`](https://url.spec.whatwg.org/#file-slash-state)\n- [`\"file host\"`](https://url.spec.whatwg.org/#file-host-state)\n- [`\"path start\"`](https://url.spec.whatwg.org/#path-start-state)\n- [`\"path\"`](https://url.spec.whatwg.org/#path-state)\n- [`\"opaque path\"`](https://url.spec.whatwg.org/#cannot-be-a-base-url-path-state)\n- [`\"query\"`](https://url.spec.whatwg.org/#query-state)\n- [`\"fragment\"`](https://url.spec.whatwg.org/#fragment-state)\n\nThe URL record type has the following API:\n\n- [`scheme`](https://url.spec.whatwg.org/#concept-url-scheme)\n- [`username`](https://url.spec.whatwg.org/#concept-url-username)\n- [`password`](https://url.spec.whatwg.org/#concept-url-password)\n- [`host`](https://url.spec.whatwg.org/#concept-url-host)\n- [`port`](https://url.spec.whatwg.org/#concept-url-port)\n- [`path`](https://url.spec.whatwg.org/#concept-url-path) (as an array of strings, or a string)\n- [`query`](https://url.spec.whatwg.org/#concept-url-query)\n- [`fragment`](https://url.spec.whatwg.org/#concept-url-fragment)\n\nThese properties should be treated with care, as in general changing them will cause the URL record to be in an inconsistent state until the appropriate invocation of `basicURLParse` is used to fix it up. You can see examples of this in the URL Standard, where there are many step sequences like \"4. Set context object’s url’s fragment to the empty string. 5. Basic URL parse _input_ with context object’s url as _url_ and fragment state as _state override_.\" In between those two steps, a URL record is in an unusable state.\n\nThe return value of \"failure\" in the spec is represented by `null`. That is, functions like `parseURL` and `basicURLParse` can return _either_ a URL record _or_ `null`.\n\n### `whatwg-url/webidl2js-wrapper` module\n\nThis module exports the `URL` and `URLSearchParams` [interface wrappers API](https://github.com/jsdom/webidl2js#for-interfaces) generated by [webidl2js](https://github.com/jsdom/webidl2js).\n\n## Development instructions\n\nFirst, install [Node.js](https://nodejs.org/). Then, fetch the dependencies of whatwg-url, by running from this directory:\n\n    npm install\n\nTo run tests:\n\n    npm test\n\nTo generate a coverage report:\n\n    npm run coverage\n\nTo build and run the live viewer:\n\n    npm run prepare\n    npm run build-live-viewer\n\nServe the contents of the `live-viewer` directory using any web server.\n\n## Supporting whatwg-url\n\nThe jsdom project (including whatwg-url) is a community-driven project maintained by a team of [volunteers](https://github.com/orgs/jsdom/people). You could support us by:\n\n- [Getting professional support for whatwg-url](https://tidelift.com/subscription/pkg/npm-whatwg-url?utm_source=npm-whatwg-url&utm_medium=referral&utm_campaign=readme) as part of a Tidelift subscription. Tidelift helps making open source sustainable for us while giving teams assurances for maintenance, licensing, and security.\n- Contributing directly to the project.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{2b/27/096a2dd3ab5f99898429194fea6035d9c892f780a26717081d47eeee735d91d229c3d7ed6f9982c806a9fddbee81c4fd7b0fd783b59e77c1f69a494d4e06 → c7/1f/a7130aa7f3dbc1d27f8d4855c5d35a9e3d2466beab1413e6fd57bbec476168338d2d70aa39a88a937bbed5cde73d56670703f184975961b7548f26ae978d}

@@ -2325,7 +2325,7 @@
   "dist-tags": {
     "latest": "6.2.1"
   },
-  "_rev": "2339-f93a9e340b73b7e6",
+  "_rev": "2344-b3e7b7ca513ca0ab",
   "_id": "ansi-styles",
   "readme": "# ansi-styles\n\n> [ANSI escape codes](https://en.wikipedia.org/wiki/ANSI_escape_code#Colors_and_Styles) for styling strings in the terminal\n\nYou probably want the higher-level [chalk](https://github.com/chalk/chalk) module for styling your strings.\n\n![](screenshot.png)\n\n## Install\n\n```sh\nnpm install ansi-styles\n```\n\n## Usage\n\n```js\nimport styles from 'ansi-styles';\n\nconsole.log(`${styles.green.open}Hello world!${styles.green.close}`);\n\n\n// Color conversion between 256/truecolor\n// NOTE: When converting from truecolor to 256 colors, the original color\n//       may be degraded to fit the new color palette. This means terminals\n//       that do not support 16 million colors will best-match the\n//       original color.\nconsole.log(`${styles.color.ansi(styles.rgbToAnsi(199, 20, 250))}Hello World${styles.color.close}`)\nconsole.log(`${styles.color.ansi256(styles.rgbToAnsi256(199, 20, 250))}Hello World${styles.color.close}`)\nconsole.log(`${styles.color.ansi16m(...styles.hexToRgb('#abcdef'))}Hello World${styles.color.close}`)\n```\n\n## API\n\n### `open` and `close`\n\nEach style has an `open` and `close` property.\n\n### `modifierNames`, `foregroundColorNames`, `backgroundColorNames`, and `colorNames`\n\nAll supported style strings are exposed as an array of strings for convenience. `colorNames` is the combination of `foregroundColorNames` and `backgroundColorNames`.\n\nThis can be useful if you need to validate input:\n\n```js\nimport {modifierNames, foregroundColorNames} from 'ansi-styles';\n\nconsole.log(modifierNames.includes('bold'));\n//=> true\n\nconsole.log(foregroundColorNames.includes('pink'));\n//=> false\n```\n\n## Styles\n\n### Modifiers\n\n- `reset`\n- `bold`\n- `dim`\n- `italic` *(Not widely supported)*\n- `underline`\n- `overline` *Supported on VTE-based terminals, the GNOME terminal, mintty, and Git Bash.*\n- `inverse`\n- `hidden`\n- `strikethrough` *(Not widely supported)*\n\n### Colors\n\n- `black`\n- `red`\n- `green`\n- `yellow`\n- `blue`\n- `magenta`\n- `cyan`\n- `white`\n- `blackBright` (alias: `gray`, `grey`)\n- `redBright`\n- `greenBright`\n- `yellowBright`\n- `blueBright`\n- `magentaBright`\n- `cyanBright`\n- `whiteBright`\n\n### Background colors\n\n- `bgBlack`\n- `bgRed`\n- `bgGreen`\n- `bgYellow`\n- `bgBlue`\n- `bgMagenta`\n- `bgCyan`\n- `bgWhite`\n- `bgBlackBright` (alias: `bgGray`, `bgGrey`)\n- `bgRedBright`\n- `bgGreenBright`\n- `bgYellowBright`\n- `bgBlueBright`\n- `bgMagentaBright`\n- `bgCyanBright`\n- `bgWhiteBright`\n\n## Advanced usage\n\nBy default, you get a map of styles, but the styles are also available as groups. They are non-enumerable so they don't show up unless you access them explicitly. This makes it easier to expose only a subset in a higher-level module.\n\n- `styles.modifier`\n- `styles.color`\n- `styles.bgColor`\n\n###### Example\n\n```js\nimport styles from 'ansi-styles';\n\nconsole.log(styles.color.green.open);\n```\n\nRaw escape codes (i.e. without the CSI escape prefix `\\u001B[` and render mode postfix `m`) are available under `styles.codes`, which returns a `Map` with the open codes as keys and close codes as values.\n\n###### Example\n\n```js\nimport styles from 'ansi-styles';\n\nconsole.log(styles.codes.get(36));\n//=> 39\n```\n\n## 16 / 256 / 16 million (TrueColor) support\n\n`ansi-styles` allows converting between various color formats and ANSI escapes, with support for 16, 256 and [16 million colors](https://gist.github.com/XVilka/8346728).\n\nThe following color spaces are supported:\n\n- `rgb`\n- `hex`\n- `ansi256`\n- `ansi`\n\nTo use these, call the associated conversion function with the intended output, for example:\n\n```js\nimport styles from 'ansi-styles';\n\nstyles.color.ansi(styles.rgbToAnsi(100, 200, 15)); // RGB to 16 color ansi foreground code\nstyles.bgColor.ansi(styles.hexToAnsi('#C0FFEE')); // HEX to 16 color ansi foreground code\n\nstyles.color.ansi256(styles.rgbToAnsi256(100, 200, 15)); // RGB to 256 color ansi foreground code\nstyles.bgColor.ansi256(styles.hexToAnsi256('#C0FFEE')); // HEX to 256 color ansi foreground code\n\nstyles.color.ansi16m(100, 200, 15); // RGB to 16 million color foreground code\nstyles.bgColor.ansi16m(...styles.hexToRgb('#C0FFEE')); // Hex (RGB) to 16 million color foreground code\n```\n\n## Related\n\n- [ansi-escapes](https://github.com/sindresorhus/ansi-escapes) - ANSI escape codes for manipulating the terminal\n\n## Maintainers\n\n- [Sindre Sorhus](https://github.com/sindresorhus)\n- [Josh Junon](https://github.com/qix-)\n\n## For enterprise\n\nAvailable as part of the Tidelift Subscription.\n\nThe maintainers of `ansi-styles` and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. [Learn more.](https://tidelift.com/subscription/pkg/npm-ansi-styles?utm_source=npm-ansi-styles&utm_medium=referral&utm_campaign=enterprise&utm_term=repo)",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{2c/76/f6db9a5c25d9789930ce0f3a7be273feb970483473c9231e2674f940a184b23945375e33a732e8b4a93deb40d6fae883718a587268b3df4fdb2bf6342ab7 → c8/7a/1d91a3797b31dc0f336c61083621dd877b39953ebb361496904f74069fc18138e74b6c551736129b0e24005108d0af78fafb6bd84c1777d84b20c8722dfd}

@@ -37143,12 +37143,126 @@
       },
       "_hasShrinkwrap": false,
       "contributors": []
+    },
+    "3.716.0": {
+      "name": "@aws-sdk/credential-provider-sso",
+      "version": "3.716.0",
+      "description": "AWS credential provider that exchanges a resolved SSO login token file for temporary AWS credentials",
+      "main": "./dist-cjs/index.js",
+      "module": "./dist-es/index.js",
+      "scripts": {
+        "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
+        "build:cjs": "node ../../scripts/compilation/inline credential-provider-sso",
+        "build:es": "tsc -p tsconfig.es.json",
+        "build:include:deps": "lerna run --scope $npm_package_name --include-dependencies build",
+        "build:types": "tsc -p tsconfig.types.json",
+        "build:types:downlevel": "downlevel-dts dist-types dist-types/ts3.4",
+        "clean": "rimraf ./dist-* && rimraf *.tsbuildinfo",
+        "test": "yarn g:vitest run",
+        "test:watch": "yarn g:vitest watch"
+      },
+      "keywords": [
+        "aws",
+        "credentials"
+      ],
+      "author": {
+        "name": "AWS SDK for JavaScript Team",
+        "url": "https://aws.amazon.com/javascript/"
+      },
+      "license": "Apache-2.0",
+      "dependencies": {
+        "@aws-sdk/client-sso": "3.716.0",
+        "@aws-sdk/core": "3.716.0",
+        "@aws-sdk/token-providers": "3.714.0",
+        "@aws-sdk/types": "3.714.0",
+        "@smithy/property-provider": "^3.1.11",
+        "@smithy/shared-ini-file-loader": "^3.1.12",
+        "@smithy/types": "^3.7.2",
+        "tslib": "^2.6.2"
+      },
+      "devDependencies": {
+        "@tsconfig/recommended": "1.0.1",
+        "@types/node": "^16.18.96",
+        "concurrently": "7.0.0",
+        "downlevel-dts": "0.10.1",
+        "rimraf": "3.0.2",
+        "typescript": "~4.9.5"
+      },
+      "types": "./dist-types/index.d.ts",
+      "engines": {
+        "node": ">=16.0.0"
+      },
+      "typesVersions": {
+        "<4.0": {
+          "dist-types/*": [
+            "dist-types/ts3.4/*"
+          ]
+        }
+      },
+      "homepage": "https://github.com/aws/aws-sdk-js-v3/tree/main/packages/credential-provider-sso",
+      "repository": {
+        "type": "git",
+        "url": "git+https://github.com/aws/aws-sdk-js-v3.git",
+        "directory": "packages/credential-provider-sso"
+      },
+      "_id": "@aws-sdk/credential-provider-sso@3.716.0",
+      "bugs": {
+        "url": "https://github.com/aws/aws-sdk-js-v3/issues"
+      },
+      "_nodeVersion": "18.20.3",
+      "_npmVersion": "10.7.0",
+      "dist": {
+        "integrity": "sha512-J2IA3WuCpRGGoZm6VHZVFCnrxXP+41iUWb9Ct/1spljegTa1XjiaZ5Jf3+Ubj7WKiyvP9/dgz1L0bu2bYEjliw==",
+        "shasum": "908e5a7201c34f8bfed79893bb57f5876900ea3e",
+        "tarball": "https://verdaccio.mrsdev.ru/@aws-sdk%2fcredential-provider-sso/-/credential-provider-sso-3.716.0.tgz",
+        "fileCount": 25,
+        "unpackedSize": 36692,
+        "signatures": [
+          {
+            "keyid": "SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA",
+            "sig": "MEUCIQCHwV5/5T18+X1qpn/gk8BFZVo2tv1JCjrTlEGQ2IHmAAIgTipTAHZmlaJusdVlCq1c/iWqeEjVUSV07/BNscQ2s74="
+          }
+        ]
+      },
+      "_npmUser": {
+        "name": "aws-sdk-bot",
+        "email": "aws-sdk-js-automation@amazon.com"
+      },
+      "directories": {},
+      "maintainers": [
+        {
+          "name": "amzn-oss",
+          "email": "osa-3p@amazon.com"
+        },
+        {
+          "name": "aws-sdk-bot",
+          "email": "aws-sdk-js-automation@amazon.com"
+        },
+        {
+          "name": "trivikr-aws",
+          "email": "trivikr@amazon.com"
+        },
+        {
+          "name": "mattsb42-aws",
+          "email": "bullocm@amazon.com"
+        },
+        {
+          "name": "kuhe",
+          "email": "george.jing.fu+npm@gmail.com"
+        }
+      ],
+      "_npmOperationalInternal": {
+        "host": "s3://npm-registry-packages-npm-production",
+        "tmp": "tmp/credential-provider-sso_3.716.0_1734638344781_0.98911972184236"
+      },
+      "_hasShrinkwrap": false,
+      "contributors": []
     }
   },
   "time": {
     "created": "2021-02-26T00:31:47.318Z",
     "3.7.0": "2021-02-26T00:31:47.664Z",
-    "modified": "2024-12-17T19:55:34.105Z",
+    "modified": "2024-12-19T19:59:05.136Z",
     "3.8.0": "2021-03-05T23:27:04.889Z",
     "3.9.0": "2021-03-18T22:19:05.594Z",
     "3.10.0": "2021-03-27T00:23:03.943Z",
@@ -37474,13 +37588,14 @@
     "3.709.0": "2024-12-10T20:36:50.999Z",
     "3.712.0": "2024-12-13T20:14:00.042Z",
     "3.713.0": "2024-12-16T20:05:22.733Z",
-    "3.714.0": "2024-12-17T19:55:33.845Z"
+    "3.714.0": "2024-12-17T19:55:33.845Z",
+    "3.716.0": "2024-12-19T19:59:04.940Z"
   },
   "users": {},
   "dist-tags": {
-    "latest": "3.714.0"
+    "latest": "3.716.0"
   },
-  "_rev": "72-80a816036d212db3",
+  "_rev": "73-4256ea46aca4517d",
   "_id": "@aws-sdk/credential-provider-sso",
   "readme": "# @aws-sdk/credential-provider-sso\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/credential-provider-sso/latest.svg)](https://www.npmjs.com/package/@aws-sdk/credential-provider-sso)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/credential-provider-sso.svg)](https://www.npmjs.com/package/@aws-sdk/credential-provider-sso)\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/{4b/8d/367b0028cbd96998a0dee289034e8af4e15efa6dfaf0200336f06e348237ce1697b69c58aa373e54992f441a86d509806a6a7c816f39e5ee1d0e2d16b68f → ca/8d/a00e2dccbb7ee6e7ad226b51d95ca5d4c4817842c7c233a898c4eabf16b7a810eacdf18c7f072c4250f3f250d23e93b678ae4307d465bf0ea1c813e177ce}

@@ -20848,7 +20848,7 @@
     "gamma": "1.0.0-gamma.8",
     "rc": "1.0.0-rc.10"
   },
-  "_rev": "69-1f64608c6e61ca4d",
+  "_rev": "70-c09f14617d3a1a30",
   "_id": "@aws-sdk/middleware-signing",
   "readme": "# @aws-sdk/signer-middleware\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/middleware-signing/latest.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-signing)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/middleware-signing.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-signing)\n\nThis package is deprecated. It is only used in \"legacy auth\", and no longer used in the\nAWS SDK as of the Smithy Reference Architecture implementation of identity and auth.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{d6/fa/e6c80a733877d7c06b6445d15d6eb239a5ce2ea919a0289ac14422636f843524d9e83844dfcc3ba2bf9dc3496e7c2a40b821302a7b0f975355446202cb1f → cc/42/da3140ab786934222ff530c53a1c2b7cea1ea3c894342d5c3e39029d5b6bfbe9a0750feb98961f6b5345542e061e5dce09dc21aa223f57e0e54c9ffeb494}

@@ -54349,12 +54349,159 @@
       },
       "_hasShrinkwrap": false,
       "contributors": []
+    },
+    "3.716.0": {
+      "name": "@aws-sdk/client-sso",
+      "description": "AWS SDK for JavaScript Sso Client for Node.js, Browser and React Native",
+      "version": "3.716.0",
+      "scripts": {
+        "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
+        "build:cjs": "node ../../scripts/compilation/inline client-sso",
+        "build:es": "tsc -p tsconfig.es.json",
+        "build:include:deps": "lerna run --scope $npm_package_name --include-dependencies build",
+        "build:types": "tsc -p tsconfig.types.json",
+        "build:types:downlevel": "downlevel-dts dist-types dist-types/ts3.4",
+        "clean": "rimraf ./dist-* && rimraf *.tsbuildinfo",
+        "extract:docs": "api-extractor run --local",
+        "generate:client": "node ../../scripts/generate-clients/single-service --solo sso"
+      },
+      "main": "./dist-cjs/index.js",
+      "types": "./dist-types/index.d.ts",
+      "module": "./dist-es/index.js",
+      "sideEffects": false,
+      "dependencies": {
+        "@aws-crypto/sha256-browser": "5.2.0",
+        "@aws-crypto/sha256-js": "5.2.0",
+        "@aws-sdk/core": "3.716.0",
+        "@aws-sdk/middleware-host-header": "3.714.0",
+        "@aws-sdk/middleware-logger": "3.714.0",
+        "@aws-sdk/middleware-recursion-detection": "3.714.0",
+        "@aws-sdk/middleware-user-agent": "3.716.0",
+        "@aws-sdk/region-config-resolver": "3.714.0",
+        "@aws-sdk/types": "3.714.0",
+        "@aws-sdk/util-endpoints": "3.714.0",
+        "@aws-sdk/util-user-agent-browser": "3.714.0",
+        "@aws-sdk/util-user-agent-node": "3.716.0",
+        "@smithy/config-resolver": "^3.0.13",
+        "@smithy/core": "^2.5.5",
+        "@smithy/fetch-http-handler": "^4.1.2",
+        "@smithy/hash-node": "^3.0.11",
+        "@smithy/invalid-dependency": "^3.0.11",
+        "@smithy/middleware-content-length": "^3.0.13",
+        "@smithy/middleware-endpoint": "^3.2.6",
+        "@smithy/middleware-retry": "^3.0.31",
+        "@smithy/middleware-serde": "^3.0.11",
+        "@smithy/middleware-stack": "^3.0.11",
+        "@smithy/node-config-provider": "^3.1.12",
+        "@smithy/node-http-handler": "^3.3.2",
+        "@smithy/protocol-http": "^4.1.8",
+        "@smithy/smithy-client": "^3.5.1",
+        "@smithy/types": "^3.7.2",
+        "@smithy/url-parser": "^3.0.11",
+        "@smithy/util-base64": "^3.0.0",
+        "@smithy/util-body-length-browser": "^3.0.0",
+        "@smithy/util-body-length-node": "^3.0.0",
+        "@smithy/util-defaults-mode-browser": "^3.0.31",
+        "@smithy/util-defaults-mode-node": "^3.0.31",
+        "@smithy/util-endpoints": "^2.1.7",
+        "@smithy/util-middleware": "^3.0.11",
+        "@smithy/util-retry": "^3.0.11",
+        "@smithy/util-utf8": "^3.0.0",
+        "tslib": "^2.6.2"
+      },
+      "devDependencies": {
+        "@tsconfig/node16": "16.1.3",
+        "@types/node": "^16.18.96",
+        "concurrently": "7.0.0",
+        "downlevel-dts": "0.10.1",
+        "rimraf": "3.0.2",
+        "typescript": "~4.9.5"
+      },
+      "engines": {
+        "node": ">=16.0.0"
+      },
+      "typesVersions": {
+        "<4.0": {
+          "dist-types/*": [
+            "dist-types/ts3.4/*"
+          ]
+        }
+      },
+      "author": {
+        "name": "AWS SDK for JavaScript Team",
+        "url": "https://aws.amazon.com/javascript/"
+      },
+      "license": "Apache-2.0",
+      "browser": {
+        "./dist-es/runtimeConfig": "./dist-es/runtimeConfig.browser"
+      },
+      "react-native": {
+        "./dist-es/runtimeConfig": "./dist-es/runtimeConfig.native"
+      },
+      "homepage": "https://github.com/aws/aws-sdk-js-v3/tree/main/clients/client-sso",
+      "repository": {
+        "type": "git",
+        "url": "git+https://github.com/aws/aws-sdk-js-v3.git",
+        "directory": "clients/client-sso"
+      },
+      "_id": "@aws-sdk/client-sso@3.716.0",
+      "bugs": {
+        "url": "https://github.com/aws/aws-sdk-js-v3/issues"
+      },
+      "_nodeVersion": "18.20.3",
+      "_npmVersion": "10.7.0",
+      "dist": {
+        "integrity": "sha512-5Nb0jJXce2TclbjG7WVPufwhgV1TRydz1QnsuBtKU0AdViEpr787YrZhPpGnNIM1Dx+R1H/tmAHZnOoohS6D8g==",
+        "shasum": "05cfe21f41fc058e0f619557a8023ae5008f70a3",
+        "tarball": "https://verdaccio.mrsdev.ru/@aws-sdk%2fclient-sso/-/client-sso-3.716.0.tgz",
+        "fileCount": 92,
+        "unpackedSize": 203037,
+        "signatures": [
+          {
+            "keyid": "SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA",
+            "sig": "MEUCIQD+cAU5Ik7lQdPsMATT5H9Rs287lWS3/7st9h7LwCoFOwIgKkdNBbffHxNta/o6O8tYeKipX+2x9ReSjYIvfG08VAo="
+          }
+        ]
+      },
+      "_npmUser": {
+        "name": "aws-sdk-bot",
+        "email": "aws-sdk-js-automation@amazon.com"
+      },
+      "directories": {},
+      "maintainers": [
+        {
+          "name": "amzn-oss",
+          "email": "osa-3p@amazon.com"
+        },
+        {
+          "name": "aws-sdk-bot",
+          "email": "aws-sdk-js-automation@amazon.com"
+        },
+        {
+          "name": "trivikr-aws",
+          "email": "trivikr@amazon.com"
+        },
+        {
+          "name": "mattsb42-aws",
+          "email": "bullocm@amazon.com"
+        },
+        {
+          "name": "kuhe",
+          "email": "george.jing.fu+npm@gmail.com"
+        }
+      ],
+      "_npmOperationalInternal": {
+        "host": "s3://npm-registry-packages-npm-production",
+        "tmp": "tmp/client-sso_3.716.0_1734638336371_0.06829078255989973"
+      },
+      "_hasShrinkwrap": false,
+      "contributors": []
     }
   },
   "time": {
     "created": "2020-01-08T03:14:16.291Z",
     "1.0.0-alpha.1": "2020-01-08T03:14:16.692Z",
-    "modified": "2024-12-17T19:55:25.103Z",
+    "modified": "2024-12-19T19:58:56.815Z",
     "1.0.0-alpha.2": "2020-01-09T23:19:55.564Z",
     "1.0.0-alpha.3": "2020-01-10T05:11:09.168Z",
     "1.0.0-alpha.4": "2020-01-10T22:50:03.271Z",
@@ -54731,17 +54878,18 @@
     "3.709.0": "2024-12-10T20:36:51.552Z",
     "3.712.0": "2024-12-13T20:13:59.908Z",
     "3.713.0": "2024-12-16T20:05:14.402Z",
-    "3.714.0": "2024-12-17T19:55:24.841Z"
+    "3.714.0": "2024-12-17T19:55:24.841Z",
+    "3.716.0": "2024-12-19T19:58:56.588Z"
   },
   "users": {},
   "dist-tags": {
     "alpha": "1.0.0-alpha.23",
-    "latest": "3.714.0",
+    "latest": "3.716.0",
     "beta": "1.0.0-beta.5",
     "gamma": "1.0.0-gamma.11",
     "rc": "3.5.1-rc.0"
   },
-  "_rev": "71-84c7d720959540b3",
+  "_rev": "72-825367026ae1d979",
   "_id": "@aws-sdk/client-sso",
   "readme": "<!-- generated file, do not edit directly -->\n\n# @aws-sdk/client-sso\n\n## Description\n\nAWS SDK for JavaScript SSO Client for Node.js, Browser and React Native.\n\n<p>AWS IAM Identity Center (successor to AWS Single Sign-On) Portal is a web service that makes it easy for you to assign user access to\nIAM Identity Center resources such as the AWS access portal. Users can get AWS account applications and roles\nassigned to them and get federated into the application.</p>\n<note>\n<p>Although AWS Single Sign-On was renamed, the <code>sso</code> and\n<code>identitystore</code> API namespaces will continue to retain their original name for\nbackward compatibility purposes. For more information, see <a href=\"https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html#renamed\">IAM Identity Center rename</a>.</p>\n</note>\n<p>This reference guide describes the IAM Identity Center Portal operations that you can call\nprogramatically and includes detailed information on data types and errors.</p>\n<note>\n<p>AWS provides SDKs that consist of libraries and sample code for various programming\nlanguages and platforms, such as Java, Ruby, .Net, iOS, or Android. The SDKs provide a\nconvenient way to create programmatic access to IAM Identity Center and other AWS services. For more\ninformation about the AWS SDKs, including how to download and install them, see <a href=\"http://aws.amazon.com/tools/\">Tools for Amazon Web Services</a>.</p>\n</note>\n\n## Installing\n\nTo install this package, simply type add or install @aws-sdk/client-sso\nusing your favorite package manager:\n\n- `npm install @aws-sdk/client-sso`\n- `yarn add @aws-sdk/client-sso`\n- `pnpm add @aws-sdk/client-sso`\n\n## Getting Started\n\n### Import\n\nThe AWS SDK is modulized by clients and commands.\nTo send a request, you only need to import the `SSOClient` and\nthe commands you need, for example `ListAccountsCommand`:\n\n```js\n// ES5 example\nconst { SSOClient, ListAccountsCommand } = require(\"@aws-sdk/client-sso\");\n```\n\n```ts\n// ES6+ example\nimport { SSOClient, ListAccountsCommand } from \"@aws-sdk/client-sso\";\n```\n\n### Usage\n\nTo send a request, you:\n\n- Initiate client with configuration (e.g. credentials, region).\n- Initiate command with input parameters.\n- Call `send` operation on client with command object as input.\n- If you are using a custom http handler, you may call `destroy()` to close open connections.\n\n```js\n// a client can be shared by different commands.\nconst client = new SSOClient({ region: \"REGION\" });\n\nconst params = {\n  /** input parameters */\n};\nconst command = new ListAccountsCommand(params);\n```\n\n#### Async/await\n\nWe recommend using [await](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/await)\noperator to wait for the promise returned by send operation as follows:\n\n```js\n// async/await.\ntry {\n  const data = await client.send(command);\n  // process data.\n} catch (error) {\n  // error handling.\n} finally {\n  // finally.\n}\n```\n\nAsync-await is clean, concise, intuitive, easy to debug and has better error handling\nas compared to using Promise chains or callbacks.\n\n#### Promises\n\nYou can also use [Promise chaining](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Using_promises#chaining)\nto execute send operation.\n\n```js\nclient.send(command).then(\n  (data) => {\n    // process data.\n  },\n  (error) => {\n    // error handling.\n  }\n);\n```\n\nPromises can also be called using `.catch()` and `.finally()` as follows:\n\n```js\nclient\n  .send(command)\n  .then((data) => {\n    // process data.\n  })\n  .catch((error) => {\n    // error handling.\n  })\n  .finally(() => {\n    // finally.\n  });\n```\n\n#### Callbacks\n\nWe do not recommend using callbacks because of [callback hell](http://callbackhell.com/),\nbut they are supported by the send operation.\n\n```js\n// callbacks.\nclient.send(command, (err, data) => {\n  // process err and data.\n});\n```\n\n#### v2 compatible style\n\nThe client can also send requests using v2 compatible style.\nHowever, it results in a bigger bundle size and may be dropped in next major version. More details in the blog post\non [modular packages in AWS SDK for JavaScript](https://aws.amazon.com/blogs/developer/modular-packages-in-aws-sdk-for-javascript/)\n\n```ts\nimport * as AWS from \"@aws-sdk/client-sso\";\nconst client = new AWS.SSO({ region: \"REGION\" });\n\n// async/await.\ntry {\n  const data = await client.listAccounts(params);\n  // process data.\n} catch (error) {\n  // error handling.\n}\n\n// Promises.\nclient\n  .listAccounts(params)\n  .then((data) => {\n    // process data.\n  })\n  .catch((error) => {\n    // error handling.\n  });\n\n// callbacks.\nclient.listAccounts(params, (err, data) => {\n  // process err and data.\n});\n```\n\n### Troubleshooting\n\nWhen the service returns an exception, the error will include the exception information,\nas well as response metadata (e.g. request id).\n\n```js\ntry {\n  const data = await client.send(command);\n  // process data.\n} catch (error) {\n  const { requestId, cfId, extendedRequestId } = error.$metadata;\n  console.log({ requestId, cfId, extendedRequestId });\n  /**\n   * The keys within exceptions are also parsed.\n   * You can access them by specifying exception names:\n   * if (error.name === 'SomeServiceException') {\n   *     const value = error.specialKeyInException;\n   * }\n   */\n}\n```\n\n## Getting Help\n\nPlease use these community resources for getting help.\nWe use the GitHub issues for tracking bugs and feature requests, but have limited bandwidth to address them.\n\n- Visit [Developer Guide](https://docs.aws.amazon.com/sdk-for-javascript/v3/developer-guide/welcome.html)\n  or [API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/index.html).\n- Check out the blog posts tagged with [`aws-sdk-js`](https://aws.amazon.com/blogs/developer/tag/aws-sdk-js/)\n  on AWS Developer Blog.\n- Ask a question on [StackOverflow](https://stackoverflow.com/questions/tagged/aws-sdk-js) and tag it with `aws-sdk-js`.\n- Join the AWS JavaScript community on [gitter](https://gitter.im/aws/aws-sdk-js-v3).\n- If it turns out that you may have found a bug, please [open an issue](https://github.com/aws/aws-sdk-js-v3/issues/new/choose).\n\nTo test your universal JavaScript code in Node.js, browser and react-native environments,\nvisit our [code samples repo](https://github.com/aws-samples/aws-sdk-js-tests).\n\n## Contributing\n\nThis client code is generated automatically. Any modifications will be overwritten the next time the `@aws-sdk/client-sso` package is updated.\nTo contribute to client you can check our [generate clients scripts](https://github.com/aws/aws-sdk-js-v3/tree/main/scripts/generate-clients).\n\n## License\n\nThis SDK is distributed under the\n[Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0),\nsee LICENSE for more information.\n\n## Client Commands (Operations List)\n\n<details>\n<summary>\nGetRoleCredentials\n</summary>\n\n[Command API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/sso/command/GetRoleCredentialsCommand/) / [Input](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-sso/Interface/GetRoleCredentialsCommandInput/) / [Output](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-sso/Interface/GetRoleCredentialsCommandOutput/)\n\n</details>\n<details>\n<summary>\nListAccountRoles\n</summary>\n\n[Command API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/sso/command/ListAccountRolesCommand/) / [Input](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-sso/Interface/ListAccountRolesCommandInput/) / [Output](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-sso/Interface/ListAccountRolesCommandOutput/)\n\n</details>\n<details>\n<summary>\nListAccounts\n</summary>\n\n[Command API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/sso/command/ListAccountsCommand/) / [Input](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-sso/Interface/ListAccountsCommandInput/) / [Output](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-sso/Interface/ListAccountsCommandOutput/)\n\n</details>\n<details>\n<summary>\nLogout\n</summary>\n\n[Command API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/sso/command/LogoutCommand/) / [Input](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-sso/Interface/LogoutCommandInput/) / [Output](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-sso/Interface/LogoutCommandOutput/)\n\n</details>",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{4d/12/0a3b82d044ce3cdcb6c261ed0bd826340dfc15370ee6eae876fa88dc7bacb8a2c3965ddbd4c5d32bacfb8d334f1eaf222d730c829b73e6233251885f313c → cd/b7/183f02e94f8a9118ec209496c5ce42f59266d49b2da890a0dab12684c444aa7368de34aab949a26ab423ea6105962e5e2a8ceba115499bbfb0275ba4ceea}

@@ -237,7 +237,7 @@
   "dist-tags": {
     "latest": "1.0.3"
   },
-  "_rev": "1073-0a23e7c426b17ecd",
+  "_rev": "1077-ffa1e5dbe05272b6",
   "_id": "core-util-is",
   "readme": "# core-util-is\n\nThe `util.is*` functions introduced in Node v0.12.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{42/89/d51074908ab124a6a088b90a776b8414211aa1559007f142288709b96b2daddd9d90a19fc7624a015ffd50c8c26892fa4bbbd55847e1b023bb995fc83f96 → ce/f5/41800f1f58b4048394fd4ed70c20025dadfd06d380f62d2d20fceb64eee8b96c6eaa6e85fd6419767489cfcec9758adfb762609bf9d701d097405cdaf7e7}

@@ -12080,7 +12080,7 @@
     "gamma": "1.0.0-gamma.8",
     "rc": "1.0.0-rc.10"
   },
-  "_rev": "50-d0d0cf5d64cd7a17",
+  "_rev": "51-79063a0d19ebffa9",
   "_id": "@aws-sdk/eventstream-serde-node",
   "readme": "# @aws-sdk/eventstream-serde-node\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/eventstream-serde-node/latest.svg)](https://www.npmjs.com/package/@aws-sdk/eventstream-serde-node)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/eventstream-serde-node.svg)](https://www.npmjs.com/package/@aws-sdk/eventstream-serde-node)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{00/e8/dbba1578346ffbd2aa5e3e42f5e948539a6123339b6c65e71c1464bad9d3ca6e9385118631608229aa125e09df840916debbbf8d187e89c63953d3ceebe0 → cf/e9/2f9f14bf60ae2029ee5d1b6b8f7c1a444594e90dfe7de1c4d05acaffe23c7f743f4feeb647bbc300940e104e020e82acd620846f706ac842837c41bfe181}

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

package/npm-cache/_cacache/content-v2/sha512/{a2/80/5bb8be0691cdb5ec62d15e9342d269f0f963b0251b5b0af6e40e5cf233414621d477eb211c6d3a4c3a50d6d78d1e74b70f80649adff93af82c35fb32643a → d1/b4/2c1433c2e69e853079e8d5269caaf233b7d4723eb6de1ca0b8fc5ce22e680c7d7faf5874706c00f9c72e6a808064d494716d4de279a19420f5d2af912317}

@@ -350,7 +350,7 @@
   "dist-tags": {
     "latest": "1.0.1"
   },
-  "_rev": "124-3c1a0c4f06c35dc2",
+  "_rev": "125-04d95fe96c2aa73a",
   "_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/{04/f4/213ff6fd9a4547af23e15580176fe2a2c03ee8cb1445fa3fb836f604333b72df77bca23ade62b8ba11b1e71c20c2405ea258026669e51369fb337c53e3cd → d2/7b/a8aad39b3b6a6f7ea5c94a2178b66fd68db268c692fa2b67af818fe9ea4b3fddf12bf10f7b0e68eb57a42f6b4af709a51d7823a0a97da26b6c3f35ed6d61}

@@ -1470,7 +1470,7 @@
   "dist-tags": {
     "latest": "1.5.1"
   },
-  "_rev": "1806-0028ccd3711ddee8",
+  "_rev": "1810-eb3c1f93ce4ce544",
   "_id": "base64-js",
   "readme": "base64-js\n=========\n\n`base64-js` does basic base64 encoding/decoding in pure JS.\n\n[![build status](https://secure.travis-ci.org/beatgammit/base64-js.png)](http://travis-ci.org/beatgammit/base64-js)\n\nMany browsers already have base64 encoding/decoding functionality, but it is for text data, not all-purpose binary data.\n\nSometimes encoding/decoding binary data in the browser is useful, and that is what this module does.\n\n## install\n\nWith [npm](https://npmjs.org) do:\n\n`npm install base64-js` and `var base64js = require('base64-js')`\n\nFor use in web browsers do:\n\n`<script src=\"base64js.min.js\"></script>`\n\n[Get supported base64-js with the Tidelift Subscription](https://tidelift.com/subscription/pkg/npm-base64-js?utm_source=npm-base64-js&utm_medium=referral&utm_campaign=readme)\n\n## methods\n\n`base64js` has three exposed functions, `byteLength`, `toByteArray` and `fromByteArray`, which both take a single argument.\n\n* `byteLength` - Takes a base64 string and returns length of byte array\n* `toByteArray` - Takes a base64 string and returns a byte array\n* `fromByteArray` - Takes a byte array and returns a base64 string\n\n## license\n\nMIT",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{3a/78/f6c6128fac440a1e669f594e744aec40c814fa0fbd63969f3a53acecd4857e0d966dd17bcc819de198578dcaf2bece64c598f838c0a8eb753de2f9a73464 → d4/02/eb592cf422bd6ac7ef262c319257781a20f560e1d8c7fd7a45b7f245450b447d44ec22ca7029c62d918a3183162a4e21f59987a6298bea74d7fd607d02f9}

@@ -7081,7 +7081,7 @@
   "dist-tags": {
     "latest": "3.374.0"
   },
-  "_rev": "50-793d97da9f0dd678",
+  "_rev": "51-07f0bcaa03e0ac8f",
   "_id": "@aws-sdk/util-stream-node",
   "readme": "# @aws-sdk/util-stream-node\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/util-stream-node/latest.svg)](https://www.npmjs.com/package/@aws-sdk/util-stream-node)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/util-stream-node.svg)](https://www.npmjs.com/package/@aws-sdk/util-stream-node)\n\n> Deprecated package\n>\n> This internal package is deprecated in favor of [@aws-sdk/util-stream](https://www.npmjs.com/package/@aws-sdk/util-stream).\n\nPackage with utilities to operate on Node.JS streams.\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}

package/npm-cache/_cacache/content-v2/sha512/{ff/6e/97d5fa201c05f93d4a3f38cd13b320ad3bd10ad38ada4b89ee3128945ed8bf932434ef5f12d02d0edf9da33633d107607fc0b3ad50474480c555cc54e0f5 → d4/30/cde5af78447ee0b058888263041fcc0511335f4493f7ad86b4094741c3e0324ccf2eec9cf3e59b299691cb524c34e254e057c60a9b4e8e0f42ad2618a7b6}

@@ -5282,7 +5282,7 @@
     "gamma": "1.0.0-gamma.7",
     "rc": "1.0.0-rc.8"
   },
-  "_rev": "58-e254405c073bd9e4",
+  "_rev": "59-5051a64f74f74921",
   "_id": "@aws-sdk/util-uri-escape",
   "readme": "# @aws-sdk/util-uri-escape\n\n[![NPM version](https://img.shields.io/npm/v/@aws-sdk/util-uri-escape/latest.svg)](https://www.npmjs.com/package/@aws-sdk/util-uri-escape)\n[![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/util-uri-escape.svg)](https://www.npmjs.com/package/@aws-sdk/util-uri-escape)\n\n> An internal package\n\n## Usage\n\nYou probably shouldn't, at least directly.",
   "_attachments": {}