npm pack creates a tarball from your lib, put the tarball on a webserver, where it can be downloaded, put the url to the tarball in the package.json of your site projects. you can name your tarball with different versions and reference it so.
npm link is meant for development not production usage. if you want localy link your myLib to site1 for development, you can uninstall myLib localy and doe the link then. Am Montag, 8. Juli 2013 14:09:10 UTC+2 schrieb Maxim Yefremov: > > I have site1 and site2 on one server, they both depend on one library > myLib via npm link. > > I changed myLib for site2 so it might be buggy for site1. How to avoid it? > > I want to use separate versions of myLib for site1 and site2. > > But when I do npm link command for myLib on server then site1 and site2 both > use the same version of myLib > -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
