Bazel For a Frontend Monorepo

Disclaimer: This was done primarily as a study exercise. The goal was to learn Bazel hands-on and explore whether it could be a good fit for optimizing the build pipeline of this monorepo in the future. The hooks package Bazelification covered here has landed in production by the time you’re reading this, but the full monorepo migration is still a future ambition, not a done deal. I have a JavaScript monorepo called Pedalboard. It holds a few React component libraries, hooks, linting plugins, and dev tooling. Nothing crazy, but it has been a good playground for experimenting with different build tools over the years. Right now, whenever a change lands in the repo, a GitHub Actions workflow kicks off and does roughly this: pnpm install pnpm run build pnpm run test:since pnpm run lint:since And then it publishes any packages that need a new version. The test:since and lint:since scripts are smart enough to only run on packages that changed. But pnpm install and pnpm run build run uncondi