3 ms·
I have to disagree with this statement: "They learned from the failures of other package managers. It’s almost prefect!" I find the following cons with NPM:
by bryanlarsen 13y ago
I have to disagree with this statement: "They learned from the failures of other package managers. It’s almost prefect!"
I find the following cons with NPM:
- shrinkwrap does not work as well as the alternatives in Bundler (yes, that's plural).
- specifying versions as git hashes does not verify the hash on "npm install"
- npm link is more awkward than using :path => in Bundler.
The big difference between NPM and bundler is that NPM allows common dependencies of dependencies to have different versions. This is usually awesome, except when it isn't -- it can cause subtle breakages if you try to pass an object from one dependency to another. This is very rare though, and if I had to choose, I'd choose the NPM behaviour.
- munificent 13y agoI'd also add: - Allowing multiple versions of the same package in one application is asking for Cthulhu to climb out of the ocean and burn a whole in your mind and your program.
- reiz 13y agoI didn't know that with the git hash. That's a good point! What I like on NPM is that they use JSON for defining the dependencies and that the packages are by default not installed globally. NPM and Bundler are different in some ways, but in general they do both a good job.