719: Fullstack TypeScript Apps with No Build Step?! with Brian LeRoux

Episode Summary

Executive Summary: Brian LaRue argues for starting with the simplest web stack—HTML, CSS, and raw ESM—before reaching for bundlers or heavy transpilation, emphasizing measurement, debugging ease, and platform-native tooling. He explains how Enhance server-renders web components without a build step, supports progressive enhancement, WebSockets, forms, and utility CSS, and discusses broader trends like browser maturity, Safari/WebKit’s progress, AWS scale, serverless, and new runtimes.

Main Topics: Anti-bundler, measure-first philosophy: Brian’s core thesis is that bundlers and transpilers should not be the default. He prefers starting with unbundled JavaScript and only introducing tooling when evidence shows it’s needed, because it improves iteration speed, source readability, and debugging. What Enhance is and how it works: Enhance is presented as an HTML-first, standards-focused framework for building web apps with server-rendered web components and no required build step. It grew out of Architect and aims to let developers build with web platform primitives. Server-rendered web components and progressive enhancement: The conversation covers how Enhance expands web component templates on the server, sends mostly HTML to the browser, and uses client JS sparingly for interactivity, forms, websockets, and enhancements. Forms, validation, and state management: Brian explains Enhance’s approach to forms: start with plain HTML forms, use server validation and redirects, preserve values via sessions, and only add client-side interactivity when necessary. This avoids unnecessary client state complexity. CSS strategy and utility-first opinions: Enhance supports raw CSS, scoped component styles, and utility CSS. Brian favors utility systems and fluid scales, arguing they reduce stylesheet bloat while still allowing component-specific styles when needed. Browser/platform maturity and ecosystem shifts: Brian argues browsers are finally good enough to rely on more directly, highlighting HTTP2/3, evergreen updates, WebKit improvements, and new features like view transitions and scroll-driven animation. AWS, serverless, and runtime ecosystem: The discussion touches on AWS re:Invent, AWS Lite, Node vs. Deno vs. Bun, and how the proliferation of runtimes and APIs reinforces Node’s importance while exposing performance/debugging tradeoffs in large SDKs.

Key Arguments: Start with the simplest thing that can possibly work; bundling is a technique, not a requirement. Bundling introduces developer-experience costs: slower iteration and harder debugging, especially when source maps or stack traces are imperfect. The browser platform has matured enough that many apps can ship mostly HTML with minimal JavaScript, especially with server rendering and progressive enhancement. Enhance can server-render web components and still preserve a migration path to richer client-side behavior when needed. TypeScript can be useful without a full transpilation/build pipeline by using JSDoc and .d.ts files. Many forms do not need client-side state machines; server validation plus redirects and session-based error handling is often enough. Utility CSS and fluid layouts can control stylesheet growth better than huge ad hoc CSS files. AWS SDK bloat and Node 20 changes show how bundling can be a liability in production and debugging contexts. Browser diversity remains important even as evergreen updates improve the baseline experience. New browser APIs and improving WebKit/Chrome capabilities make the native platform increasingly viable for sophisticated UI patterns.

Data Points: AWS SDK package size: ~95 MB - Brian cites the new AWS JavaScript SDK payload as a major cold-start and performance problem. AWS Lite benchmark speedup: ~5x faster - He says AWS Lite benchmarks show roughly five times better performance than the bundled/standard approach in that case. Enhanced.dev JS on music page: 21 lines - He references enhanced-music.com and notes the client-side JavaScript visible in DevTools is only 21 lines including service worker registration. Server-rendered components benchmark: 10,000 components in sub-10 ms - Brian claims Enhance can render about ten thousand components on the server in under ten milliseconds. Time to first URL on Begin: within 1.5 minutes - He says Begin can get an application a URL very quickly. Time to custom domain on Begin: another 5 minutes - He adds that a custom domain can be configured shortly after initial deployment. AWS re:Invent attendance: 60,000-70,000 people - Brian describes the scale of the conference. AWS service count: ~400 services - He uses this to illustrate AWS’s breadth and the difficulty of navigating it. Enhance’s AWS usage: ~30 services - He notes their startup uses less than 10% of AWS’s total surface area.

Pivotal Quotes: "You can't fix what you can't measure." — Brian LaRue: Used to justify measurement-first engineering and observability before optimizing or debating tooling choices. "It's a technique. It's not an edict." — Brian LaRue: Referring to bundling, emphasizing that developers should choose it only when it solves a real problem. "The simplest thing that could work is probably HTML, CSS, and JavaScript." — Brian LaRue: Summarizes his preferred starting point for web development before adding extra tools.

Implications: Listeners are encouraged to treat bundlers, transpilers, and heavy client frameworks as optional optimizations—not defaults. The episode suggests the platform is now strong enough for more server-first, standards-based apps with better debugging, performance, and portability.