$ firebase --version
3.13.1
$ node --version
v8.8.1
$ uname -a
Darwin Kits-MacBook-Pro.local 17.0.0 Darwin Kernel Version 17.0.0: Thu Aug 24 21:48:19 PDT 2017; root:xnu-4570.1.46~2/RELEASE_X86_64 x86_64
yarn global add firebase-tools
firebase deploy
=== Deploying to 'amigas-del-mar'...
[..]
i functions: preparing functions directory for uploading...
Error: Error parsing triggers: Cannot find module '/private/var/folders/bp/b021274d72qfz2v19mm9pc480000gn/T/fbfn_616726OrDctMi1yiU/node_modules/firebase-admin/node_modules/grpc/src/node/extension_binary/node-v57-darwin-x64/grpc_node.node
This makes no difference: https://github.com/firebase/firebase-tools/issues/442 and I don't have this installation issue: https://github.com/firebase/firebase-tools/issues/467
I've uninstalled firebase-tools completely, removed previous versions of node, removed node_modules and cleaned the yarn and npm cache. Nothing seem to resolve the issue except to downgrade to node 7.x, I'm at a loss.
Same with versions:
node v6.11.1
firebase 3.14.0
Switch to node v8.9 (using nvm) resolved this for me.
@FirebaseTeam Can you please investigate this firebase-functions + grpc thing and provide an official solution? It popped up for me when I went out of my way to downgrade to 6.11.1 (using nvm, n, brew, official installer, etc. now...) to be in-line with firebase-functions old version of Node.
I've seen several of these issues and the problem just seems like a problem with the grpc build.
馃帀 Running npm rebuild finally fixed the issue for me.
If you're still having GRPC issues, please provide feedback at grpc/grpc-node#121
I had to run the npm rebuild from within the functions directory, then it was fixed.
Most helpful comment
@FirebaseTeam Can you please investigate this firebase-functions + grpc thing and provide an official solution? It popped up for me when I went out of my way to downgrade to 6.11.1 (using nvm, n, brew, official installer, etc. now...) to be in-line with firebase-functions old version of Node.
I've seen several of these issues and the problem just seems like a problem with the grpc build.
馃帀 Running
npm rebuildfinally fixed the issue for me.