Next-Gen Server JavaScript: Web Standards
summary
JavaScript now runs on many server runtimes (Node, Deno, Bun, Cloudflare Workers, Fastly, Alibaba) while browsers use three engines (V8, SpiderMonkey, JavaScriptCore), so there are more server environments than browsers. The useful specifics: the fetch standard unifies request/response handlers and enables a single Handler to run on Bun, Deno, and Cloudflare; web streams and renderToReadableStream enable streaming React HTML to clients; Cloudflare’s HTML Rewriter and workers power on‑the‑fly proxies, image caching for Cloudinary, and incremental site migration. Packages like linkedom and worker tools increase cross‑runtime compatibility; a recent runtime hit 45 million installs in a week.
AI-written summary · about
chapters (13)
- 0:00Introduction to JS runtimes
- 1:29The state of server JS
- 2:38Why new runtimes exist
- 4:51Server types
- 6:49Standardizing APIs
- 8:25Fetch API implementation
- 9:50Web streams and events
- 11:52Forms and workers
- 13:34Edge functions use cases
- 16:42Modifying SaaS with edge
- 18:51Async context and tools
- 20:51Interoperable packages
- 23:43Future of standards
related talks
40mIt's Not Just Node.js Anymore
32mPushing boundaries to the edge
07mBuilding a Node js runtime for the browser
32mJavaScript on the Server: To Be or Not To Be?
26mTowards a stdlib for JavaScript Runtimes
23mWeb Assembly: The Future Of Js And A Multi-Language Web
17mShipping to the Edge
21mWhat to expect from a modern web framework?