fix: allow Uint8Arrays to be passed to FsWriteStream

[MrMYHuang]

From the Volume write function declaration, we can see the second argument has a type of Buffer or Uint8Array.

memfs/src/volume.ts

Lines 1211 to 1218 in 0587738

	write(
	fd: number,
	buffer: Buffer | Uint8Array,
	offset: number,
	length: number,
	position: number,
	callback: (...args) => void,
	);

However, FsWriteStream.prototype._write only allows a type of Buffer:

memfs/src/volume.ts

Lines 2569 to 2591 in 0587738

	FsWriteStream.prototype._write = function(data, encoding, cb) {
	if (!(data instanceof Buffer)) return this.emit('error', new Error('Invalid data'));
	if (typeof this.fd !== 'number') {
	return this.once('open', function() {
	this._write(data, encoding, cb);
	});
	}
	var self = this; // tslint:disable-line no-this-assignment
	this._vol.write(this.fd, data, 0, data.length, this.pos, (er, bytes) => {
	if (er) {
	if (self.autoClose && self.destroy) {
	self.destroy();
	}
	return cb(er);
	}
	self.bytesWritten += bytes;
	cb();
	});
	if (this.pos !== undefined) this.pos += data.length;
	};

This issue does cause an error of the combination: webpack 5 + node-downloader-helper + memfs.
node-downloader-helper and its dependencies can call FsWriteStream.prototype._write with a data of type Uint8Array.
(If anyone has an interest for an example, please try my project https://github.com/MrMYHuang/taa with memfs 3.4.3.)

After applying my changes, this issues is fixed.

[streamich]

🎉 This PR is included in version 3.4.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀