From 51d20b6a8f695947a700e7fed8f0e5b33b79cefb Mon Sep 17 00:00:00 2001 From: Richard Lau Date: Tue, 12 Feb 2019 15:39:10 +0000 Subject: fs, src, lib: fix `blksize` & `blocks` on Windows libuv returns values for `blksize` and `blocks` on stat calls so do not coerce them into `undefined` on Windows. PR-URL: https://github.com/nodejs/node/pull/26056 Fixes: https://github.com/nodejs/node/issues/25913 Reviewed-By: Ben Noordhuis Reviewed-By: Colin Ihrig Reviewed-By: Anna Henningsen Reviewed-By: Joyee Cheung Reviewed-By: James M Snell --- doc/api/fs.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'doc/api/fs.md') diff --git a/doc/api/fs.md b/doc/api/fs.md index 53a504f3ec..ea983a8c1c 100644 --- a/doc/api/fs.md +++ b/doc/api/fs.md @@ -3427,8 +3427,7 @@ to compare `curr.mtime` and `prev.mtime`. When an `fs.watchFile` operation results in an `ENOENT` error, it will invoke the listener once, with all the fields zeroed (or, for dates, the -Unix Epoch). In Windows, `blksize` and `blocks` fields will be `undefined`, -instead of zero. If the file is created later on, the listener will be called +Unix Epoch). If the file is created later on, the listener will be called again, with the latest stat objects. This is a change in functionality since v0.10. -- cgit v1.2.3