-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
doc: clarify ERR_FS_FILE_TOO_LARGE explanation to reflect fs.readFile() I/O limit #59050
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
LGTM with adjusting the commit message to adhere guidelines (the message length has to be 72 or less). |
Co-authored-by: James M Snell <[email protected]>
The commit message has been updated per guidelines and all reviews are approved. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you.
A pull request needs to stay open for at least 48 hours from when it is submitted (which makes about 32 more hours from now), and afterwards any collaborator can merge this.
All reviews are done and 48 hours have passed. Could someone please merge this? 🙏 |
This comment was marked as outdated.
This comment was marked as outdated.
Landed in 9f486c3 |
PR-URL: #59050 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: LiviaMedeiros <[email protected]>
Fix: clarify ERR_FS_FILE_TOO_LARGE message to reflect fs.readFile() I/O limit
The error previously suggested the issue might be due to Buffer limitations,
but in fact it's an internal constraint of fs.readFile(). Updated the
documentation to avoid confusion and guide users toward fs.createReadStream()
for large files.
ref #55864