Which Will Reach Production, Deno or Bun? Lessons from Implementing...
summary
A TypeScript SCIM-like user provisioning API was implemented and deployed in Docker/Kubernetes, and the team compared running the same tsoa/Express-generated routes on Node.js alternatives Deno and Bun. Deno required explicit permission flags, import maps, and a week-long workaround to add ".ts" suffixes to generated imports but is running in production for some clients; Bun is almost Node-compatible, released a stable version recently, and works with Vitest while Deno tests use its test runner.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:10Node.js overview
- 4:11Node.js issues and Deno
- 5:57First Deno use case
- 7:23Deno imports and permissions
- 9:48Deno executables and tools
- 11:56Deno tests and compatibility
- 14:02Deno dependency management
- 15:45Deno API implementation
- 18:41Deno challenges
- 19:03Bun overview
- 20:10Bun compatibility and tests
- 21:16Bun deployment and usage
- 22:48Deno vs Bun comparison
- 25:20Performance and community analysis
- 26:44Q&A
