doc: clarify ERR_FS_FILE_TOO_LARGE to reflect fs.readFile() I/O limit · nodejs/node@2d1dcb8 · GitHub

nodejs / node Public

• Notifications You must be signed in to change notification settings
• Fork 36.6k
• Star 120k

• Code
• Issues 633
• Pull requests 747
• Actions
• Projects
• Security and quality
• Insights

Additional navigation options

Commit 2d1dcb8

Browse filesBrowse the repository at this point in the historyBrowse files

haramj

authored and

targos

committed

doc: clarify ERR_FS_FILE_TOO_LARGE to reflect fs.readFile() I/O limit

PR-URL: #59050 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: LiviaMedeiros <livia@cirno.name>

1 parent 999b5e5 commit 2d1dcb8
Copy full SHA for 2d1dcb8

1 file changed

+4-2Lines changed: 4 additions & 2 deletions

File tree

Expand file treeCollapse file tree

Open diff view settings

Filter options

• doc/api
  • errors.md

Expand file treeCollapse file tree

Open diff view settings

Collapse file

‎doc/api/errors.md‎

Copy file name to clipboardExpand all lines: doc/api/errors.md

+4-2Lines changed: 4 additions & 2 deletions

• Display the source diff
• Display the rich diff

Original file line number	Diff line number	Diff line change
@@ -1362,8 +1362,10 @@ Path is a directory.
1362	1362
1363	1363	### `ERR_FS_FILE_TOO_LARGE`
1364	1364
1365		- An attempt has been made to read a file whose size is larger than the maximum
1366		- allowed size for a `Buffer`.
	1365	+ An attempt was made to read a file larger than the supported 2 GiB limit for
	1366	+ `fs.readFile()`. This is not a limitation of `Buffer`, but an internal I/O constraint.
	1367	+ For handling larger files, consider using `fs.createReadStream()` to read the
	1368	+ file in chunks.
1367	1369
1368	1370	<a id="ERR_FS_WATCH_QUEUE_OVERFLOW"></a>
1369	1371

0 commit comments

Comments

0 (0)