5 ms·
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
by 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 agoThe npm supports overrides field in package.json since like a few years already.
- samtheprogram 2y agoTrue. 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.