Yarn Fun
Use Cases and Deployment Scope
We have a lot of NodeJS projects in the company I work for. This includes our customer database, which contains millions of records. Many of those projects also have a microservice architecture. In order to keep our code tidy and manageable, we segment it into logical NodeJS modules and use Yarn to install those modules and manage their versions. This is very important to us, as we need to reuse as much code as we can in different microservices (for authentication, calling other APIs, security ...)
Pros
- Package management
- Speed of download compared to npm
- Moduel version control
Cons
- Rarely, some server connection error appear, while npm works alright.
- Sometimes, deleting the whole vendor directory is the best solution to solve weird issues.
- You still might need npm to install Yarn.
Most Important Features
- Ease of use to manage our dependencies
- Integration inside CI/CD pipelines
- Its Performance
Return on Investment
- Deployments happen much faster.
- Building and testing our apps is much more streamlined and efficient.
- Makes it easier to write reusable code.
Alternatives Considered
npm
Other Software Used
Composer, Amazon Fargate, Amazon Aurora