Why you need a build system, and why it should be Bazel
summary
A real migration story: a codebase moves to TypeScript and a homegrown build is a 2,000-line gulp with 100 tasks and 400 dependencies, slow, non‑reproducible and brittle, costing weeks to fix. Replacing it with Bazel yields hermetic, declarative build rules, precise dependency graphs, sandboxed actions, caching, parallelism and remote execution; concrete artifacts are produced incrementally (JS and .d.ts), rules_typescript and rules_angular exist, and the build becomes debuggable, fast and reproducible.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:41Typescript
- 1:08The old build system
- 3:48Broccoli build tool
- 4:10Bazel was bad
- 5:16Angular is just a snowflake
- 5:34The conceptual problem
- 6:40Basil
- 6:54Functional Programming
- 7:16fractional builds
- 9:08Bazel build files
- 10:40Demo
- 13:34Build rules
- 14:28Implementation
- 15:17Type of Implementation
- 16:57Dependencies
- 20:39The build rule
- 21:43Conclusion
related talks
31mHey Dad, What's Bazel?
28mFront End Development with Bazel: Angular/TypeScript and Persistent Workers
01h 01mIntroduction to Bazel
26mBuilding Go with Bazel
23mFull stack development with Bazel, Angular and other friends.
25mInteroperating Bazel and Other Build Systems
23mPolyglot Builds with Bazel
37mSupercharge Your Builds with Bazel