From 50d983e80bf8fccb595f2964fdc7f3c46a988558 Mon Sep 17 00:00:00 2001 From: Ian Kerins Date: Mon, 21 Oct 2024 20:17:55 -0400 Subject: [PATCH] doc: remove outdated remarks about `highWaterMark` in fs `Readable`'s `highWaterMark` has in fact been 64KiB since #52037. PR-URL: https://github.com/nodejs/node/pull/55462 Reviewed-By: Luigi Pinca Reviewed-By: James M Snell --- doc/api/fs.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/doc/api/fs.md b/doc/api/fs.md index 0c26b4afae9db1..0b85ad82bf274d 100644 --- a/doc/api/fs.md +++ b/doc/api/fs.md @@ -270,9 +270,6 @@ added: v16.11.0 * `signal` {AbortSignal|undefined} **Default:** `undefined` * Returns: {fs.ReadStream} -Unlike the 16 KiB default `highWaterMark` for a {stream.Readable}, the stream -returned by this method has a default `highWaterMark` of 64 KiB. - `options` can include `start` and `end` values to read a range of bytes from the file instead of the entire file. Both `start` and `end` are inclusive and start counting at 0, allowed values are in the @@ -2551,9 +2548,6 @@ changes: * `signal` {AbortSignal|null} **Default:** `null` * Returns: {fs.ReadStream} -Unlike the 16 KiB default `highWaterMark` for a {stream.Readable}, the stream -returned by this method has a default `highWaterMark` of 64 KiB. - `options` can include `start` and `end` values to read a range of bytes from the file instead of the entire file. Both `start` and `end` are inclusive and start counting at 0, allowed values are in the