How to Use Bazel to Manage Monorepos: The Grammarly Front-End Team’s Experience [rus]
At some point, we reached the limit of the existing build process in the Grammarly Editor monorepo. Build tools required too much time to support, and each new package increased build time and made dependency management harder. To move further, we had to rethink the architecture of the build process. Our solution: We switched to Bazel. In this talk, I will share our findings and how we made the architecture of the build process scalable and predictable.
- Tech Lead, Software Engineer at Grammarly
- Has more than 10 years of experience in front-end development using various technologies, from Rails to Typescript
- Focused on creating the Grammarly Editor, an AI-powered writing assistant for Grammarly’s 30 million daily active users, for the last 5 years
- Contributes to Focal, an open-source reactive state management framework, in his spare time
- Co-hosts weekly talks in devua.club