undefined | Better HN

0 pointsFriedrichN1y ago0 comments

Just the fact that Yarn seems to be the dominant package manager now when it seems like last week it was npm. What will it be next week?

I truly wonder, do people use this stuff for software that is expected to be maintained for 5-10 years? I feel that with the speed at which everything changes, gets deprecated, discontinued, succeeded, etc. you'll spend a good chunk of your time staying up to date with the current js ecosystem. That doesn't seem very economic to me.

0 comments

colordrops1y ago

Naw it's back to npm

anonzzzies1y ago

Pnpm ? Seems every week another flavour without any benefits.

tentacleuno1y ago

PNPM isn't exactly new; it's been in development since 2016[0] (which makes it 9 years old).

I've been using it for quite a while now. It has excellent mono-repo features, pnpmfile.js hooks, and it's just downright faster than NPM. Way, way faster.

I switched to it a couple of years ago, and it was definitely a breath of fresh air: no more waiting for 5 minutes for dependencies to install! I still find this to be the case when the odd create-XXX-app script finds itself using NPM.

[0]: https://github.com/pnpm/pnpm/commits/main/?after=5d1ed94e6c4...

fire_lake1y ago

pnpm has some advantages

true_religion1y ago

I have used yarn since 2018. It was developed in 2016.

What does dominant even mean in such a short term context? It hasn’t even been 10 years.

As far as companies go, we move so slowly that when someone brings up a tech fad, the fad is gone by the time the committee actually gets to decide. So we stick with the status quo.

rjh291y ago

Basically npm fell heavily behind in development so people switched to yarn; it's back to npm now. This is over a timescale of 10 years or so.

dudus1y ago

I'm one of "those".

I'm using bun now, but I was on pnpm for a while.

j / k navigate · click thread line to collapse