I think it comes down to a tradeoff. A lot of packages are not written as well or as thorough as they could be. A lot of packages I look at on NPM are pre 0.1 even.
Thus it comes down to whether you would rather have all packages using their latest version, or whether you want a tacit "guarantee" of functionality. The Linux kernel team for example recommends always running the latest release, but most distributions lock the kernel version down for several months if not longer. I think just using the latest compatible (i.e. no API changes) package for all packages is a good idea, but when things go wrong I would like to know the *exact* versions used by the developer in order to avoid a lot of wasted time troubleshooting. On Tue, Oct 23, 2012 at 6:11 PM, Alex Kocharin <[email protected]> wrote: > > It's because I strongly believe that, if you have enough time for testing, > it's far better to always use latest versions of every software. > > If you have a good knowledge of the software you use, and good integration > tests, and a testing team, it's nothing wrong with usage of, say, node > 0.9.x on production, right? I assume that newer versions of a software is > generally better, if you have a time to test everything and track all API > changes. > -- > // alex > > > 23.10.2012, 11:06, "greelgorke" <[email protected]>: > > only option is to install all dependencies, then remove all > sub-dependencies and reinstall then manually also. > but why do you that that anyway? > > Am Dienstag, 23. Oktober 2012 01:22:47 UTC+2 schrieb Alex Kocharin: > > Hi all, > > Some node.js modules depend on strict versions of another modules like > that: > "dependencies":{"mongodb":"0.9.9-3"} // mongode > > or that: > "engines": { "node": "~0.6" } // express did it some time ago > > Now suppose I want to always use newer versions of any modules and don't > care much about what maintainers thinks about it. What should I do? > > Is there any option for npm to lose respect for upper bounds of version > range, but still respect lower bounds? Or any configuration like "whenever > you see module@X, always install module@Y"? > > -- > // alex > > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
