npm ERR! Failed at the grpc@1.24.0 install script.

[huturen]

Error as below:

npm ERR! Failed at the grpc@1.24.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-10-09T11_59_21_558Z-debug.log
Task quited with error: Task end with error: Error: Command failed: npm --registry=http://r.npm.oa.com install --production In file included from ../deps/grpc/third_party/upb/upb/msg.h:14:0, from ../deps/grpc/third_party/upb/upb/generated_util.h:10, from ../deps/grpc/src/core/ext/upb-generated/src/proto/grpc/gcp/transport_security_common.upb.h:12, from ../deps/grpc/src/core/tsi/alts/handshaker/transport_security_common_api.h:29, from ../deps/grpc/src/core/lib/security/credentials/alts/grpc_alts_credentials_options.h:26, from ../deps/grpc/src/core/lib/security/credentials/alts/alts_credentials.h:26, from ../deps/grpc/src/core/lib/security/credentials/alts/alts_credentials.cc:21: ../deps/grpc/third_party/upb/upb/upb.h:27:28: fatal error: upb/port_def.inc: No such file or directory compilation terminated. make: *** [Release/obj.target/grpc/deps/grpc/src/core/lib/security/credentials/alts/alts_credentials.o] Error 1 gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23) gyp ERR! stack at ChildProcess.emit (events.js:198:13) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12) gyp ERR! System Linux 3.10.107-1-tlinux2-0048 gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--library=static_library" "--module=~/dataServer/dataServer/src/node_modules/grpc/src/node/extension_binary/node-v64-linux-x64-glibc/grpc_node.node" "--module_name=grpc_node" "--module_path=~/dataServer/dataServer/src/node_modules/grpc/src/node/extension_binary/node-v64-linux-x64-glibc" "--napi_version=4" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v64" gyp ERR! cwd ~/dataServer/dataServer/src/node_modules/grpc gyp ERR! node -v v10.16.0 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok node-pre-gyp ERR! build error node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --library=static_library --module=~/dataServer/dataServer/src/node_modules/grpc/src/node/extension_binary/node-v64-linux-x64-glibc/grpc_node.node --module_name=grpc_node --module_path=~/dataServer/dataServer/src/node_modules/grpc/src/node/extension_binary/node-v64-linux-x64-glibc --napi_version=4 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v64' (1) node-pre-gyp ERR! stack at ChildProcess. (~/dataServer/dataServer/src/node_modules/grpc/node_modules/node-pre-gyp/lib/util/compile.js:83:29) node-pre-gyp ERR! stack at ChildProcess.emit (events.js:198:13) node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:982:16) node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5) node-pre-gyp ERR! System Linux 3.10.107-1-tlinux2-0048 node-pre-gyp ERR! command "/usr/local/bin/node" "~/dataServer/dataServer/src/node_modules/grpc/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" "--library=static_library" node-pre-gyp ERR! cwd ~/dataServer/dataServer/src/node_modules/grpc node-pre-gyp ERR! node -v v10.16.0 node-pre-gyp ERR! node-pre-gyp -v v0.13.0 node-pre-gyp ERR! not ok npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! grpc@1.24.0 install: `node-pre-gyp install --fallback-to-build --library=static_library` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the grpc@1.24.0 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2019-10-09T11_59_21_558Z-debug.log (2)

dependency tree like below:

➜  DataServer git:(master) ✗ npm ls grpc 
dataserver@1.0.0 ~/DataServer
└─┬ @lag/ad-api@1.2.3
  └─┬ google-ads-api@3.4.2
    └─┬ google-ads-node@1.13.8
      └── grpc@1.24.0 

[huturen]

Fixed it after degrading to "grpc": "1.23.3"

 "dependencies": {
  ...
  "grpc": "1.23.3",
  ...
}

➜  DataServer git:(master) ✗ npm ls grpc 
dataserver@1.0.0 ~/DataServer
├─┬ @lag/ad-api@1.2.3
│ └─┬ google-ads-api@3.4.2
│   └─┬ google-ads-node@1.13.8
│     └── grpc@1.23.3  deduped
└── grpc@1.23.3 

[nuri-engin]

I got similar error for installing grpc@1.24.0 during npm install --save firebase. I just upgrade NodeJS version from v8* to latest v10 and problem solved.

[huturen]

I got similar error for installing grpc@1.24.0 during npm install --save firebase. I just upgrade NodeJS version from v8* to latest v10 and problem solved.

@nuri-engin I got this error on NodeJS version v10.16.0.

Maybe a bug has occurred since version grpc@1.24.0.

[SmirnovM91]

any updates?

[mdenissov]

I got similar error for npm install --save firebase Linux 4.4.0-101-generic node v11.12.0 npm v6.7.0

[Katsukiniwa]

I got same error when tried npm install My local enviroment is

• macOS Mojave version 10.14.6
• node v10.16.0
• npm v6.12.0

Who know how to solve this error ???

[scriptPilot]

Same issue on my side while installing latest Firebase ...

[crudexec]

same issue on my end and its failing on my heroku build.

[micah-akpan]

I fixed this error by downgrading my node version from the latest (13.1.0) to 12.13.0

[matheo]

This error is gone for me without up/downgrading anything I bet it's something about some bundles downloaded while it installs, so it's basically an infrastructure issue.

[VincentMRA]

Any other solutions? I'm still facing this issue. I have node v12.13.0 downgraded dependencies of grpc @1.23.3 This happened for me as well after upgrading to the latest firebase-tools

[santhoshlfms]

Any updates, same issue node version 10.17.0 and version 12.13.1 :(

[konradsofton]

Same issue. Just use Yarn

[AprilPolubiec]

Same issue with node@13.1.0... downgraded to grpc@1.23.3 but still getting the error

[jhimy-michel]

Delete the old node_modules and package.lock.json and then install the latest version for firebase. Hope this would help you. :)

[DmytroMysak]

Same issue with node v12.9.1 Having issue only in google cloud build during integration tests. As a temporary solution skip test.

[shahbazhaidry]

Same issue with node v13.5

[yasirjanjua]

Delete the old node_modules and package.lock.json and then install the latest version for firebase. Hope this would help you. :)

Done it several times. Couldn't find the solution :disappointed:

[frederikocmr]

I have used Yarn instead.

In the folder of my package, where the error was occurring when using npm link

I just deleted the node_modules and package.lock.json and did the following steps:

yarn

yarn build

then

yarn link

all of it worked well.

[StanfordLin]

was having trouble with Firebase cuz firebase needs grpc, so I went to package.json and updated firebase version to the current latest version "7.7.0". Yarn install and I don't see this error anymore

[waqaramjad]

same issue no solution worked

[DaniPB]

I fixed this error by using node v8.17.0

[scolcoin]

Same issue with node@13.1.0 grpc@1.24.0

[itzzmeakhi]

Any updates on this issue?

[scolcoin]

I try to cejecutar hyper fabric 1.4.4 and I have tried several versions of npm and node recommended by the system but the grpc is a problem. at the time of mounting the fabcar npm install the following error comes up npm ERR! code ELIFECYCLE npm ERR! syscall spawn npm ERR! file sh npm ERR! errno ENOENT npm ERR! grpc@1.23.3 install: node-pre-gyp install --fallback-to-build --library=static_library npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the grpc@1.23.3 install script.

I also update and this error comes out: npm install --save firebase npm ERR! code ELIFECYCLE npm ERR! syscall spawn npm ERR! file sh npm ERR! errno ENOENT npm ERR! grpc@1.24.2 install: node-pre-gyp install --fallback-to-build --library=static_library npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the grpc@1.24.2 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. help please!

[JanuaryThomas]

Downgrade the version of Node js

[MrEmanuel]

I found that the problem was that the package request was missing. Installing it before installing grpc fixed my issues. If you have a package depending on grpc, install request first.

yarn add request yarn add grpc

A colleague mentioned that the package "spike" is used if request is not available and that doesn't play nice with the company proxy. Dunno if that's actually the problem, but adding request did fix the issue.

[rupal-simform]

Downgrade the version of Node js

This worked for me. Mac OS Catalina and react-native project

[AndrianD]

Delete the old node_modules and package.lock.json and then install the latest version for firebase. Hope this would help you. :)

Done it several times. Couldn't find the solution 😞

work for me..

[reymalahay]

First off, please do not upgrade/ downgrade your global environment libraries simply because a single library refuses to play nicely, save that as a super-last resort...

Try this:

1. Remove the lock file and the node_modules directory

   rm -rfv package-lock.json node_modules

2. get the latest version of firebase

   npm install --save-exact --save firebase@latest

at the time of writing this, the latest version of firebase was 7.10.0

3. check for vulnerabilities

   npm audit fix

4. then run install

   npm install

It worked for me with this combination:

node version: v13.7.0
npm version: 6.13.6

hth anyone who is still struggling...

[jvandy83]

reymalahay...saved my life.

node version: 13.5.0 npm version: 6.13.4

It worked for me!

[mctata]

Downgrade the version of Node js

@JanuaryThomas Thank you! It did work for me :)

[JanuaryThomas]

First off, please do not upgrade/ downgrade your global environment libraries simply because a single library refuses to play nicely, save that as a super-last resort...

Try this:

1. Remove the lock file and the node_modules directory

rm -rfv package-lock.json node_modules

1. get the latest version of firebase

npm install --save-exact --save firebase@latest

at the time of writing this, the latest version of firebase was 7.10.0

1. check for vulnerabilities

npm audit fix

1. then run install

npm install

It worked for me with this combination:

node version: v13.7.0
npm version: 6.13.6

hth anyone who is still struggling...

Good work around

[SteveRaskin]

@reymalahay Thank you for pointing the way to the exit from today's visit to Dependency Hell

[isabelgk]

I am following the grpc/grpc-web Hello World example.

When I need to npm install grpc, I have the same error with node-pre-gyp. I have tried the suggested changes in grpc, Node, and npm versions without any luck.

13226 verbose pkgid grpc@1.24.2
13227 verbose cwd /home/ubuntu/grpc-web/net/grpc/gateway/examples/helloworld
13228 verbose Linux 4.15.0-96-generic
13229 verbose argv "/usr/bin/node" "/usr/bin/npm" "install"
13230 verbose node v13.12.0
13231 verbose npm  v6.14.4
13232 error code ELIFECYCLE
13233 error errno 6
13234 error grpc@1.24.2 install: `node-pre-gyp install --fallback-to-build --library=static_library`
13234 error Exit status 6
13235 error Failed at the grpc@1.24.2 install script.
13235 error This is probably not a problem with npm. There is likely additional logging output above.

I also found another user having the same issue on StackOverflow.

Any suggestions? I'm on Ubuntu 18.04 and behind a corporate proxy, if that makes a difference.

[reymalahay]

@isabelgk

do an ls -l to see if you have a package-lock.json file. if you do, delete it then run npm install again.

btw, i cloned the example and ran npm install; it works without any changes.

hth

I am following the grpc/grpc-web Hello World example.

When I need to npm install grpc, I have the same error with node-pre-gyp. I have tried the suggested changes in grpc, Node, and npm versions without any luck.

13226 verbose pkgid grpc@1.24.2
13227 verbose cwd /home/ubuntu/grpc-web/net/grpc/gateway/examples/helloworld
13228 verbose Linux 4.15.0-96-generic
13229 verbose argv "/usr/bin/node" "/usr/bin/npm" "install"
13230 verbose node v13.12.0
13231 verbose npm  v6.14.4
13232 error code ELIFECYCLE
13233 error errno 6
13234 error grpc@1.24.2 install: `node-pre-gyp install --fallback-to-build --library=static_library`
13234 error Exit status 6
13235 error Failed at the grpc@1.24.2 install script.
13235 error This is probably not a problem with npm. There is likely additional logging output above.

I also found another user having the same issue on StackOverflow.

Any suggestions? I'm on Ubuntu 18.04 and behind a corporate proxy, if that makes a difference.

[xi1494-jaswantdhayal]

I found that the problem was that the package request was missing. Installing it before installing grpc fixed my issues. If you have a package depending on grpc, install request first.

yarn add request yarn add grpc

A colleague mentioned that the package "spike" is used if request is not available and that doesn't play nice with the company proxy. Dunno if that's actually the problem, but adding request did fix the issue.

This solution is worked for me

[nocraza]

First off, please do not upgrade/ downgrade your global environment libraries simply because a single library refuses to play nicely, save that as a super-last resort...

Try this:

1. Remove the lock file and the node_modules directory

rm -rfv package-lock.json node_modules

1. get the latest version of firebase

npm install --save-exact --save firebase@latest

at the time of writing this, the latest version of firebase was 7.10.0

1. check for vulnerabilities

npm audit fix

1. then run install

npm install

It worked for me with this combination:

node version: v13.7.0
npm version: 6.13.6

hth anyone who is still struggling...

This solution worked for me. I used yarn though.

node version: v13.2.0 yarn version: 1.22.4

[duduwe]

I fixed this error by downgrading my node version from the latest (13.1.0) to 12.13.0

Downgrading also worked for me.

[SoniaKaudjhis]

I have the same issue with Linux 18.04 and node 14.0.0 It seems it can't find the tar file for linux 64-bit arch Using request for node-pre-gyp https download node-pre-gyp WARN Tried to download(404): https://node-precompiled-binaries.grpc.io/grpc/v1.20.2/node-v83-linux-x64-glibc.tar.gz node-pre-gyp WARN Pre-built binaries not found for grpc@1.20.2 and node@14.0.0 (node-v83 ABI, glibc) (falling back to source compile with node

[dipshojol]

First off, please do not upgrade/ downgrade your global environment libraries simply because a single library refuses to play nicely, save that as a super-last resort...

Try this:

1. Remove the lock file and the node_modules directory

rm -rfv package-lock.json node_modules

1. get the latest version of firebase

npm install --save-exact --save firebase@latest

at the time of writing this, the latest version of firebase was 7.10.0

1. check for vulnerabilities

npm audit fix

1. then run install

npm install

It worked for me with this combination:

node version: v13.7.0
npm version: 6.13.6

hth anyone who is still struggling...

worked. thankz

[enigmaticmahesh]

I found that the problem was that the package request was missing. Installing it before installing grpc fixed my issues. If you have a package depending on grpc, install request first. yarn add request yarn add grpc A colleague mentioned that the package "spike" is used if request is not available and that doesn't play nice with the company proxy. Dunno if that's actually the problem, but adding request did fix the issue.

This solution is worked for me

This Worked for me.... thank you

[andrzeij]

I found that the problem was that the package request was missing. Installing it before installing grpc fixed my issues. If you have a package depending on grpc, install request first. yarn add request yarn add grpc A colleague mentioned that the package "spike" is used if request is not available and that doesn't play nice with the company proxy. Dunno if that's actually the problem, but adding request did fix the issue.

This solution is worked for me

This Worked for me.... thank you

Yes this one worked for me to solve heroku failed build .. thank you

[srishab]

First off, please do not upgrade/ downgrade your global environment libraries simply because a single library refuses to play nicely, save that as a super-last resort...

Try this:

1. Remove the lock file and the `node_modules` directory

rm -rfv package-lock.json node_modules

1. get the latest version of `firebase`

npm install --save-exact --save firebase@latest

at the time of writing this, the latest version of firebase was 7.10.0

1. check for vulnerabilities

npm audit fix

1. then run install

npm install

It worked for me with this combination:

node version: v13.7.0
npm version: 6.13.6

hth anyone who is still struggling.

thanks bro

[jimmy30]

First off, please do not upgrade/ downgrade your global environment libraries simply because a single library refuses to play nicely, save that as a super-last resort...

Try this:

1. Remove the lock file and the node_modules directory

rm -rfv package-lock.json node_modules

1. get the latest version of firebase

npm install --save-exact --save firebase@latest

at the time of writing this, the latest version of firebase was 7.10.0

1. check for vulnerabilities

npm audit fix

1. then run install

npm install

It worked for me with this combination:

node version: v13.7.0
npm version: 6.13.6

hth anyone who is still struggling...

Great, this worked. Thanks

[JPSantistebanQ]

Fixed downgrade to Node LTS last version 12.18.2

[codehunter1992]

Delete the old node_modules and package.lock.json and then install the latest version for firebase. Hope this would help you. :)

This is working well for me :) 👍

[jnisperuza]

First off, please do not upgrade/ downgrade your global environment libraries simply because a single library refuses to play nicely, save that as a super-last resort...

Try this:

1. Remove the lock file and the node_modules directory

rm -rfv package-lock.json node_modules

1. get the latest version of firebase

npm install --save-exact --save firebase@latest

at the time of writing this, the latest version of firebase was 7.10.0

1. check for vulnerabilities

npm audit fix

1. then run install

npm install

It worked for me with this combination:

node version: v13.7.0
npm version: 6.13.6

hth anyone who is still struggling...

This really works

[luckydevboy]

In package.json firebase version fixed to 7.5.2 "firebase": "7.5.2". I set it to be updated to the latest version "firebase": "^7.5.2" but before doing that I removed the node_modules folder and package-lock.json. Now get rid of the error.

[kennyish1173]

Delete the old node_modules and package.lock.json and then install the latest version for firebase. Hope this would help you. :)

This worked for me too! Thank you so mucho!

node version: v12.18.3
npm version: 6.14.6