The deployment then fails. The only way I can reference these packages is by referring to the tarball files for them from github. This works as a workaround for me, but this is an issue that I'm sure has to be causing others trouble, too.
I'm not sure if it's complaining that it can't find `git`, or if the temporary directory (npm-6548) doesn't exist.
Here is the exact error output from Azure's deployment log:
npm ERR! git clone git://github.com/aejay/locomotive.git#master CreateProcessW: The system cannot find the file specified.
npm ERR! Error: `git "clone" "git://github.com/aejay/locomotive.git#master" "C:\\DWASFiles\\Sites\\[site-name]\\Temp\\npm-6548\\1355148333320-0.58272026758641"` failed with 127
npm ERR! at ChildProcess.<anonymous> (D:\Program Files (x86)\nodejs\node_modules\npm\lib\utils\exec.js:56:20)
npm ERR! at ChildProcess.emit (events.js:70:17)
npm ERR! at maybeExit (child_process.js:358:16)
npm ERR! at Socket.<anonymous> (child_process.js:463:7)
npm ERR! at Socket.emit (events.js:67:17)
npm ERR! at Array.<anonymous> (net.js:335:10)
npm ERR! at EventEmitter._tickCallback (node.js:190:38)
npm ERR! [Error: `git "clone" "git://github.com/aejay/locomotive.git#master" "C:\\DWASFiles\\Sites\\[site-name]\\Temp\\npm-6548\\1355148333320-0.58272026758641"` failed with 127]
Edited byAejayMonday, December 10, 2012 6:32 PMAdded details
@Aejay: could you please share a minimal repo (e.g. on Github) that we can directly try pushing to Azure to see what you're seeing? That would help make sure that we are trying the exact same thing as you. Thanks!
I haven't tried that yet, but I can do so in a few minutes.
Here is a fresh test repo that shows the same symptoms:
Or not. The network proxy I'm working through right now won't let me push to the repository. If you push a copy of that repo to a site, though, you should get the same result (I hope, otherwise I'll look like a fool).