-
Notifications
You must be signed in to change notification settings - Fork 161
Description
Summary
Since the very early days of this of this repository we have used lerna
to orchestrate commands across the workspaces of this monorepo.
Since then the ecosystem has evolved and we've been able to offload most of the tasks that lerna
does to npm workspaces, except two:
lerna version
lerna publish
Since the version of lerna
that we are using is dependent on vulnerable dependencies, and upgrading it has proven challenging in the past, we're going to instead invest efforts in finally migrating off it.
Why is this needed?
Lerna is a dependency-heavy package, it brings in 554 dependencies, some of which completely useless for what we need it for.
By investing this initial effort in replacing it with more focused alternatives or by npm
workspaces (aka no dependencies) we'll reduce the dependency tree surface and decrease maintenance overhead in the long term.
Which area does this relate to?
Automation
Solution
No response
Acknowledgment
- This request meets Powertools for AWS Lambda (TypeScript) Tenets
- Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET
Future readers
Please react with 👍 and your use case to help us understand customer demand.
Sub-issues
Metadata
Metadata
Assignees
Labels
Type
Projects
Status