"package": ">=1.0.1" Will grab the latest above that version. Is that what you are looking for?
-Chad -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Alex Kocharin Sent: Monday, October 22, 2012 7:22 PM To: [email protected] Subject: [nodejs] npm: version locking in modules 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
