Skip to content

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

haramj
Copy link

@haramj haramj commented Jul 13, 2025

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

@nodejs-github-bot nodejs-github-bot added doc Issues and PRs related to the documentations. errors Issues and PRs related to JavaScript errors originated in Node.js core. labels Jul 13, 2025
@jasnell jasnell added the request-ci Add this label to start a Jenkins CI on a PR. label Jul 13, 2025
@LiviaMedeiros LiviaMedeiros added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. and removed request-ci Add this label to start a Jenkins CI on a PR. author ready PRs that have at least one approval, no pending requests for changes, and a CI started. labels Jul 13, 2025
@LiviaMedeiros
Copy link
Member

LGTM with adjusting the commit message to adhere guidelines (the message length has to be 72 or less).
Not needs-ci PRs that need a full CI run. since this is doc-only.

@haramj
Copy link
Author

haramj commented Jul 13, 2025

The commit message has been updated per guidelines and all reviews are approved.
I don’t have merge permissions.
Could someone please merge this PR?

@LiviaMedeiros LiviaMedeiros added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Jul 14, 2025
Copy link
Member

@LiviaMedeiros LiviaMedeiros left a 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. doc Issues and PRs related to the documentations. errors Issues and PRs related to JavaScript errors originated in Node.js core.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants