The future of the Scheduler API
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the early Scheduler API work in issue #40909 and review the current Node.js API surface against postTask() and yield(). The issue is complete when maintainers clarify whether Node intends to advance this API and identify the next steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100