fs: use sized reads for large files in readFileUtf8 by codebytere · Pull Request #65328 · nodejs/node

codebytere · 2026-08-16T15:51:21Z

fs.readFileSync(path, 'utf8') gets +19…42 % on 4 MiB files and +60…231 % on 256 KiB files, with small files untouched, by reading large files into one right-sized buffer instead of 8 KiB at a time.

fs/readfile-utf8-fastpath.js source='path' content='ascii' size=262144 *** 231.14 % ±2.91%
fs/readfile-utf8-fastpath.js source='path' content='utf8_mixed' size=262144 *** 60.16 % ±0.93%
fs/readfile-utf8-fastpath.js source='path' content='ascii' size=4194304 *** 41.86 % ±5.85%
fs/readfile-utf8-fastpath.js source='path' content='utf8_mixed' size=4194304 *** 19.06 % ±2.92%
fs/readfile-utf8-fastpath.js source='fd' * size=4194304 *** +22…27 %
fs/readfile-utf8-fastpath.js * * size≤16384 0…+2 %
fs/readFileSync.js (1 KiB) ~0 % n.s.

(Linux x64, 30 runs. A 300 KB file goes from 39 syscalls to 5.)

ReadFileUtf8 - behind readFileSync(…, 'utf8') and therefore every CommonJS module load - read in 8 KiB read()s, appending each to a std::string. Files that fit the first 8 KiB read behave exactly as before. Once a read fills the stack buffer, the rest goes straight into one heap buffer: a 64 KiB step first (so files up to 64 KiB take the same reads as today and no fstat), then sized from fstat() if that fills too, with geometric growth as the fallback. The size is only an allocation hint - reading continues until read() returns 0, so procfs/sysfs and concurrently changing files behave as before and StringBytes::Encode() sees exactly the bytes read. Allocation failure throws ERR_MEMORY_ALLOCATION_FAILED.

Tests:test-fs-readfilesync-utf8-sizes.js (new): equals readFileSync(path).toString('utf8') around every internal boundary (0 … 8 MiB+5) with multi-byte characters straddling chunk edges; by fd from start / at EOF / mid-file; binary input; /proc/self/maps and friends; EISDIR. fs, module and require suites pass.

Disclosure: the code, test, measurements and this description were written by Claude Code, directed and reviewed by @codebytere.

codecov · 2026-08-16T22:09:50Z

Codecov Report

❌ Patch coverage is 78.26087% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.11%. Comparing base (30bff4a) to head (60bf6b9).
⚠️ Report is 149 commits behind head on main.

Files with missing lines	Patch %	Lines
src/node_file.cc	78.26%	2 Missing and 8 partials ⚠️

Additional details and impacted files

@@ Coverage Diff @@## main #65328 +/- ##
==========================================
- Coverage 90.13% 90.11% -0.03% 
==========================================
Files 752 751 -1 Lines 251568 252570 +1002 Branches 47270 47526 +256 ==========================================
+ Hits 226759 227604 +845 - Misses 16168 16247 +79 - Partials 8641 8719 +78

Files with missing lines	Coverage Δ
src/node_file.cc	`74.10% <78.26%> (-0.10%)`	⬇️

... and 121 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

mcollina

lgtm

nodejs-github-bot · 2026-08-21T10:39:01Z

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

nodejs-github-bot · 2026-08-21T14:09:44Z

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

nodejs-github-bot · 2026-08-21T21:03:56Z

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

nodejs-github-bot · 2026-08-22T17:50:43Z

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

fs.readFileSync(path, 'utf8') read the whole file in 8 KiB read() calls appended to a std::string, i.e. one syscall and a potential reallocation per 8 KiB (an 8 MiB file took ~1400 read() calls). Keep the exact old sequence for small files (one read into the 8 KiB stack buffer, one read reporting EOF). Once a read fills the stack buffer, read the rest directly into one heap buffer sized from fstat() (plus one byte so that the EOF read does not force growth), growing geometrically only when the size is unavailable or wrong. The size is only an allocation hint: reading continues until read() reports EOF, so procfs/sysfs files, FIFOs, files that change while being read and file descriptors positioned mid-file behave as before, and the bytes handed to StringBytes::Encode() are exactly the ones read. Signed-off-by: Shelley Vohr <shelley.vohr@gmail.com>

nodejs-github-bot · 2026-08-23T08:02:53Z

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

nodejs-github-bot · 2026-08-23T19:56:57Z

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

nodejs-github-bot · 2026-08-24T07:44:00Z

Landed in 18fb35a

fs.readFileSync(path, 'utf8') read the whole file in 8 KiB read() calls appended to a std::string, i.e. one syscall and a potential reallocation per 8 KiB (an 8 MiB file took ~1400 read() calls). Keep the exact old sequence for small files (one read into the 8 KiB stack buffer, one read reporting EOF). Once a read fills the stack buffer, read the rest directly into one heap buffer sized from fstat() (plus one byte so that the EOF read does not force growth), growing geometrically only when the size is unavailable or wrong. The size is only an allocation hint: reading continues until read() reports EOF, so procfs/sysfs files, FIFOs, files that change while being read and file descriptors positioned mid-file behave as before, and the bytes handed to StringBytes::Encode() are exactly the ones read. Signed-off-by: Shelley Vohr <shelley.vohr@gmail.com> PR-URL: #65328 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>

codebytere · 2026-08-16T15:51:21Z

fs.readFileSync(path, 'utf8') gets +19…42 % on 4 MiB files and +60…231 % on 256 KiB files, with small files untouched, by reading large files into one right-sized buffer instead of 8 KiB at a time.

fs/readfile-utf8-fastpath.js source='path' content='ascii' size=262144 *** 231.14 % ±2.91%
fs/readfile-utf8-fastpath.js source='path' content='utf8_mixed' size=262144 *** 60.16 % ±0.93%
fs/readfile-utf8-fastpath.js source='path' content='ascii' size=4194304 *** 41.86 % ±5.85%
fs/readfile-utf8-fastpath.js source='path' content='utf8_mixed' size=4194304 *** 19.06 % ±2.92%
fs/readfile-utf8-fastpath.js source='fd' * size=4194304 *** +22…27 %
fs/readfile-utf8-fastpath.js * * size≤16384 0…+2 %
fs/readFileSync.js (1 KiB) ~0 % n.s.

(Linux x64, 30 runs. A 300 KB file goes from 39 syscalls to 5.)

ReadFileUtf8 - behind readFileSync(…, 'utf8') and therefore every CommonJS module load - read in 8 KiB read()s, appending each to a std::string. Files that fit the first 8 KiB read behave exactly as before. Once a read fills the stack buffer, the rest goes straight into one heap buffer: a 64 KiB step first (so files up to 64 KiB take the same reads as today and no fstat), then sized from fstat() if that fills too, with geometric growth as the fallback. The size is only an allocation hint - reading continues until read() returns 0, so procfs/sysfs and concurrently changing files behave as before and StringBytes::Encode() sees exactly the bytes read. Allocation failure throws ERR_MEMORY_ALLOCATION_FAILED.

Tests:test-fs-readfilesync-utf8-sizes.js (new): equals readFileSync(path).toString('utf8') around every internal boundary (0 … 8 MiB+5) with multi-byte characters straddling chunk edges; by fd from start / at EOF / mid-file; binary input; /proc/self/maps and friends; EISDIR. fs, module and require suites pass.

Disclosure: the code, test, measurements and this description were written by Claude Code, directed and reviewed by @codebytere.

codecov · 2026-08-16T22:09:50Z

Codecov Report

❌ Patch coverage is 78.26087% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.11%. Comparing base (30bff4a) to head (60bf6b9).
⚠️ Report is 149 commits behind head on main.

Files with missing lines	Patch %	Lines
src/node_file.cc	78.26%	2 Missing and 8 partials ⚠️

Additional details and impacted files

@@ Coverage Diff @@## main #65328 +/- ##
==========================================
- Coverage 90.13% 90.11% -0.03% 
==========================================
Files 752 751 -1 Lines 251568 252570 +1002 Branches 47270 47526 +256 ==========================================
+ Hits 226759 227604 +845 - Misses 16168 16247 +79 - Partials 8641 8719 +78

Files with missing lines	Coverage Δ
src/node_file.cc	`74.10% <78.26%> (-0.10%)`	⬇️

... and 121 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

mcollina

lgtm

nodejs-github-bot · 2026-08-21T10:39:01Z

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

nodejs-github-bot · 2026-08-21T14:09:44Z

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

nodejs-github-bot · 2026-08-21T21:03:56Z

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

nodejs-github-bot · 2026-08-22T17:50:43Z

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

fs.readFileSync(path, 'utf8') read the whole file in 8 KiB read() calls appended to a std::string, i.e. one syscall and a potential reallocation per 8 KiB (an 8 MiB file took ~1400 read() calls). Keep the exact old sequence for small files (one read into the 8 KiB stack buffer, one read reporting EOF). Once a read fills the stack buffer, read the rest directly into one heap buffer sized from fstat() (plus one byte so that the EOF read does not force growth), growing geometrically only when the size is unavailable or wrong. The size is only an allocation hint: reading continues until read() reports EOF, so procfs/sysfs files, FIFOs, files that change while being read and file descriptors positioned mid-file behave as before, and the bytes handed to StringBytes::Encode() are exactly the ones read. Signed-off-by: Shelley Vohr <shelley.vohr@gmail.com>

nodejs-github-bot · 2026-08-23T08:02:53Z

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

nodejs-github-bot · 2026-08-23T19:56:57Z

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

nodejs-github-bot · 2026-08-24T07:44:00Z

Landed in 18fb35a

fs.readFileSync(path, 'utf8') read the whole file in 8 KiB read() calls appended to a std::string, i.e. one syscall and a potential reallocation per 8 KiB (an 8 MiB file took ~1400 read() calls). Keep the exact old sequence for small files (one read into the 8 KiB stack buffer, one read reporting EOF). Once a read fills the stack buffer, read the rest directly into one heap buffer sized from fstat() (plus one byte so that the EOF read does not force growth), growing geometrically only when the size is unavailable or wrong. The size is only an allocation hint: reading continues until read() reports EOF, so procfs/sysfs files, FIFOs, files that change while being read and file descriptors positioned mid-file behave as before, and the bytes handed to StringBytes::Encode() are exactly the ones read. Signed-off-by: Shelley Vohr <shelley.vohr@gmail.com> PR-URL: #65328 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>

codebytere · 2026-08-16T15:51:21Z

fs.readFileSync(path, 'utf8') gets +19…42 % on 4 MiB files and +60…231 % on 256 KiB files, with small files untouched, by reading large files into one right-sized buffer instead of 8 KiB at a time.

fs/readfile-utf8-fastpath.js source='path' content='ascii' size=262144 *** 231.14 % ±2.91%
fs/readfile-utf8-fastpath.js source='path' content='utf8_mixed' size=262144 *** 60.16 % ±0.93%
fs/readfile-utf8-fastpath.js source='path' content='ascii' size=4194304 *** 41.86 % ±5.85%
fs/readfile-utf8-fastpath.js source='path' content='utf8_mixed' size=4194304 *** 19.06 % ±2.92%
fs/readfile-utf8-fastpath.js source='fd' * size=4194304 *** +22…27 %
fs/readfile-utf8-fastpath.js * * size≤16384 0…+2 %
fs/readFileSync.js (1 KiB) ~0 % n.s.

(Linux x64, 30 runs. A 300 KB file goes from 39 syscalls to 5.)

ReadFileUtf8 - behind readFileSync(…, 'utf8') and therefore every CommonJS module load - read in 8 KiB read()s, appending each to a std::string. Files that fit the first 8 KiB read behave exactly as before. Once a read fills the stack buffer, the rest goes straight into one heap buffer: a 64 KiB step first (so files up to 64 KiB take the same reads as today and no fstat), then sized from fstat() if that fills too, with geometric growth as the fallback. The size is only an allocation hint - reading continues until read() returns 0, so procfs/sysfs and concurrently changing files behave as before and StringBytes::Encode() sees exactly the bytes read. Allocation failure throws ERR_MEMORY_ALLOCATION_FAILED.

Tests:test-fs-readfilesync-utf8-sizes.js (new): equals readFileSync(path).toString('utf8') around every internal boundary (0 … 8 MiB+5) with multi-byte characters straddling chunk edges; by fd from start / at EOF / mid-file; binary input; /proc/self/maps and friends; EISDIR. fs, module and require suites pass.

Disclosure: the code, test, measurements and this description were written by Claude Code, directed and reviewed by @codebytere.

codecov · 2026-08-16T22:09:50Z

Codecov Report

❌ Patch coverage is 78.26087% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.11%. Comparing base (30bff4a) to head (60bf6b9).
⚠️ Report is 149 commits behind head on main.

Files with missing lines	Patch %	Lines
src/node_file.cc	78.26%	2 Missing and 8 partials ⚠️

Additional details and impacted files

@@ Coverage Diff @@## main #65328 +/- ##
==========================================
- Coverage 90.13% 90.11% -0.03% 
==========================================
Files 752 751 -1 Lines 251568 252570 +1002 Branches 47270 47526 +256 ==========================================
+ Hits 226759 227604 +845 - Misses 16168 16247 +79 - Partials 8641 8719 +78

Files with missing lines	Coverage Δ
src/node_file.cc	`74.10% <78.26%> (-0.10%)`	⬇️

... and 121 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

mcollina

lgtm

nodejs-github-bot · 2026-08-21T10:39:01Z

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

nodejs-github-bot · 2026-08-21T14:09:44Z

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

nodejs-github-bot · 2026-08-21T21:03:56Z

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

nodejs-github-bot · 2026-08-22T17:50:43Z

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

fs.readFileSync(path, 'utf8') read the whole file in 8 KiB read() calls appended to a std::string, i.e. one syscall and a potential reallocation per 8 KiB (an 8 MiB file took ~1400 read() calls). Keep the exact old sequence for small files (one read into the 8 KiB stack buffer, one read reporting EOF). Once a read fills the stack buffer, read the rest directly into one heap buffer sized from fstat() (plus one byte so that the EOF read does not force growth), growing geometrically only when the size is unavailable or wrong. The size is only an allocation hint: reading continues until read() reports EOF, so procfs/sysfs files, FIFOs, files that change while being read and file descriptors positioned mid-file behave as before, and the bytes handed to StringBytes::Encode() are exactly the ones read. Signed-off-by: Shelley Vohr <shelley.vohr@gmail.com>

nodejs-github-bot · 2026-08-23T08:02:53Z

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

nodejs-github-bot · 2026-08-23T19:56:57Z

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

nodejs-github-bot · 2026-08-24T07:44:00Z

Landed in 18fb35a

fs.readFileSync(path, 'utf8') read the whole file in 8 KiB read() calls appended to a std::string, i.e. one syscall and a potential reallocation per 8 KiB (an 8 MiB file took ~1400 read() calls). Keep the exact old sequence for small files (one read into the 8 KiB stack buffer, one read reporting EOF). Once a read fills the stack buffer, read the rest directly into one heap buffer sized from fstat() (plus one byte so that the EOF read does not force growth), growing geometrically only when the size is unavailable or wrong. The size is only an allocation hint: reading continues until read() reports EOF, so procfs/sysfs files, FIFOs, files that change while being read and file descriptors positioned mid-file behave as before, and the bytes handed to StringBytes::Encode() are exactly the ones read. Signed-off-by: Shelley Vohr <shelley.vohr@gmail.com> PR-URL: #65328 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>

codebytere · 2026-08-16T15:51:21Z

fs.readFileSync(path, 'utf8') gets +19…42 % on 4 MiB files and +60…231 % on 256 KiB files, with small files untouched, by reading large files into one right-sized buffer instead of 8 KiB at a time.

fs/readfile-utf8-fastpath.js source='path' content='ascii' size=262144 *** 231.14 % ±2.91%
fs/readfile-utf8-fastpath.js source='path' content='utf8_mixed' size=262144 *** 60.16 % ±0.93%
fs/readfile-utf8-fastpath.js source='path' content='ascii' size=4194304 *** 41.86 % ±5.85%
fs/readfile-utf8-fastpath.js source='path' content='utf8_mixed' size=4194304 *** 19.06 % ±2.92%
fs/readfile-utf8-fastpath.js source='fd' * size=4194304 *** +22…27 %
fs/readfile-utf8-fastpath.js * * size≤16384 0…+2 %
fs/readFileSync.js (1 KiB) ~0 % n.s.

(Linux x64, 30 runs. A 300 KB file goes from 39 syscalls to 5.)

ReadFileUtf8 - behind readFileSync(…, 'utf8') and therefore every CommonJS module load - read in 8 KiB read()s, appending each to a std::string. Files that fit the first 8 KiB read behave exactly as before. Once a read fills the stack buffer, the rest goes straight into one heap buffer: a 64 KiB step first (so files up to 64 KiB take the same reads as today and no fstat), then sized from fstat() if that fills too, with geometric growth as the fallback. The size is only an allocation hint - reading continues until read() returns 0, so procfs/sysfs and concurrently changing files behave as before and StringBytes::Encode() sees exactly the bytes read. Allocation failure throws ERR_MEMORY_ALLOCATION_FAILED.

Tests:test-fs-readfilesync-utf8-sizes.js (new): equals readFileSync(path).toString('utf8') around every internal boundary (0 … 8 MiB+5) with multi-byte characters straddling chunk edges; by fd from start / at EOF / mid-file; binary input; /proc/self/maps and friends; EISDIR. fs, module and require suites pass.

Disclosure: the code, test, measurements and this description were written by Claude Code, directed and reviewed by @codebytere.

codecov · 2026-08-16T22:09:50Z

Codecov Report

❌ Patch coverage is 78.26087% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.11%. Comparing base (30bff4a) to head (60bf6b9).
⚠️ Report is 149 commits behind head on main.

Files with missing lines	Patch %	Lines
src/node_file.cc	78.26%	2 Missing and 8 partials ⚠️

Additional details and impacted files

@@ Coverage Diff @@## main #65328 +/- ##
==========================================
- Coverage 90.13% 90.11% -0.03% 
==========================================
Files 752 751 -1 Lines 251568 252570 +1002 Branches 47270 47526 +256 ==========================================
+ Hits 226759 227604 +845 - Misses 16168 16247 +79 - Partials 8641 8719 +78

Files with missing lines	Coverage Δ
src/node_file.cc	`74.10% <78.26%> (-0.10%)`	⬇️

... and 121 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

mcollina

lgtm

nodejs-github-bot · 2026-08-21T10:39:01Z

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

nodejs-github-bot · 2026-08-21T14:09:44Z

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

nodejs-github-bot · 2026-08-21T21:03:56Z

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

nodejs-github-bot · 2026-08-22T17:50:43Z

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

fs.readFileSync(path, 'utf8') read the whole file in 8 KiB read() calls appended to a std::string, i.e. one syscall and a potential reallocation per 8 KiB (an 8 MiB file took ~1400 read() calls). Keep the exact old sequence for small files (one read into the 8 KiB stack buffer, one read reporting EOF). Once a read fills the stack buffer, read the rest directly into one heap buffer sized from fstat() (plus one byte so that the EOF read does not force growth), growing geometrically only when the size is unavailable or wrong. The size is only an allocation hint: reading continues until read() reports EOF, so procfs/sysfs files, FIFOs, files that change while being read and file descriptors positioned mid-file behave as before, and the bytes handed to StringBytes::Encode() are exactly the ones read. Signed-off-by: Shelley Vohr <shelley.vohr@gmail.com>

nodejs-github-bot · 2026-08-23T08:02:53Z

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

nodejs-github-bot · 2026-08-23T19:56:57Z

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

nodejs-github-bot · 2026-08-24T07:44:00Z

Landed in 18fb35a

fs.readFileSync(path, 'utf8') read the whole file in 8 KiB read() calls appended to a std::string, i.e. one syscall and a potential reallocation per 8 KiB (an 8 MiB file took ~1400 read() calls). Keep the exact old sequence for small files (one read into the 8 KiB stack buffer, one read reporting EOF). Once a read fills the stack buffer, read the rest directly into one heap buffer sized from fstat() (plus one byte so that the EOF read does not force growth), growing geometrically only when the size is unavailable or wrong. The size is only an allocation hint: reading continues until read() reports EOF, so procfs/sysfs files, FIFOs, files that change while being read and file descriptors positioned mid-file behave as before, and the bytes handed to StringBytes::Encode() are exactly the ones read. Signed-off-by: Shelley Vohr <shelley.vohr@gmail.com> PR-URL: #65328 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>

codebytere · 2026-08-16T15:51:21Z

fs.readFileSync(path, 'utf8') gets +19…42 % on 4 MiB files and +60…231 % on 256 KiB files, with small files untouched, by reading large files into one right-sized buffer instead of 8 KiB at a time.

fs/readfile-utf8-fastpath.js source='path' content='ascii' size=262144 *** 231.14 % ±2.91%
fs/readfile-utf8-fastpath.js source='path' content='utf8_mixed' size=262144 *** 60.16 % ±0.93%
fs/readfile-utf8-fastpath.js source='path' content='ascii' size=4194304 *** 41.86 % ±5.85%
fs/readfile-utf8-fastpath.js source='path' content='utf8_mixed' size=4194304 *** 19.06 % ±2.92%
fs/readfile-utf8-fastpath.js source='fd' * size=4194304 *** +22…27 %
fs/readfile-utf8-fastpath.js * * size≤16384 0…+2 %
fs/readFileSync.js (1 KiB) ~0 % n.s.

(Linux x64, 30 runs. A 300 KB file goes from 39 syscalls to 5.)

ReadFileUtf8 - behind readFileSync(…, 'utf8') and therefore every CommonJS module load - read in 8 KiB read()s, appending each to a std::string. Files that fit the first 8 KiB read behave exactly as before. Once a read fills the stack buffer, the rest goes straight into one heap buffer: a 64 KiB step first (so files up to 64 KiB take the same reads as today and no fstat), then sized from fstat() if that fills too, with geometric growth as the fallback. The size is only an allocation hint - reading continues until read() returns 0, so procfs/sysfs and concurrently changing files behave as before and StringBytes::Encode() sees exactly the bytes read. Allocation failure throws ERR_MEMORY_ALLOCATION_FAILED.

Tests:test-fs-readfilesync-utf8-sizes.js (new): equals readFileSync(path).toString('utf8') around every internal boundary (0 … 8 MiB+5) with multi-byte characters straddling chunk edges; by fd from start / at EOF / mid-file; binary input; /proc/self/maps and friends; EISDIR. fs, module and require suites pass.

Disclosure: the code, test, measurements and this description were written by Claude Code, directed and reviewed by @codebytere.

codecov · 2026-08-16T22:09:50Z

Codecov Report

❌ Patch coverage is 78.26087% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.11%. Comparing base (30bff4a) to head (60bf6b9).
⚠️ Report is 149 commits behind head on main.

Files with missing lines	Patch %	Lines
src/node_file.cc	78.26%	2 Missing and 8 partials ⚠️

Additional details and impacted files

@@ Coverage Diff @@## main #65328 +/- ##
==========================================
- Coverage 90.13% 90.11% -0.03% 
==========================================
Files 752 751 -1 Lines 251568 252570 +1002 Branches 47270 47526 +256 ==========================================
+ Hits 226759 227604 +845 - Misses 16168 16247 +79 - Partials 8641 8719 +78

Files with missing lines	Coverage Δ
src/node_file.cc	`74.10% <78.26%> (-0.10%)`	⬇️

... and 121 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

mcollina

lgtm

nodejs-github-bot · 2026-08-21T10:39:01Z

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

nodejs-github-bot · 2026-08-21T14:09:44Z

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

nodejs-github-bot · 2026-08-21T21:03:56Z

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

nodejs-github-bot · 2026-08-22T17:50:43Z

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

fs.readFileSync(path, 'utf8') read the whole file in 8 KiB read() calls appended to a std::string, i.e. one syscall and a potential reallocation per 8 KiB (an 8 MiB file took ~1400 read() calls). Keep the exact old sequence for small files (one read into the 8 KiB stack buffer, one read reporting EOF). Once a read fills the stack buffer, read the rest directly into one heap buffer sized from fstat() (plus one byte so that the EOF read does not force growth), growing geometrically only when the size is unavailable or wrong. The size is only an allocation hint: reading continues until read() reports EOF, so procfs/sysfs files, FIFOs, files that change while being read and file descriptors positioned mid-file behave as before, and the bytes handed to StringBytes::Encode() are exactly the ones read. Signed-off-by: Shelley Vohr <shelley.vohr@gmail.com>

nodejs-github-bot · 2026-08-23T08:02:53Z

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

nodejs-github-bot · 2026-08-23T19:56:57Z

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

nodejs-github-bot · 2026-08-24T07:44:00Z

Landed in 18fb35a

fs.readFileSync(path, 'utf8') read the whole file in 8 KiB read() calls appended to a std::string, i.e. one syscall and a potential reallocation per 8 KiB (an 8 MiB file took ~1400 read() calls). Keep the exact old sequence for small files (one read into the 8 KiB stack buffer, one read reporting EOF). Once a read fills the stack buffer, read the rest directly into one heap buffer sized from fstat() (plus one byte so that the EOF read does not force growth), growing geometrically only when the size is unavailable or wrong. The size is only an allocation hint: reading continues until read() reports EOF, so procfs/sysfs files, FIFOs, files that change while being read and file descriptors positioned mid-file behave as before, and the bytes handed to StringBytes::Encode() are exactly the ones read. Signed-off-by: Shelley Vohr <shelley.vohr@gmail.com> PR-URL: #65328 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>

codebytere · 2026-08-16T15:51:21Z

fs.readFileSync(path, 'utf8') gets +19…42 % on 4 MiB files and +60…231 % on 256 KiB files, with small files untouched, by reading large files into one right-sized buffer instead of 8 KiB at a time.

fs/readfile-utf8-fastpath.js source='path' content='ascii' size=262144 *** 231.14 % ±2.91%
fs/readfile-utf8-fastpath.js source='path' content='utf8_mixed' size=262144 *** 60.16 % ±0.93%
fs/readfile-utf8-fastpath.js source='path' content='ascii' size=4194304 *** 41.86 % ±5.85%
fs/readfile-utf8-fastpath.js source='path' content='utf8_mixed' size=4194304 *** 19.06 % ±2.92%
fs/readfile-utf8-fastpath.js source='fd' * size=4194304 *** +22…27 %
fs/readfile-utf8-fastpath.js * * size≤16384 0…+2 %
fs/readFileSync.js (1 KiB) ~0 % n.s.

(Linux x64, 30 runs. A 300 KB file goes from 39 syscalls to 5.)

ReadFileUtf8 - behind readFileSync(…, 'utf8') and therefore every CommonJS module load - read in 8 KiB read()s, appending each to a std::string. Files that fit the first 8 KiB read behave exactly as before. Once a read fills the stack buffer, the rest goes straight into one heap buffer: a 64 KiB step first (so files up to 64 KiB take the same reads as today and no fstat), then sized from fstat() if that fills too, with geometric growth as the fallback. The size is only an allocation hint - reading continues until read() returns 0, so procfs/sysfs and concurrently changing files behave as before and StringBytes::Encode() sees exactly the bytes read. Allocation failure throws ERR_MEMORY_ALLOCATION_FAILED.

Tests:test-fs-readfilesync-utf8-sizes.js (new): equals readFileSync(path).toString('utf8') around every internal boundary (0 … 8 MiB+5) with multi-byte characters straddling chunk edges; by fd from start / at EOF / mid-file; binary input; /proc/self/maps and friends; EISDIR. fs, module and require suites pass.

Disclosure: the code, test, measurements and this description were written by Claude Code, directed and reviewed by @codebytere.

codecov · 2026-08-16T22:09:50Z

Codecov Report

❌ Patch coverage is 78.26087% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.11%. Comparing base (30bff4a) to head (60bf6b9).
⚠️ Report is 149 commits behind head on main.

Files with missing lines	Patch %	Lines
src/node_file.cc	78.26%	2 Missing and 8 partials ⚠️

Additional details and impacted files

@@ Coverage Diff @@## main #65328 +/- ##
==========================================
- Coverage 90.13% 90.11% -0.03% 
==========================================
Files 752 751 -1 Lines 251568 252570 +1002 Branches 47270 47526 +256 ==========================================
+ Hits 226759 227604 +845 - Misses 16168 16247 +79 - Partials 8641 8719 +78

Files with missing lines	Coverage Δ
src/node_file.cc	`74.10% <78.26%> (-0.10%)`	⬇️

... and 121 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

mcollina

lgtm

nodejs-github-bot · 2026-08-21T10:39:01Z

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

nodejs-github-bot · 2026-08-21T14:09:44Z

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

nodejs-github-bot · 2026-08-21T21:03:56Z

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

nodejs-github-bot · 2026-08-22T17:50:43Z

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

fs.readFileSync(path, 'utf8') read the whole file in 8 KiB read() calls appended to a std::string, i.e. one syscall and a potential reallocation per 8 KiB (an 8 MiB file took ~1400 read() calls). Keep the exact old sequence for small files (one read into the 8 KiB stack buffer, one read reporting EOF). Once a read fills the stack buffer, read the rest directly into one heap buffer sized from fstat() (plus one byte so that the EOF read does not force growth), growing geometrically only when the size is unavailable or wrong. The size is only an allocation hint: reading continues until read() reports EOF, so procfs/sysfs files, FIFOs, files that change while being read and file descriptors positioned mid-file behave as before, and the bytes handed to StringBytes::Encode() are exactly the ones read. Signed-off-by: Shelley Vohr <shelley.vohr@gmail.com>

nodejs-github-bot · 2026-08-23T08:02:53Z

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

nodejs-github-bot · 2026-08-23T19:56:57Z

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

nodejs-github-bot · 2026-08-24T07:44:00Z

Landed in 18fb35a

fs.readFileSync(path, 'utf8') read the whole file in 8 KiB read() calls appended to a std::string, i.e. one syscall and a potential reallocation per 8 KiB (an 8 MiB file took ~1400 read() calls). Keep the exact old sequence for small files (one read into the 8 KiB stack buffer, one read reporting EOF). Once a read fills the stack buffer, read the rest directly into one heap buffer sized from fstat() (plus one byte so that the EOF read does not force growth), growing geometrically only when the size is unavailable or wrong. The size is only an allocation hint: reading continues until read() reports EOF, so procfs/sysfs files, FIFOs, files that change while being read and file descriptors positioned mid-file behave as before, and the bytes handed to StringBytes::Encode() are exactly the ones read. Signed-off-by: Shelley Vohr <shelley.vohr@gmail.com> PR-URL: #65328 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>

codebytere · 2026-08-16T15:51:21Z

fs.readFileSync(path, 'utf8') gets +19…42 % on 4 MiB files and +60…231 % on 256 KiB files, with small files untouched, by reading large files into one right-sized buffer instead of 8 KiB at a time.

fs/readfile-utf8-fastpath.js source='path' content='ascii' size=262144 *** 231.14 % ±2.91%
fs/readfile-utf8-fastpath.js source='path' content='utf8_mixed' size=262144 *** 60.16 % ±0.93%
fs/readfile-utf8-fastpath.js source='path' content='ascii' size=4194304 *** 41.86 % ±5.85%
fs/readfile-utf8-fastpath.js source='path' content='utf8_mixed' size=4194304 *** 19.06 % ±2.92%
fs/readfile-utf8-fastpath.js source='fd' * size=4194304 *** +22…27 %
fs/readfile-utf8-fastpath.js * * size≤16384 0…+2 %
fs/readFileSync.js (1 KiB) ~0 % n.s.

(Linux x64, 30 runs. A 300 KB file goes from 39 syscalls to 5.)

ReadFileUtf8 - behind readFileSync(…, 'utf8') and therefore every CommonJS module load - read in 8 KiB read()s, appending each to a std::string. Files that fit the first 8 KiB read behave exactly as before. Once a read fills the stack buffer, the rest goes straight into one heap buffer: a 64 KiB step first (so files up to 64 KiB take the same reads as today and no fstat), then sized from fstat() if that fills too, with geometric growth as the fallback. The size is only an allocation hint - reading continues until read() returns 0, so procfs/sysfs and concurrently changing files behave as before and StringBytes::Encode() sees exactly the bytes read. Allocation failure throws ERR_MEMORY_ALLOCATION_FAILED.

Tests:test-fs-readfilesync-utf8-sizes.js (new): equals readFileSync(path).toString('utf8') around every internal boundary (0 … 8 MiB+5) with multi-byte characters straddling chunk edges; by fd from start / at EOF / mid-file; binary input; /proc/self/maps and friends; EISDIR. fs, module and require suites pass.

Disclosure: the code, test, measurements and this description were written by Claude Code, directed and reviewed by @codebytere.

codecov · 2026-08-16T22:09:50Z

Codecov Report

❌ Patch coverage is 78.26087% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.11%. Comparing base (30bff4a) to head (60bf6b9).
⚠️ Report is 149 commits behind head on main.

Files with missing lines	Patch %	Lines
src/node_file.cc	78.26%	2 Missing and 8 partials ⚠️

Additional details and impacted files

@@ Coverage Diff @@## main #65328 +/- ##
==========================================
- Coverage 90.13% 90.11% -0.03% 
==========================================
Files 752 751 -1 Lines 251568 252570 +1002 Branches 47270 47526 +256 ==========================================
+ Hits 226759 227604 +845 - Misses 16168 16247 +79 - Partials 8641 8719 +78

Files with missing lines	Coverage Δ
src/node_file.cc	`74.10% <78.26%> (-0.10%)`	⬇️

... and 121 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

mcollina

lgtm

nodejs-github-bot · 2026-08-21T10:39:01Z

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

nodejs-github-bot · 2026-08-21T14:09:44Z

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

nodejs-github-bot · 2026-08-21T21:03:56Z

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

nodejs-github-bot · 2026-08-22T17:50:43Z

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

fs.readFileSync(path, 'utf8') read the whole file in 8 KiB read() calls appended to a std::string, i.e. one syscall and a potential reallocation per 8 KiB (an 8 MiB file took ~1400 read() calls). Keep the exact old sequence for small files (one read into the 8 KiB stack buffer, one read reporting EOF). Once a read fills the stack buffer, read the rest directly into one heap buffer sized from fstat() (plus one byte so that the EOF read does not force growth), growing geometrically only when the size is unavailable or wrong. The size is only an allocation hint: reading continues until read() reports EOF, so procfs/sysfs files, FIFOs, files that change while being read and file descriptors positioned mid-file behave as before, and the bytes handed to StringBytes::Encode() are exactly the ones read. Signed-off-by: Shelley Vohr <shelley.vohr@gmail.com>

nodejs-github-bot · 2026-08-23T08:02:53Z

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

nodejs-github-bot · 2026-08-23T19:56:57Z

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

nodejs-github-bot · 2026-08-24T07:44:00Z

Landed in 18fb35a

fs.readFileSync(path, 'utf8') read the whole file in 8 KiB read() calls appended to a std::string, i.e. one syscall and a potential reallocation per 8 KiB (an 8 MiB file took ~1400 read() calls). Keep the exact old sequence for small files (one read into the 8 KiB stack buffer, one read reporting EOF). Once a read fills the stack buffer, read the rest directly into one heap buffer sized from fstat() (plus one byte so that the EOF read does not force growth), growing geometrically only when the size is unavailable or wrong. The size is only an allocation hint: reading continues until read() reports EOF, so procfs/sysfs files, FIFOs, files that change while being read and file descriptors positioned mid-file behave as before, and the bytes handed to StringBytes::Encode() are exactly the ones read. Signed-off-by: Shelley Vohr <shelley.vohr@gmail.com> PR-URL: #65328 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>

codebytere · 2026-08-16T15:51:21Z

fs.readFileSync(path, 'utf8') gets +19…42 % on 4 MiB files and +60…231 % on 256 KiB files, with small files untouched, by reading large files into one right-sized buffer instead of 8 KiB at a time.

fs/readfile-utf8-fastpath.js source='path' content='ascii' size=262144 *** 231.14 % ±2.91%
fs/readfile-utf8-fastpath.js source='path' content='utf8_mixed' size=262144 *** 60.16 % ±0.93%
fs/readfile-utf8-fastpath.js source='path' content='ascii' size=4194304 *** 41.86 % ±5.85%
fs/readfile-utf8-fastpath.js source='path' content='utf8_mixed' size=4194304 *** 19.06 % ±2.92%
fs/readfile-utf8-fastpath.js source='fd' * size=4194304 *** +22…27 %
fs/readfile-utf8-fastpath.js * * size≤16384 0…+2 %
fs/readFileSync.js (1 KiB) ~0 % n.s.

(Linux x64, 30 runs. A 300 KB file goes from 39 syscalls to 5.)

ReadFileUtf8 - behind readFileSync(…, 'utf8') and therefore every CommonJS module load - read in 8 KiB read()s, appending each to a std::string. Files that fit the first 8 KiB read behave exactly as before. Once a read fills the stack buffer, the rest goes straight into one heap buffer: a 64 KiB step first (so files up to 64 KiB take the same reads as today and no fstat), then sized from fstat() if that fills too, with geometric growth as the fallback. The size is only an allocation hint - reading continues until read() returns 0, so procfs/sysfs and concurrently changing files behave as before and StringBytes::Encode() sees exactly the bytes read. Allocation failure throws ERR_MEMORY_ALLOCATION_FAILED.

Tests:test-fs-readfilesync-utf8-sizes.js (new): equals readFileSync(path).toString('utf8') around every internal boundary (0 … 8 MiB+5) with multi-byte characters straddling chunk edges; by fd from start / at EOF / mid-file; binary input; /proc/self/maps and friends; EISDIR. fs, module and require suites pass.

Disclosure: the code, test, measurements and this description were written by Claude Code, directed and reviewed by @codebytere.

codecov · 2026-08-16T22:09:50Z

Codecov Report

❌ Patch coverage is 78.26087% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.11%. Comparing base (30bff4a) to head (60bf6b9).
⚠️ Report is 149 commits behind head on main.

Files with missing lines	Patch %	Lines
src/node_file.cc	78.26%	2 Missing and 8 partials ⚠️

Additional details and impacted files

@@ Coverage Diff @@## main #65328 +/- ##
==========================================
- Coverage 90.13% 90.11% -0.03% 
==========================================
Files 752 751 -1 Lines 251568 252570 +1002 Branches 47270 47526 +256 ==========================================
+ Hits 226759 227604 +845 - Misses 16168 16247 +79 - Partials 8641 8719 +78

Files with missing lines	Coverage Δ
src/node_file.cc	`74.10% <78.26%> (-0.10%)`	⬇️

... and 121 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

mcollina

lgtm

nodejs-github-bot · 2026-08-21T10:39:01Z

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

nodejs-github-bot · 2026-08-21T14:09:44Z

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

nodejs-github-bot · 2026-08-21T21:03:56Z

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

nodejs-github-bot · 2026-08-22T17:50:43Z

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

fs.readFileSync(path, 'utf8') read the whole file in 8 KiB read() calls appended to a std::string, i.e. one syscall and a potential reallocation per 8 KiB (an 8 MiB file took ~1400 read() calls). Keep the exact old sequence for small files (one read into the 8 KiB stack buffer, one read reporting EOF). Once a read fills the stack buffer, read the rest directly into one heap buffer sized from fstat() (plus one byte so that the EOF read does not force growth), growing geometrically only when the size is unavailable or wrong. The size is only an allocation hint: reading continues until read() reports EOF, so procfs/sysfs files, FIFOs, files that change while being read and file descriptors positioned mid-file behave as before, and the bytes handed to StringBytes::Encode() are exactly the ones read. Signed-off-by: Shelley Vohr <shelley.vohr@gmail.com>

nodejs-github-bot · 2026-08-23T08:02:53Z

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

nodejs-github-bot · 2026-08-23T19:56:57Z

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

nodejs-github-bot · 2026-08-24T07:44:00Z

Landed in 18fb35a

fs.readFileSync(path, 'utf8') read the whole file in 8 KiB read() calls appended to a std::string, i.e. one syscall and a potential reallocation per 8 KiB (an 8 MiB file took ~1400 read() calls). Keep the exact old sequence for small files (one read into the 8 KiB stack buffer, one read reporting EOF). Once a read fills the stack buffer, read the rest directly into one heap buffer sized from fstat() (plus one byte so that the EOF read does not force growth), growing geometrically only when the size is unavailable or wrong. The size is only an allocation hint: reading continues until read() reports EOF, so procfs/sysfs files, FIFOs, files that change while being read and file descriptors positioned mid-file behave as before, and the bytes handed to StringBytes::Encode() are exactly the ones read. Signed-off-by: Shelley Vohr <shelley.vohr@gmail.com> PR-URL: #65328 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>

nodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. fs Issues and PRs related to file-system APIs and the fs module. needs-ci PRs that need a full CI run. labels Aug 16, 2026

codebytere force-pushed the perf/fs-readfile-utf8-sized-reads branch 2 times, most recently from 39c515d to ff70ea5Compare August 16, 2026 20:30

codebytere requested review from RafaelGSS and jasnell August 17, 2026 05:44

codebytere added request-ci Add this label to start a Jenkins CI on a PR. and removed needs-ci PRs that need a full CI run. labels Aug 17, 2026

codebytere requested a review from aduh95 August 17, 2026 10:31

codebytere added the needs-ci PRs that need a full CI run. label Aug 17, 2026

codebytere requested review from anonrig and avivkeller and removed request for RafaelGSS August 19, 2026 08:55

mcollina reviewed Aug 20, 2026
View reviewed changes

Comment threadsrc/node_file.cc Outdated

codebytere force-pushed the perf/fs-readfile-utf8-sized-reads branch from ff70ea5 to d47ea46Compare August 20, 2026 17:18

mcollina approved these changes Aug 21, 2026
View reviewed changes

mcollina added request-ci Add this label to start a Jenkins CI on a PR. and removed request-ci Add this label to start a Jenkins CI on a PR. labels Aug 21, 2026

github-actionsBot removed the request-ci Add this label to start a Jenkins CI on a PR. label Aug 21, 2026

codebytere added the request-ci Add this label to start a Jenkins CI on a PR. label Aug 21, 2026

github-actionsBot removed the request-ci Add this label to start a Jenkins CI on a PR. label Aug 21, 2026

codebytere force-pushed the perf/fs-readfile-utf8-sized-reads branch from d47ea46 to f6970e8Compare August 22, 2026 14:46

codebytere force-pushed the perf/fs-readfile-utf8-sized-reads branch from f6970e8 to 60bf6b9Compare August 22, 2026 18:39

anonrig approved these changes Aug 22, 2026
View reviewed changes

codebytere added commit-queue PRs queued for automated landing through the Commit Queue. and removed needs-ci PRs that need a full CI run. labels Aug 24, 2026

nodejs-github-bot merged commit 18fb35a into nodejs:mainAug 24, 2026
68 checks passed

nodejs-github-bot removed the commit-queue PRs queued for automated landing through the Commit Queue. label Aug 24, 2026

github-actionsBot mentioned this pull request Aug 25, 2026
2026-08-26, Version 26.8.0 (Current) #65551
Merged

panva mentioned this pull request Aug 26, 2026
RuntimeError: unreachable #64226
Open

sxa mentioned this pull request Aug 26, 2026
test: deflake fastutf8stream destroy and reopen tests #65554
Merged