dominictarr / semver-ftw

Simple Description of SemVer
http://semver-ftw.org
MIT License
25 stars 5 forks source link

Exact almost never break #6

Closed vvo closed 8 years ago

vvo commented 9 years ago

also fixes #4

naholyr commented 9 years ago

Should add a word about shrinkwrap or is it too trolly ? :P

vvo commented 9 years ago

I stay away from shrinkwrap until it will be stable :)

vvo commented 9 years ago

I mean, shrinkwrap works but is a pain to use and update

naholyr commented 9 years ago

As an addendum, it's the author to decide but it's not obvious to me if this article should or not bother about sub-dependencies. Maybe the proper fix would be keeping the old sentence and add "(beware poorly managed sub-dependencies)" + a link to more info

vvo commented 9 years ago

beware poorly managed sub-dependencies

Well the default npm install strategy is to be "poor". Choosing save-exact is only a matter of taste/preference/paranoia I think

dominictarr commented 9 years ago

this is correct, but I feel it is sort of off putting to the reader, the objective here is to explain responsible use of semver. I'm okay with encouraging people to use exact..

maybe it should say that it's best practice to check in your dependencies if you are writing an application? and not a module?

vvo commented 8 years ago

Not needed, I don't even use exact anymore: https://gist.github.com/vvo/84a94cfc0f94c91ea6b6