chore(deps): update dependency get-stream to v9

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
get-stream	6.0.1 -> 9.0.1

---

Release Notes

sindresorhus/get-stream (get-stream)

v9.0.1

Compare Source

• Upgrade ReadableStream[Symbol.asyncIterator] ponyfill (#​128) df42674

v9.0.0

Compare Source

Breaking

• Require Node.js 18 (#​111) 7ccab70

Improvements

• Fix browser support (#​122) 4d233d3
• Allow multiple readers at once (#​121) a51d085

v8.0.1

Compare Source

Fixes

• Ensure error.bufferedData is as full as possible. (#​106)
• Fix the maxBuffer option being one byte off in some edge case. (#​105)

v8.0.0

Compare Source

Huge thanks to @​ehmicky for doing all the work for this release 🙌

Breaking

• Remove the encoding option. (#​69, #​67)
  • This package handles binary, UTF-8 and object streams.
  • For other encodings like UTF-16, hexacimal and base64, please see the following tip. (#​84)
  • Methods like buffer.toString('hex') or buffer.toString('base64') can also be used.

Improvements

• Support any JavaScript environment, including browsers. (#​85)
• Support web streams (ReadableStream). (#​82, #​78, #​79, #​80)
• Support async iterables. (#​69, #​93)
• Add getStreamAsArray() method to pass streams in object mode. (#​86)
• Add getStreamAsArrayBuffer() method to return the stream as an ArrayBuffer. (#​81)
• When the stream is larger than the maximum size for a string, buffer or ArrayBuffer, set error.bufferedData with the partially read data instead of leaving it empty. (#​68, #​48)

Fixes

• Do not crash on big streams (with one/many GBs). (#​66)
• Ensure maxBuffer stops infinite streams. (#​62)
• Stop consuming the streaming when hitting maxBuffer. (#​42, #​69).
• Set error.bufferedData when the stream errors for other reasons than maxBuffer. (#​56, #​63)
• Ensure error.bufferedData is smaller than maxBuffer. (#​89)

TypeScript types

• The stream argument must be a Readable, ReadableStream or AsyncIterable. (#​71)

Documentation

• Add tips on alternatives, Blob and JSON streaming. (#​58, #​95, #​96, #​97)

Performance

• Do not block the event loop when the stream ends. (#​92)

v7.0.1

Compare Source

• Work around issue with handling large sizes e58d141

v7.0.0

Compare Source

Breaking

• Require Node.js 16 70571f8
• This package is now pure ESM. Please read this.
• Removed getStream.array()
  • It complicated the codebase considerably and I personally never used it.
  • You can use readableStream.toArray() instead. Example
• const getStream = require('get-stream'); getStream.buffer(…); → import {getStreamAsBuffer} from 'get-stream'; getStreamAsBuffer(…);
• const getStream = require('get-stream'); getStream.MaxBufferError; → import {MaxBufferError} from 'get-stream'; MaxBufferError;

Tip

You may not need this package anymore.

---

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: xmltest@1.5.0
npm ERR! Found: get-stream@9.0.1
npm ERR! node_modules/get-stream
npm ERR!   dev get-stream@"9.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer get-stream@"^6.0.0" from xmltest@1.5.0
npm ERR! node_modules/xmltest
npm ERR!   dev xmltest@"1.5.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: get-stream@6.0.1
npm ERR! node_modules/get-stream
npm ERR!   peer get-stream@"^6.0.0" from xmltest@1.5.0
npm ERR!   node_modules/xmltest
npm ERR!     dev xmltest@"1.5.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-03-26T19_24_34_831Z-debug-0.log

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 9.x releases. But if you manually upgrade to 9.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.