Replies: 1 comment 2 replies
-
Thanks for sharing the blog, I was waiting for it and didn't notice it. No plan on the short term, when I created Lerna-Lite I was mainly focused on updating all dependencies and then eventually made it smaller (for my use case, I only ever used 3 commands,
In summary, I'm especially concerned about number 2 and I still prefer to use Lerna-Lite because of number 1. When I created Lerna-Lite, I was more interested in updating all dependencies since they were quite outdated at the time and I wasn't looking too much at the modularity but now that I have it, then I think it's a great advantage for its smaller size in comparison to Lerna. Also, we'll see how often they'll change the codebase but as it is today, the code that is in Lerna-Lite came from Lerna, so I can still follow Lerna PRs and apply their changes into Lerna-Lite by replicating their PRs (when possible). Nrwl has a blog talking about computational caching which might be interesting but again we'll see how big of a change that will be on the codebase to implement it, if it's thousand of lines to change then that might be harder to replicate. I'm not sure if that addresses your question, but that's my take on it for the short term. At the end of the day, I'm just a regular developer/user of Lerna and I created Lerna-Lite to help my own project and if it's helping others (I think it does consider all the stars it has now) if that is the case, then it's an satisfying enough as a bonus We'll see what happens next with Lerna in the future, time will tell. EDITI was afraid of number 2 and unfortunately, but not surprisingly, it came true. Lerna 5+ now has installs Nx and even TypeScript as required dependencies (want it or not), which is not the case in Lerna-Lite (and will never be). So... Lerna-Lite is here to stay. 🚀 |
Beta Was this translation helpful? Give feedback.
-
lerna/lerna#3121
and https://blog.nrwl.io/lerna-is-dead-long-live-lerna-61259f97dbd9
Beta Was this translation helpful? Give feedback.
All reactions