npm install @google-cloud/speech fails about nodejs-speech

[alexander-fenster]

My understanding is that it was caused by some temporary npm outage. We sometimes have some transient failures in our CI usually caused by npm but overall it's mostly green for speech. https://circleci.com/gh/googleapis/workflows/nodejs-speech/tree/master

Let me close this issue for now. @cconcise please feel free to reopen / comment if you still experience the install issue.

[JustinBeckwith]

Meep. I can reproduce this:

beckwith-macbookpro2:speeeeech beckwith$ npm install @google-cloud/speech
WARN tar ENOENT: no such file or directory, open '/Users/beckwith/Code/speeeeech/node_modules/.staging/yargs-c7f67d2c/lib/tokenize-arg-string.js'
WARN tar ENOENT: no such file or directory, open '/Users/beckwith/Code/speeeeech/node_modules/.staging/yargs-c7f67d2c/lib/usage.js'
WARN tar ENOENT: no such file or directory, open '/Users/beckwith/Code/speeeeech/node_modules/.staging/bytebuffer-a6d9511b/dist/bytebuffer.min.js'
npm WARN [email protected] No description
npm WARN [email protected] No repository field.

npm ERR! code E404
npm ERR! 404 Not Found: protobufjs@^5.0.3

Before trying it, make sure to:

$ npm cache clean --force
$ rm -rf node_modules package-lock.json
$ npm install

[JustinBeckwith]

@alexander-fenster I'm running out of people to assign P0 issues to 😆 Do you think you could take a look tomorrow?

[jkwlui]

I am unable to reproduce the problem, it installed fine on my machine.

$  node -v
v6.11.1

$  npm -v
3.10.10

[mattrcullum]

Just confirming that installing the package works fine now and it was in fact caused by an NPM outage