镜像站点 · 本页由第三方 GitHub 只读镜像提供，非 GitHub 官方站点，不接受任何登录或凭据输入。前往 github.com
Skip to content

Major discrepancy in FS constants between the docs and distribution #41590

Closed as not planned
Closed as not planned
Major discrepancy in FS constants between the docs and distribution#41590
Labels
docIssues and PRs related to Node.js documentation.fsIssues and PRs related to file-system APIs and the fs module.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

Description

@dead-claudia
dead-claudia
opened on Jan 19, 2022

Version

v16.13.2

Platform

Microsoft Windows NT 10.0.19043.0 x64

Subsystem

fs

Ref: https://nodejs.org/docs/latest-v16.x/api/fs.html#file-access-constants

What steps will reproduce the bug?

Run the following script:

const {constants} = require("fs")

for (const k of Object.keys(constants).sort()) {
    const v = constants[k]
    if (v != null && typeof v !== "function" && typeof v !== "object") {
        console.log(k)
    }
}

How often does it reproduce? Is there a required condition?

100% of the time

What is the expected behavior?

The following modulo whatever legacy constants there are.

COPYFILE_EXCL
COPYFILE_FICLONE_FORCE
COPYFILE_FICLONE
F_OK
O_APPEND
O_CREAT
O_DIRECT
O_DIRECTORY
O_DSYNC
O_EXCL
O_NOATIME
O_NOCTTY
O_NOFOLLOW
O_NONBLOCK
O_RDONLY
O_RDWR
O_SYMLINK
O_SYNC
O_TRUNC
O_WRONLY
R_OK
S_IFBLK
S_IFCHR
S_IFDIR
S_IFIFO
S_IFLNK
S_IFMT
S_IFREG
S_IFSOCK
S_IRGRP
S_IROTH
S_IRUSR
S_IRWXG
S_IRWXO
S_IRWXU
S_IWGRP
S_IWOTH
S_IWUSR
S_IXGRP
S_IXOTH
S_IXUSR
UV_FS_O_FILEMAP
W_OK
X_OK

What do you see instead?

COPYFILE_EXCL
COPYFILE_FICLONE
COPYFILE_FICLONE_FORCE
F_OK
O_APPEND
O_CREAT
O_EXCL
O_RDONLY
O_RDWR
O_TRUNC
O_WRONLY
R_OK
S_IFCHR
S_IFDIR
S_IFLNK
S_IFMT
S_IFREG
UV_DIRENT_BLOCK
UV_DIRENT_CHAR
UV_DIRENT_DIR
UV_DIRENT_FIFO
UV_DIRENT_FILE
UV_DIRENT_LINK
UV_DIRENT_SOCKET
UV_DIRENT_UNKNOWN
UV_FS_COPYFILE_EXCL
UV_FS_COPYFILE_FICLONE
UV_FS_COPYFILE_FICLONE_FORCE
UV_FS_O_FILEMAP
UV_FS_SYMLINK_DIR
UV_FS_SYMLINK_JUNCTION
W_OK
X_OK

Additional information

This represents the following diff (hand-written):

---distribution
+++docs
 COPYFILE_EXCL
 COPYFILE_FICLONE
 COPYFILE_FICLONE_FORCE
 F_OK
 O_APPEND
 O_CREAT
+O_DIRECT
+O_DIRECTORY
+O_DSYNC
 O_EXCL
+O_NOATIME
+O_NOCTTY
+O_NOFOLLOW
+O_NONBLOCK
 O_RDONLY
 O_RDWR
+O_SYMLINK
+O_SYNC
 O_TRUNC
 O_WRONLY
 R_OK
+S_IFBLK
 S_IFCHR
 S_IFDIR
+S_IFIFO
 S_IFLNK
 S_IFMT
 S_IFREG
+S_IFSOCK
+S_IRGRP
+S_IROTH
+S_IRUSR
+S_IRWXG
+S_IRWXO
+S_IRWXU
+S_IWGRP
+S_IWOTH
+S_IWUSR
+S_IXGRP
+S_IXOTH
+S_IXUSR
-UV_DIRENT_BLOCK
-UV_DIRENT_CHAR
-UV_DIRENT_DIR
-UV_DIRENT_FIFO
-UV_DIRENT_FILE
-UV_DIRENT_LINK
-UV_DIRENT_SOCKET
-UV_DIRENT_UNKNOWN
-UV_FS_COPYFILE_EXCL
-UV_FS_COPYFILE_FICLONE
-UV_FS_COPYFILE_FICLONE_FORCE
+UV_FS_O_FILEMAP
-UV_FS_SYMLINK_DIR
-UV_FS_SYMLINK_JUNCTION
 W_OK
 X_OK

Activity

  1. targos commented on Jan 19, 2022

    @targos
    targos
    on Jan 19, 2022
    Member

    The documentation says:

    Not every constant will be available on every operating system.

    This explains why some constants are in the documentation but not available on Windows.

    The red lines in your diff are probably additions that we forgot to document.

  2. targos
    added
    docIssues and PRs related to Node.js documentation.
    fsIssues and PRs related to file-system APIs and the fs module.
    on Jan 19, 2022

  3. dead-claudia commented on Jan 19, 2022

    @dead-claudia
    dead-claudia
    on Jan 19, 2022
    Author

    Not every constant will be available on every operating system.

    Okay, I missed that bit. I'll log a separate feature request for that so the docs are easier to follow in that area.

  4. github-actions commented on Jun 25, 2026

    @github-actions
    github-actionsbot
    on Jun 25, 2026 – with GitHub Actions
    Contributor

    This issue has been marked as stale due to 210 days of inactivity.
    It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.

  5. github-actions
    added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Jun 25, 2026

  6. github-actions commented on Jul 26, 2026

    @github-actions
    github-actionsbot
    on Jul 26, 2026 – with GitHub Actions
    Contributor

    This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
    If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.

  7. github-actions
    closed this as not plannedon Jul 26, 2026
  8. Akagilnc
    added a commit that references this issue on Aug 22, 2026

    ak-roles: PR #418 三条 CodeRabbit finding 修复——lease 清理真因落痕、O_NOFOLLOW 缺…

    748497f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    docIssues and PRs related to Node.js documentation.fsIssues and PRs related to file-system APIs and the fs module.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions