Echo JS 0.11.0

From npm to yarn to pnpm - the why, what and how

at blog.bitexpert.de

1 up and 0 down, posted by bitexpert 497 days ago 2 comments

badsyntax 494 days ago. link 1 point ▲ ▼

I really don't get the reasons for moving away from npm. package lock conflicts? you should have processes in place to ensure you're all using the same node/npm version. package hoisting? npm workspaces work great.

The author talks about having less issues from moving from npm to yarn, but here they are now moving away from yarn, seemingly just to save space on disk?

Honestly I do think there are more important things to be doing. npm works fine.

Replies

tracker1 493 days ago. link 1 point ▲ ▼

When yarn started, it really was a performance improvement over npm at the time... but npm has gotten (much) better... I think it's just best to generally stick with npm, though the past couple jobs I've been at they were using yarn.