chore: drop stream-buffers in favor of a generator

[ferhatelmas]

What kind of change does this PR introduce?

Refactor

What is the current behavior?

stream-buffers dependency is used for a test to construct a stream that emits slow chunks.

What is the new behavior?

Replace it with a generator that sleeps in between since extended API of the dependency isn't needed.

Additional context

Less dependencies is better.

[Copilot]

Pull request overview

Removes the stream-buffers dependency by rewriting the one test case that needed a “slow-chunking” readable stream to use a native async generator + Readable.from, keeping the same behavioral intent while reducing supply-chain surface area.

Changes:

• Replaced ReadableStreamBuffer usage in the S3 protocol test with Readable.from(async function* ...) and a timed delay between chunks.
• Removed stream-buffers and its type package from package.json / package-lock.json.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File	Description
src/test/s3-protocol.test.ts	Replaces the slow-chunk stream construction with a native generator-based readable stream.
package.json	Drops stream-buffers and @types/stream-buffers dependencies.
package-lock.json	Removes the corresponding locked dependencies.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coveralls]

Coverage Report for CI Build 25731246483

Coverage increased (+0.006%) to 74.378%

Details

• Coverage increased (+0.006%) from the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	10297
Covered Lines:	8066
Line Coverage:	78.33%
Relevant Branches:	5951
Covered Branches:	4019
Branch Coverage:	67.53%
Branches in Coverage %:	Yes
Coverage Strength:	410.86 hits per line

---

💛 - Coveralls