ahh.. that makes sense.
Lately, I've been using "latest" in my package.json while in development (so I can stay updated and fix issues as new things are released), then changing to specific version numbers right before release.
I'm open to feedback on that approach if y'all think I'm insane. :)
On Feb 7, 2012, at 9:45 AM, Bill Laing wrote:
version - "Version must be parseable by node-semver, which is bundled with npm as a dependency. (
npm install semver to use it yourself.) "
tag - The only tag with special significance is "latest". That version is installed by default when no other tag or version number is specified, and always points to the most recently updated version of a package.
Ill interpret version as a numbering system that accommodates range dependencies, whereas tag acts more like an alias. Tag could support a nomenclature like latest for most recent and stable for currently supported version for example.
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Bill Laing ([address removed]) from Atlanta Nodejs Developers.
To learn more about Bill Laing, visit his/her member profile
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages
Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]