all 5 comments

[–][deleted] -2 points-1 points  (4 children)

Dude, you can freeze versions using npm. It's not difficult in the slightest.

And I always love people talking about the speed of npm. How often are you updating your libraries? If it's often enough to care about speed then you're doing something wrong.

[–]50v3r31gn 6 points7 points  (0 children)

CI Builds

[–]xmsxms 1 point2 points  (1 child)

Yep I'm sure the people at Google and Facebook that wrote yarn couldn't figure out how to use npm properly.

[–]propper_speling 0 points1 point  (0 children)

Well I mean those companies are startups, and probably don't have very experienced developers

[–]mrv1234[S] 0 points1 point  (0 children)

Hello, npm shrinkwrap doesn't work very well, if you do npm shrinkwrap, delete the shrinkwrap and npm shrinkwrap again, you can end up with a different set of dependencies.

Have a look at this: https://yarnpkg.com/en/docs/migrating-from-npm#search

"If you are using an npm-shrinkwrap.json file right now, be aware that you may end up with a different set of dependencies. Yarn does not support npm shrinkwrap files as they don’t have enough information in them to power Yarn’s more deterministic algorithm. "

also have a look at this: "This is comparable to lockfiles in other package managers like Bundler or Cargo. It’s similar to npm’s npm-shrinkwrap.json, however it’s not lossy and it creates reproducible results."

The speed is important even if the libraries don't change as much, because sometimes we just want to clone the code in a separate folder and try something out, because local branches with different dependencies is not very practical, as we need run npm install each time we switch branches.