Grpc-node: node-v59-linux-x64/grpc_node.node is missing

Created on 17 Nov 2017  路  9Comments  路  Source: grpc/grpc-node

I am trying to use Firebase admin SDK in my server. When I deploy I get the error I am missing file node-v59-linux-x64/grpc_node.node in firebase-admin node_module map. I added "grpc": "1.7.1" in my package, but I still do not get that file after NPM update. I get an older version, node-v57. I also checked this path https://registry.npmjs.org/grpc/-/grpc-1.7.1.tgz, but I could not locate the file. I deleted my node_modules map and ran npm install again, still no node-v59.

How/where can I download that file? Is there any one who can put the file here so I can manually add it?

Error: Cannot find module '/data/app/node_modules/grpc/src/node/extension_binary/node-v59-linux-x64/grpc_node.node'

Most helpful comment

This will probably be fixed by running npm rebuild on the server that you deploy to.

All 9 comments

This will probably be fixed by running npm rebuild on the server that you deploy to.

No it still can not find that module. If anyone can place it here I can manually fix it.

The file is being downloaded by the node-pre-gyp package during the installation, it's not supposed to be inside the npm package. I would recommend looking at the installation logs to see why node-pre-gyp didn't properly download and/or install that file.

As described in the binary section of the package.json file, the URL for these binary files are https://storage.googleapis.com/grpc-precompiled-binaries/node/{name}/v{version}/{node_abi}-{platform}-{arch}.tar.gz so if you insist on hacking at your installation, you can find that file here: https://storage.googleapis.com/grpc-precompiled-binaries/node/grpc/v1.7.1/node-v59-linux-x64.tar.gz

@nicolasnoble thanks that worked. I had the problem before with node-v57 as well. I am running the server on Evennode. On both mac and windows I had the missing file, so maybe it is a problem on there server?

Same here, missing: node-v57-darwin-x64-unknown/grpc_node.node

Seeing this on production, can't deploy to our servers without running npm rebuild.

How can you tell what versions are available?

Without logs from what npm install says it's going to be difficult to troubleshoot this any further.

For the list of what we are currently releasing as binary packages, unfortunately google compute storage doesn't seem to allow us to share directories trees so we can't directly show what we have. But this is kind of inferable from these scripts.

With no further information nor logs, this issue is getting stale. Closing it.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

yanbou893 picture yanbou893  路  5Comments

Aswathi17 picture Aswathi17  路  3Comments

shotor picture shotor  路  3Comments

respinha picture respinha  路  6Comments

bkw picture bkw  路  5Comments