Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit bd0e0d2

Browse filesBrowse files
jasnellMylesBorins
authored andcommitted
doc: document ACL limitation for fs.access on Windows
Fixes: #19192 PR-URL: #23772 Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Bartosz Sosnowski <bartosz@janeasystems.com>
1 parent 64f9a3c commit bd0e0d2
Copy full SHA for bd0e0d2

File tree

Expand file treeCollapse file tree

1 file changed

+5
-0
lines changed
Open diff view settings
Filter options
Expand file treeCollapse file tree

1 file changed

+5
-0
lines changed
Open diff view settings
Collapse file

‎doc/api/fs.md‎

Copy file name to clipboardExpand all lines: doc/api/fs.md
+5Lines changed: 5 additions & 0 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -980,6 +980,11 @@ In general, check for the accessibility of a file only if the file will not be
980980
used directly, for example when its accessibility is a signal from another
981981
process.
982982

983+
On Windows, access-control policies (ACLs) on a directory may limit access to
984+
a file or directory. The `fs.access()` function, however, does not check the
985+
ACL and therefore may report that a path is accessible even if the ACL restricts
986+
the user from reading or writing to it.
987+
983988
## fs.accessSync(path[, mode])
984989
<!-- YAML
985990
added: v0.11.15

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.