Standard Server JavaScript - Deno, Workers, Bun and More

Episode Summary

Executive Summary: The episode argues that server-side JavaScript is converging around browser-standard APIs, making code more portable across Node, Deno, Cloudflare, Bun, and other runtimes. Wes and Scott explain why developers should prefer standards like fetch, URL, web streams, and structured clone, while using lightweight frameworks and tools to bridge routing and response helpers. They also discuss practical limits such as startup time, file-system support, and runtime differences.

Main Topics: Server-side runtime fragmentation and portability: The hosts survey the growing number of JavaScript runtimes and edge platforms, emphasizing that code portability is becoming a major concern for package authors and server-side developers. Browser APIs as the standard layer: They argue that the future of server-side JavaScript is to use browser-native APIs (fetch, URL, streams, etc.) instead of Node-only APIs wherever possible. Fetch, Request, Response, and URL tooling: The episode details how fetch underpins incoming/outgoing communication on edge platforms and how URL and URLSearchParams simplify parsing and constructing request state. Web streams, cancellation, and structured clone: They explain streaming responses, canceling in-flight work, and deep-cloning data with structured clone as key examples of cross-runtime standardization. Lightweight runtime-agnostic libraries and frameworks: Tools like Hono, itty-router, and linkedom are highlighted as examples of small abstractions that preserve portability while adding missing convenience features. Gaps and constraints in the standardization effort: They note current limitations around file-system APIs, startup time, and compatibility with older Node-oriented packages, which can complicate migration. Sponsor/sick-pick segment and personal recommendations: The episode closes with lifestyle recommendations (outdoor furniture and a calorie-tracking app) plus promotional mentions for courses and Sentry.

Key Arguments: Server-side JavaScript should increasingly target web standards so code can run across multiple runtimes without rewrite. Browser APIs are already familiar to developers, so standardizing on them reduces cognitive overhead and improves interoperability. Fetch and Request/Response form the core abstraction for serverless and edge handlers, especially on platforms like Cloudflare and Deno Deploy. URL and URLSearchParams are superior to ad hoc string parsing for query state, routing, and shareable application state. Web streams enable real-time, progressive delivery of data and can be canceled from the client without custom protocols. Structured clone solves deep-copy needs and is becoming a useful cross-runtime primitive. Small wrapper frameworks such as Hono and itty-router make standard APIs practical by adding routing and convenience methods without heavy runtime lock-in. There are still unresolved areas like standardized file-system access, and startup/CPU limits on edge runtimes can affect package choice.

Data Points: Number of runtimes named in intro: Node, Deno, Cloudflare, Bun, Fastly, Alibaba (and more) - Used to illustrate the explosion of server-side JavaScript runtimes Cloudflare worker startup limit: About 50 megabytes - Mentioned as a rough size limit for serverless/edge functions Cloudflare CPU startup concern: 200 milliseconds boot time is too long - Example of a package taking too long to bootstrap for edge runtimes Chrome support for structured clone: Chrome 98 - Used to show structured clone is relatively recent in browsers Safari support for structured clone: Safari 15.4 - Used alongside Chrome version to show browser rollout timing Episode reference: 587 - Referenced as the prior episode explaining web streams Hono size: 12 KB - Described as a lightweight framework suited for edge/runtime portability itty-router size: 440 bytes - Highlighted as an extremely small router abstraction itty-fetcher size comparison: 1/20th the size of Axios - Positioned as a lightweight Axios replacement Weight-loss progress duration: About a year and a half - Scott’s personal fitness goal mentioned during the sick pick segment Scheduled points accumulation: Credit card points used yearly - Wes uses points to buy outdoor furniture for the cottage

Pivotal Quotes: "At the end of the day, it's all just JavaScript." — Wes Boss: Explaining the appeal of standard browser APIs across server-side runtimes "So just tell yourself, okay, let me pause for a second, figure out: is there a web standards way?" — Wes Boss: Advice to developers even when building for Node only "The whole point of the Winter CG is that we're not standardizing on Node APIs." — Wes Boss: Clarifying that the industry is converging on web standards rather than Node-specific primitives

Implications: Developers should favor portable web APIs and lightweight abstractions now, because the ecosystem is moving toward runtime-agnostic server-side JavaScript. This can reduce lock-in and ease migration across edge and cloud platforms.