Accept `Blob`s anywhere where a `Buffer` is currently accepted for writing

What is the problem this feature will solve?

Because Buffers aren't immutable, any time a Buffer is passed to something which will perform an asynchronous write, there is a concurrency hazard where the buffer could conceivably get modified before it gets a chance to be written. This can lead to bugs which are hard to track down. (I speak from experience.)

What is the feature you are proposing to solve the problem?

Anywhere where Buffer is currently accepted for a write operation, e.g. and perhaps most notably stream.Writable.write() and stream.Writable.end(), also make it acceptable to pass a Blob. Blobs are always immutable.

What alternatives have you considered?

Just keep using Buffers, mostly keep my fingers crossed, and sometimes make copies of Buffers as a safeguard.

(Note: It also makes sense to have a way to optionally have Blobs returned from readable streams, but I figure that'd be a different feature request.)

Node.js の stream.Writable.write() と stream.Writable.end() のエントリポイントから始め、非同期書き込みで現在 Buffer を受け付けている他の API も調査します。必要な Blob の動作を判断し、関連する実装、テスト、API ドキュメントを更新して、readable-stream の戻り値の動作を変更せずに Blob 入力が一貫して受け付けられるようにします。