Towards a stdlib for JavaScript Runtimes
summary
Proposal defines a common minimum API drawn from browser Web Platform APIs and targeted at Node, Deno, Cloudflare Workers and others, with a rule that any API present in two runtimes gets listed. Work uses existing specs, Web Platform Tests and the W3C/WICG process; examples already landed: URL class, AbortController, fetch and response.json; web streams are implemented but required rewriting after failing conformance; webstream spec is implemented webstream spec three times in nine months. A draft note records variances and migration guidance.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 3:09Problem with multiple runtimes
- 7:01Web standards adoption in Node
- 10:30Acceptance of web standards
- 12:40Challenges with web streams
- 16:29Founding WinterCG
- 20:20Proposing new APIs
- 22:49Common minimum API surface
- 25:17Purpose of WinterCG
related talks
40mIt's Not Just Node.js Anymore
25mNext-Gen Server JavaScript: Web Standards
30mAdvancing Web Runtime Interoperability with WinterCG: Empowering the Future of the..
24mWeb APIs in Node.js Core: Past, Present, and Future
07mBuilding a Node js runtime for the browser
19mKeynote: The Future of JavaScript is Universal
50mProposals in this day & age, taking steps to the next stage
22mBun, Deno, Node.js? Recreating a JavaScript runtime from Scratch