Error: Failed to load gRPC binary module because it was not installed for the current system
See original GitHub issueI follow the instructions here https://firebase.google.com/docs/cli#npm
I run npm install -g firebase-tools
, login and then run firebase serve
and receive the following error
Error: Failed to load gRPC binary module because it was not installed for the current system Expected directory: node-v57-darwin-x64-unknown Found: [node-v64-darwin-x64-unknown]
Ive tried running npm rebuild
as suggested on other threads and on stack exchange but the error persists. Any ideas of what can be done to fix this. I’ve tried uninstalling and reinstalling the node_modules
but still the problem persists. Any ideas of what can be done.
I’m running npm version 6.9.0 Firebase CLI version 7.5.0 MacOS Catalina 10.15
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:7 (5 by maintainers)
Top Results From Across the Web
NodeJs Error - Failed to load gRPC binary module because it ...
This typically happens when "npm install" is run locally rather than in the container. Any differences, OS, node version become a conflict as ......
Read more >Getting Failed to load gRPC binary error (with either node v12 ...
Hi, I'm working on an application that runs fine locally, but when running through docker I constantly get this error. web_1 | Error:...
Read more >https://support.codefresh.io/hc/en-us/articles/360...
No information is available for this page.
Read more >"Failed to load gRPC binary module" Error
Why am I getting the "Failed to load gRPC binary module" error when running ... load gRPC binary module because it was not...
Read more >Node.js – NodeJs Error – Failed to load gRPC binary module ...
Node.js – NodeJs Error – Failed to load gRPC binary module because it was not installed for the current system Expected directory. grpcnode.js....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
So, I don’t know all of the details I’m talking about here, but my understanding is that Catalina separated user and system space on the file system and things that attempt to cross those boundaries have some odd behaviors.
I don’t have a setup to test this now myself, but I may be able to look into it later. What I would recommend for you:
firebase-tools
and going about your workflow. (There’s a second option here that you may need to give Node JS full access to your file system or something, but I’m not 100% sure how to advice this).firebase-tools
and go about your workflow.Let me know if that works for you!
Since there haven’t been any recent updates here, I am going to close this issue.
@TOMZACH if you’re still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.