@ravi Your package.json can point to tarball or git repo which could be internal or where ever. In this way, none of these need to be published to npm and thus they can have conflicting names. For instance you can have a package name called 'request' that is different than the one in npm (maybe it is a private fork).
If you are using github then there is a nice way to get tarball using the URL form: https://github.com/USER/REPO/tarball/COMMIT where the COMMIT can be 'master', a branch, a tag, etc. So your dependency would look something like: { "dependencies": { "foo": "https://github.com/USER/REPO/tarball/mytag"; } For more info on this, use `npm help json` and scroll to the dependencies section. -- 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
