Managing packages with Lerna?

[open-telemetry]

Managing packages with Lerna?

[rochdev]

In my experience using it in a few large projects, it's really a must-have for monorepos. Using scripts is possible, but it becomes very cumbersome very quickly, and in the end you end up pretty much rewriting Lerna but as a less feature complete, more difficult to use, and with more bugs implementation since it's not an external project that can be contributed to easily.

I'd say this is a general rule for using scripts in general. For example why use npm or yarn at all? They are just downloading files and resolving dependencies using semver which can be done with scripts.

To be honest, I would even go as far as to say not using Lerna might end up preventing a lot of users from contributing due to how complex the project will become. This is especially true for instrumentation repos where many different library versions have to be tested at the same time.

Let's focus on our domain (telemetry) and not on managing monorepos.

[draffensperger]

I'm definitely open to Lerna, but in my limited experience with it for OpenCensus Web, it often felt like onre more dependency to have to manage (upgrade for security fixes, etc.) and that a lot of its functionality might be able to be replaced using simple scripts or tricks as explained in the gist above.

[rochdev]

Most of the downsides mentioned in the articles are also mitigated by combining Lerna with TypeScript and Yarn.

[draffensperger]

I'm fine with use of Lerna, just wanted to make sure including it is worth the extra weight of an extra dependency, sounds like in this case it is worth it!

[mayurkale22]

All agreed to use Lerna in today's meeting.

• It has its shortcomings (extra dependency) but it’s worth using it.
• OpenCensus uses it and worked well.
• It doesn't have the overhead on end users.