This tutorial walks you through creating a modular, plugin‑based CLI scaffold for a Valentine’s Day project, covering monorepo setup with Lerna, core CLI package creation, plugin registration, command handling, inter‑plugin communication with tapable, and deployment considerations.
This article outlines the evolution of our wireless frontend architecture from a legacy Backbone.js and ASP.NET stack to a modern Node.js/React-IMVC solution, discusses the challenges of size, tooling, and cross‑platform development, and presents our shift to a Model‑Oriented Pure‑Model framework with Monorepo and GraphQL‑BFF integration.
By migrating the “全民 K 歌” base library to a monorepo using Lerna, Yarn workspaces, and TypeScript, the team unified dependency management, enabled topological builds, enforced master‑only versioning with conventional commits, and automated CI‑driven publishing—including beta canary releases—significantly speeding iteration and improving maintenance.
This article explains the benefits of a monorepo for multi‑service web applications and demonstrates how to build, test, and deploy the services using Docker, docker‑compose, and GitLab CI/CD pipelines with selective job execution based on code changes.
This article explores the concept of a “micro‑backend” by adapting micro‑frontend principles to server‑side applications, detailing how to use IoC, monorepo management with Lerna, and Midway’s configurable scanning to split a large Node.js codebase into independent, maintainable domain modules without changing developer workflows.
This article analyzes common source‑code management patterns for numerous small projects, identifies their drawbacks, and proposes a hybrid solution that combines a single‑git repository with git‑submodule based sub‑projects, automated shell scripts, and Umi‑based tooling to achieve unified yet isolated development and deployment.
Facing rapid growth and the need to support dozens of OTT platforms, Tubi’s frontend team redesigned its web player into an independent, TypeScript‑driven module with a clear Adapter‑Player‑Action‑Reducer architecture, monorepo management, comprehensive testing and documentation, enabling higher code quality and a better cross‑platform playback experience.
This article explains the challenges of collaborating on multiple tightly coupled JavaScript packages, compares multirepo, monorepo and submodule strategies, introduces Lerna as a monorepo tool, and provides detailed guidance on its configuration, modes, and command‑line usage for efficient package management.
Google’s Piper monolithic code repository, built atop Spanner, holds over a billion files and 86 TB of source code, serving tens of thousands of engineers worldwide with trunk‑based development, fine‑grained permissions, automated code review, and massive build traffic, illustrating the benefits and challenges of a single‑repo strategy.
Using Lerna, the article shows how to convert a multi‑package JavaScript project into a production‑ready monorepo by initializing Lerna, hoisting dependencies, automating versioning and publishing, integrating commit‑linting, code‑style tools, Babel builds, and VSCode debugging for streamlined development.
