From 36f16e7ebad58af16715b2d7dd2acdb07c407e8a Mon Sep 17 00:00:00 2001 From: Trivikram Kamat <16024985+trivikr@users.noreply.github.com> Date: Tue, 8 Sep 2026 18:34:28 -0700 Subject: [PATCH] doc: qualify directory read ordering for native fs Clarify that the documented operating system directory ordering applies to reads handled by the native file system. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com> PR-URL: https://github.com/nodejs/node/pull/65868 Reviewed-By: James M Snell Reviewed-By: Luigi Pinca --- doc/api/fs.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/api/fs.md b/doc/api/fs.md index 03e9b8be5e9..4d15a82e4a0 100644 --- a/doc/api/fs.md +++ b/doc/api/fs.md @@ -7358,8 +7358,9 @@ Asynchronously read the next directory entry via readdir(3) as an A promise is returned that will be fulfilled with an {fs.Dirent}, or `null` if there are no more directory entries to read. -Directory entries returned by this function are in no particular order as -provided by the operating system's underlying directory mechanisms. +For directory reads handled by the native file system, directory entries +returned by this function are in no particular order as provided by the +operating system's underlying directory mechanisms. Entries added or removed while iterating over the directory might not be included in the iteration results.