Skip to content

Support providing AbortSignal to the fs.stat functions #57751

Description

@Nokel81

What is the problem this feature will solve?

Currently fs.stat does not support providing an AbortSignal to fail-fast during teardown, unlike basically all other fs operations

What is the feature you are proposing to solve the problem?

That the StatOptions object have a new field signal?: AbortSignal and when that signal emits an "abort" event the underlying OS FS actions is aborted an the callback parameter of stat is called with an AbortError and undefined.

Futhermore, the async version of stat would also support this option but instead would reject the promise with an AbortError.

What alternatives have you considered?

None, this needs to be implemented within the VM

Activity

  1. github-actions commented on Oct 2, 2025

    @github-actions
    Contributor

    There has been no activity on this feature request for 5 months. To help maintain relevant open issues, please add the never-stale Issues and PRs exempt from automated stale handling. label or close this issue if it should be closed. If not, the issue will be automatically closed 6 months after the last non-automated comment.
    For more information on how the project manages feature requests, please consult the feature request management document.

  2. added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Oct 2, 2025
  3. Nokel81 commented on Oct 2, 2025

    @Nokel81
    Author

    This is still relevant and a pr seems to have been opened

  4. removed
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Oct 3, 2025
  5. github-actions commented on Apr 1, 2026

    @github-actions
    Contributor

    There has been no activity on this feature request for 5 months. To help maintain relevant open issues, please add the never-stale Issues and PRs exempt from automated stale handling. label or close this issue if it should be closed. If not, the issue will be automatically closed 6 months after the last non-automated comment.
    For more information on how the project manages feature requests, please consult the feature request management document.

  6. added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Apr 1, 2026
  7. Nokel81 commented on Apr 1, 2026

    @Nokel81
    Author

    This is still relevant and a pr seems to have been opened

  8. removed
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Apr 2, 2026
  9. trivikr commented on Jul 16, 2026

    @trivikr
    Member

    This should be fixed by #63142

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

    feature requestIssues requesting new Node.js features.

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions