Skip to content

The future of the Scheduler API #59596

Open
Open
The future of the Scheduler API#59596
Labels
never-staleIssues and PRs exempt from automated stale handling.

Description

@Renegade334
Renegade334
opened on Aug 23, 2025

The early work on the Scheduler API (#40909) essentially hasn't been touched in the last few years.

In that time, the WG appears to have settled on postTask() and yield() as its foreseeable interface. Firefox provides this out-of-the-box as of last week, and Chromium have settled on this for some time (albeit with yield() still flagged).

Is the API still something intended to be taken forward in Node?

cc: @jasnell

Activity

  1. jasnell commented on Aug 23, 2025

    @jasnell
    jasnell
    on Aug 23, 2025
    Member

    Yep, just been waiting the browsers/specs to progress.

  2. github-actions commented on Apr 19, 2026

    @github-actions
    github-actionsbot
    on Apr 19, 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.

  3. github-actions
    added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Apr 19, 2026
  4. jasnell
    added
    never-staleIssues and PRs exempt from automated stale handling.
    and removed
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Apr 19, 2026
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

    never-staleIssues and PRs exempt from automated stale handling.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions