How to Use Yarn Workspaces for Efficient Code Sharing in a Mono-Repository

Yarn workspaces provide an efficient and standardized way to share code across multiple projects within a single repository. In this article, we will explore how we have successfully implemented yarn workspaces in our own project.

To begin with, we removed all the `node_modules` folders and `yarn.lock` files from each of our projects. We then ran `yarn install` at the root of the project to create a new and clean `yarn.lock` file. This allowed us to keep track of all our dependencies in one place.

Next, we created a top-level `package.json` file with a workspace configuration. The official documentation provides detailed instructions on how to migrate to yarn workspaces, which is highly recommended for those interested in learning more.

One of the key benefits of using yarn workspaces is the ability to reduce the size of Docker images by installing only the dependencies required for each individual project. This can be achieved with the help of the `focus` plugin, which allows us to install dependencies specific to a particular workspace.

In addition to reducing image sizes, yarn workspaces also enable us to easily declare folders on our file system as packages that can be installed and used directly in other projects. For example, we have created a `frontend` workspace at `/frontend`, which has its own `package.json` file with dependencies specific to that project.

Another advantage of using yarn workspaces is the ability to keep all our code organized under one umbrella. By having a single `yarn.lock` file at the root of our project, we can easily manage and update dependencies across all our projects.

In our case, we have three projects: an API written in Python with the Django web framework, a big React app, and a website built with NextJS. All of these projects are stored within the same Git repository, making it easy to share code and collaborate with my team.

Working with yarn workspaces has been a game-changer for our development workflow. It allows us to easily make changes across all our projects simultaneously, which has significantly improved our productivity and efficiency. With yarn workspaces, we can focus on writing code rather than worrying about managing dependencies and configurations.

If you're interested in learning more about yarn workspaces or monorepo architecture, I recommend checking out the official documentation and other resources such as monorepo.tools and Misconceptions about Monorepos: Monorepo != Monolith.

Yarn workspaces run