3 ms·

I know it's dumb, but when a library requires me to install Yarn to install it, I think so much less of it. I just hate the idea that I have to install an enti

I know it's dumb, but when a library requires me to install Yarn to install it, I think so much less of it. I just hate the idea that I have to install an entire package manager simply to use some Node.js code, when NPM almost certainly could have done the job.

skrebbel 2y ago
It's not a library, it's an application. You're quoting a section called "Installing from Source". Obviously that'll require you to use the build tools the developers happened to have chosen. There's also a Docker option if you don't want to do that.
- EGreg 2y ago
  If anything requires me to install Docker, Yarn, or even Node.js, I immediately lose interest. Real programmers use butterflies!
  - MarcelOlsz 2y ago
    You can pry my JS ecosystem from my cold (& well manicured) dead hands.
samtheprogram 2y ago
Seems like it’s because they’re using the resolutions feature to override a dependency resolution. The alternative would be forking at least 1 package, all the way down to the dependency, to fix the version. There’s a reason there’s 3 popular package managers for Node that aren’t NPM. Yes, part of that is the culture/ecosystem, but not entirely.
- Ciunkos 2y ago
  The npm supports overrides field in package.json since like a few years already.
  - samtheprogram 2y ago
    True. Either way, Umami's been using `yarn` since 2020, before that release of NPM (although for what reason at that time, I don't know). Being bad thereby creating desirable competition has lasting effects. We could get into when/why/what each thing supports all day, but it's not worth it. Speaking of what's supported nowadays, installing other package managers is a corepack call away -- literally a whole other feature built into Node.js because NPM is/was/etc subpar. It's experimental, but this is all to say: it doesn't surprise me in the slightest that a project might use something that isn't NPM, and I actively expect it when picking up other's projects.

skrebbel 2y ago

It's not a library, it's an application. You're quoting a section called "Installing from Source". Obviously that'll require you to use the build tools the developers happened to have chosen. There's also a Docker option if you don't want to do that.

EGreg 2y ago
If anything requires me to install Docker, Yarn, or even Node.js, I immediately lose interest. Real programmers use butterflies!
- MarcelOlsz 2y ago
  You can pry my JS ecosystem from my cold (& well manicured) dead hands.

samtheprogram 2y ago

Seems like it’s because they’re using the resolutions feature to override a dependency resolution. The alternative would be forking at least 1 package, all the way down to the dependency, to fix the version. There’s a reason there’s 3 popular package managers for Node that aren’t NPM. Yes, part of that is the culture/ecosystem, but not entirely.

Ciunkos 2y ago
The npm supports overrides field in package.json since like a few years already.
- samtheprogram 2y ago
  True. Either way, Umami's been using `yarn` since 2020, before that release of NPM (although for what reason at that time, I don't know). Being bad thereby creating desirable competition has lasting effects. We could get into when/why/what each thing supports all day, but it's not worth it. Speaking of what's supported nowadays, installing other package managers is a corepack call away -- literally a whole other feature built into Node.js because NPM is/was/etc subpar. It's experimental, but this is all to say: it doesn't surprise me in the slightest that a project might use something that isn't NPM, and I actively expect it when picking up other's projects.