Here are some relevant npm github issues for reference: https://github.com/isaacs/npm/issues/1341 https://github.com/isaacs/npm/issues/2442 https://github.com/isaacs/npm/issues/1558
Cheers, Adam On Mon, Aug 20, 2012 at 10:38 AM, Adam Crabtree <[email protected]>wrote: > Howdy all, > > We're currently determining our post-git-merge npm install process, and I > was just curious if anyone's come up with anything particularly elegant > that's worked well for them. Our project is a multiprocess server, with > each process having it's own self-contained dependencies in addition to a > shared lib directory with its own dependencies. > > / > /lib > package.json > /node_modules > /services > /serviceA > package.json > /node_modules > /main > package.json > /node_modules > > After merging, npm install needs to be run on each directory with a > package.json. Currently in our root directory's package.json we have a > preinstall hook to cd to each directory, and run `npm install`, which is a > bit awkward, thus my question. How are others handling this scenario since > npm does not support AFAIK providing a directory to run `npm install` in or > recursively crawling a root directory and npm installing automatically? > > Cheers, > Adam Crabtree > > -- > Better a little with righteousness > than much gain with injustice. > Proverbs 16:8 > -- Better a little with righteousness than much gain with injustice. Proverbs 16:8 -- 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
