4 ms·

> But why would I use yarn today? I think many many many people switched to Yarn 1.x wholesale and then switched back to NPM once it had undergone some improve

> But why would I use yarn today? I think many many many people switched to Yarn 1.x wholesale and then switched back to NPM once it had undergone some improvements.

leptons 3y ago
That's me. But for some projects I've had to switch back to yarn, because npm no longer works to install node_modules, and I don't really care why. Yarn works on those projects, npm does not. If npm works for a project, I use that, but there are some where yarn works and npm simply errors and quits.
spankalee 3y ago
This is exactly what I did. I even participated in the Yarn project a bit before it was fully open, but as npm 6 and 7 brought major speed improvements, workspaces, and overrides, I don't see the need for an alternate package manager anymore. As a library maintainer using the same package manager that most of my users do is a pretty big help. I'll be very happy when npm's linked install strategy is stable so that there's less reason to use pnpm and we get dependency isolation in monorepos.
- bhouston 3y ago
  > I don't see the need for an alternate package manager anymore. I do see a strong need for lerna though. Lerna's ability to manage concurrency, topological sort-based builds and streaming builds is phenomenal and an absolute necessity in monorepositories. It is unfortunate that this functionality is not available by default in npm in any way.
  - spankalee 3y ago
    npm workspaces plus Wireit works far better than Lerna, in my experience. https://github.com/google/wireit https://github.com/google/wireit Wireit's ability to specify actual script dependencies, do caching (and on Github actions), and its long-running service script support make it much more useful and comprehensive than Lerna. I agree that this should be built into npm. There's an RRFC for it here: https://github.com/npm/rfcs/issues/706 https://github.com/npm/rfcs/issues/706
koromak 3y ago
I did the same, switched back to npm in 2018/19 as I saw the majority of packages I was using doing the same. But in 2022-2023, I feel like I'm starting to see a lot of yarn again. Maybe just anecdotal, or maybe something changed I'm not aware of.

> But why would I use yarn today? I think many many many people switched to Yarn 1.x wholesale and then switched back to NPM once it had undergone some improvements.

leptons 3y ago

That's me. But for some projects I've had to switch back to yarn, because npm no longer works to install node_modules, and I don't really care why. Yarn works on those projects, npm does not. If npm works for a project, I use that, but there are some where yarn works and npm simply errors and quits.

spankalee 3y ago

This is exactly what I did. I even participated in the Yarn project a bit before it was fully open, but as npm 6 and 7 brought major speed improvements, workspaces, and overrides, I don't see the need for an alternate package manager anymore. As a library maintainer using the same package manager that most of my users do is a pretty big help. I'll be very happy when npm's linked install strategy is stable so that there's less reason to use pnpm and we get dependency isolation in monorepos.

bhouston 3y ago
> I don't see the need for an alternate package manager anymore. I do see a strong need for lerna though. Lerna's ability to manage concurrency, topological sort-based builds and streaming builds is phenomenal and an absolute necessity in monorepositories. It is unfortunate that this functionality is not available by default in npm in any way.
- spankalee 3y ago
  npm workspaces plus Wireit works far better than Lerna, in my experience. https://github.com/google/wireit https://github.com/google/wireit Wireit's ability to specify actual script dependencies, do caching (and on Github actions), and its long-running service script support make it much more useful and comprehensive than Lerna. I agree that this should be built into npm. There's an RRFC for it here: https://github.com/npm/rfcs/issues/706 https://github.com/npm/rfcs/issues/706

koromak 3y ago

I did the same, switched back to npm in 2018/19 as I saw the majority of packages I was using doing the same. But in 2022-2023, I feel like I'm starting to see a lot of yarn again. Maybe just anecdotal, or maybe something changed I'm not aware of.