fs: add stream utilities to FileHandle

[aduh95]

Adding filehandle.createReadStream and filehandle.createWriteStream methods to FileHandle class. This is useful to be able create ReadStream or WriteStream from fs/promises.

import { open } from 'node:fs/promises';
import { stdout } from 'node:process';

try {
  const textFile = await open(new URL('./file.txt', import.meta.url));
  textFile.createReadStream().pipe(stdout);
} catch (err) {
  // error while opening the file
  // ...
}

It also accept the same functions as fs.createReadStream and fs.createWriteStream respectively:

import { open } from 'node:fs/promises';
import { stdout } from 'node:process';
import { finished } from 'node:stream/promises';

let textFile;
try {
  textFile = await open(new URL('./file.txt', import.meta.url));
  await finished(textFile.createReadStream({ autoClose: false, encoding: 'utf8' }).pipe(stdout));
} catch (err) {
  // error while opening the file or while streaming the file
  // ...
} finally {
  await textFile?.close();
}

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/39824/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/39827/

[ronag]

Can we remove autoClose & emitClose from here?

[aduh95]

Could you explain why?

[ronag]

They are legacy. The only reason we have still have them is to avoid breakage. Since this is a new API they are not necessary.

[aduh95]

It’s a new way for exposing the same old API, removing it would be harder than keeping it – also I don’t think they’re documented as legacy anywhere, so that’s probably best to leave that discussion for another PR.

[ronag]

Can we remove autoClose & emitClose from here?

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/39970/ 💛

[aduh95]

/cc @nodejs/fs

[jasnell]

Landed in 026bd82

[danielleadams]

@aduh95 do you mind opening a backport PR to v16.x-staging? The PR broke the lint-js script. Thanks!