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.
Not a fan.
We'll be shipping dead code, bloating our client side code. Solution to that? Strip these comments are part of a build step. Ok, but then, what benefit does this provide?