Videos / Web Dev

Episode 11 of 16 · Web development, end to end

Bun: a runtime, a bundler and a package manager in one binary

Chapters

1. Five programs, one binary0:00
2. The engine underneath0:16
3. Tiers, and what for0:34
4. Written in Zig0:54
5. What is in the binary1:12
6. The drift that stops1:30
7. An install, in files1:47
8. The resolve pass2:04
9. The lockfile, readable2:24
10. One cache per machine2:42
11. The copy never made3:00
12. The limit, and the edge3:17
13. Hand it a TypeScript file3:35
14. Erased, and not checked3:52
15. JSX, and one config4:09
16. The bundler, flags4:26
17. One file to hand over4:43
18. Hooks, and the limit5:01
19. A test that needs nothing5:19
20. A surface you know5:37
21. The browser it lacks5:55
22. Shaped like Node6:12
23. And the web platform6:31
24. The Bun only half6:48
25. The only report that counts7:04
26. What does work7:21
27. The native wall7:40
28. The V8 shaped edges7:57
29. Four checks, in order8:18
30. Loud, and reversible8:37
31. One line in a CI file8:57
32. Where it reliably wins9:14
33. A different size of bet9:33
34. Four times to say no9:50
35. The benchmark trap10:08
36. A week of it10:27
37. From the outside in10:44

Bun: a runtime, a bundler and a package manager in one binary. Start a Node project and count the programs you now depend on. Node itself. N P M. The TypeScript compiler. A test runner. A bundler. Five separate tools that all have to agree wit

Mark as watchedSaved in this browser only.