Request for Node.js Position on an Emerging Specification

• Specification title: Observable API
• Specification or proposal URL (if available): https://wicg.github.io/observable/
• Explainer URL (if available): https://github.com/WICG/observable/blob/master/README.md
• Proposal author(s) (@-mention GitHub accounts): @domfarolino, @benlesh
• Node.js collaborators or ecosystem members who can provide input (optional): ?

Notes

The Observable API is a primitive with long history, providing declarative ergonomics for streams of async events. At an extremely high level, they are "Promises for multiple events, but with no built-in async scheduling". The Observable API is a long-awaited and highly-desired feature on the web platform.

The reason we're coming to Node.js (and WinterCG more broadly) is because these environments implement similar DOM APIs that integrate strongly with Observables, such as EventTarget and AbortController/AbortSignal. This is a natural primitive to sit alongside those ones, hence the outreach we're performing here. Please let me know if you have any questions, and see WICG/observable#93 for a list of all standards positions issues that we've filed for the Observable API.