“Failed to load gRPC binary module because it was not installed for the current system” Only on windows












0















I am having above error when I am trying to run my packaged app on windows. It works perfectly fine on linux.



Expected directory: electron-v2.0-win32-ia32-unknown
Found: node-v57-linux-x64-glibc


This is where expected directory was supposed to be:



"/node_modules/grpc/src/node/extension_binary/node-v57-linux-x64-glibc/grpc_node.node"


package.json



    "dependencies": {
"electron": "^2.0.10",
"firebase": "^5.5.2",
"material-design-lite": "^1.3.0"
},
"devDependencies": {
"electron-packager": "^12.2.0",
"electron-rebuild": "^1.8.2"
}


Things I tried:




  • Rebuid

  • This question


Let me know if you need any other detail.










share|improve this question



























    0















    I am having above error when I am trying to run my packaged app on windows. It works perfectly fine on linux.



    Expected directory: electron-v2.0-win32-ia32-unknown
    Found: node-v57-linux-x64-glibc


    This is where expected directory was supposed to be:



    "/node_modules/grpc/src/node/extension_binary/node-v57-linux-x64-glibc/grpc_node.node"


    package.json



        "dependencies": {
    "electron": "^2.0.10",
    "firebase": "^5.5.2",
    "material-design-lite": "^1.3.0"
    },
    "devDependencies": {
    "electron-packager": "^12.2.0",
    "electron-rebuild": "^1.8.2"
    }


    Things I tried:




    • Rebuid

    • This question


    Let me know if you need any other detail.










    share|improve this question

























      0












      0








      0








      I am having above error when I am trying to run my packaged app on windows. It works perfectly fine on linux.



      Expected directory: electron-v2.0-win32-ia32-unknown
      Found: node-v57-linux-x64-glibc


      This is where expected directory was supposed to be:



      "/node_modules/grpc/src/node/extension_binary/node-v57-linux-x64-glibc/grpc_node.node"


      package.json



          "dependencies": {
      "electron": "^2.0.10",
      "firebase": "^5.5.2",
      "material-design-lite": "^1.3.0"
      },
      "devDependencies": {
      "electron-packager": "^12.2.0",
      "electron-rebuild": "^1.8.2"
      }


      Things I tried:




      • Rebuid

      • This question


      Let me know if you need any other detail.










      share|improve this question














      I am having above error when I am trying to run my packaged app on windows. It works perfectly fine on linux.



      Expected directory: electron-v2.0-win32-ia32-unknown
      Found: node-v57-linux-x64-glibc


      This is where expected directory was supposed to be:



      "/node_modules/grpc/src/node/extension_binary/node-v57-linux-x64-glibc/grpc_node.node"


      package.json



          "dependencies": {
      "electron": "^2.0.10",
      "firebase": "^5.5.2",
      "material-design-lite": "^1.3.0"
      },
      "devDependencies": {
      "electron-packager": "^12.2.0",
      "electron-rebuild": "^1.8.2"
      }


      Things I tried:




      • Rebuid

      • This question


      Let me know if you need any other detail.







      npm electron






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 13 '18 at 8:37









      LcukerdLcukerd

      18512




      18512
























          1 Answer
          1






          active

          oldest

          votes


















          2














          You have to rebuild the package in your Electron's version.
          For example, here is the command I use to rebuild my C++ package for my Electron App :



          npm rebuild --runtime=electron --target=2.0.11 --disturl=https://atom.io/download/electron --abi=57


          You have to say to npm rebuild the runtime (electron in this case), the version target you want (2.0.11 in my case), the disturl is used to download Electron release and finally the ABI of your Electron's version (you can get this with this command: electron --abi)



          Hope this can help you :)



          [EDIT]



          Here the command to have ABI version with Electron installed in global:
          Screenshot Electron



          Or here when I want the Electron's version & ABI installed in my project:
          Screenshot Electron






          share|improve this answer


























          • electron --abi is not recognized as a command.

            – Lcukerd
            Nov 19 '18 at 18:05











          • If you don't have Electron installed in global, it's normal, so use "npx electron --abi" in your project with Electron, or install it in global "npm i -g electron"

            – Toinane
            Nov 20 '18 at 9:14











          • For the Electron v2.0, its ABI is 57

            – Toinane
            Nov 20 '18 at 9:26











          • I now get Found: [electron-v3.0-linux-x64-glibc,node-v64-linux-x64-glibc]. I removed node_modules and install 3.0.10 this time.

            – Lcukerd
            Nov 20 '18 at 10:10











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53276898%2ffailed-to-load-grpc-binary-module-because-it-was-not-installed-for-the-current%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2














          You have to rebuild the package in your Electron's version.
          For example, here is the command I use to rebuild my C++ package for my Electron App :



          npm rebuild --runtime=electron --target=2.0.11 --disturl=https://atom.io/download/electron --abi=57


          You have to say to npm rebuild the runtime (electron in this case), the version target you want (2.0.11 in my case), the disturl is used to download Electron release and finally the ABI of your Electron's version (you can get this with this command: electron --abi)



          Hope this can help you :)



          [EDIT]



          Here the command to have ABI version with Electron installed in global:
          Screenshot Electron



          Or here when I want the Electron's version & ABI installed in my project:
          Screenshot Electron






          share|improve this answer


























          • electron --abi is not recognized as a command.

            – Lcukerd
            Nov 19 '18 at 18:05











          • If you don't have Electron installed in global, it's normal, so use "npx electron --abi" in your project with Electron, or install it in global "npm i -g electron"

            – Toinane
            Nov 20 '18 at 9:14











          • For the Electron v2.0, its ABI is 57

            – Toinane
            Nov 20 '18 at 9:26











          • I now get Found: [electron-v3.0-linux-x64-glibc,node-v64-linux-x64-glibc]. I removed node_modules and install 3.0.10 this time.

            – Lcukerd
            Nov 20 '18 at 10:10
















          2














          You have to rebuild the package in your Electron's version.
          For example, here is the command I use to rebuild my C++ package for my Electron App :



          npm rebuild --runtime=electron --target=2.0.11 --disturl=https://atom.io/download/electron --abi=57


          You have to say to npm rebuild the runtime (electron in this case), the version target you want (2.0.11 in my case), the disturl is used to download Electron release and finally the ABI of your Electron's version (you can get this with this command: electron --abi)



          Hope this can help you :)



          [EDIT]



          Here the command to have ABI version with Electron installed in global:
          Screenshot Electron



          Or here when I want the Electron's version & ABI installed in my project:
          Screenshot Electron






          share|improve this answer


























          • electron --abi is not recognized as a command.

            – Lcukerd
            Nov 19 '18 at 18:05











          • If you don't have Electron installed in global, it's normal, so use "npx electron --abi" in your project with Electron, or install it in global "npm i -g electron"

            – Toinane
            Nov 20 '18 at 9:14











          • For the Electron v2.0, its ABI is 57

            – Toinane
            Nov 20 '18 at 9:26











          • I now get Found: [electron-v3.0-linux-x64-glibc,node-v64-linux-x64-glibc]. I removed node_modules and install 3.0.10 this time.

            – Lcukerd
            Nov 20 '18 at 10:10














          2












          2








          2







          You have to rebuild the package in your Electron's version.
          For example, here is the command I use to rebuild my C++ package for my Electron App :



          npm rebuild --runtime=electron --target=2.0.11 --disturl=https://atom.io/download/electron --abi=57


          You have to say to npm rebuild the runtime (electron in this case), the version target you want (2.0.11 in my case), the disturl is used to download Electron release and finally the ABI of your Electron's version (you can get this with this command: electron --abi)



          Hope this can help you :)



          [EDIT]



          Here the command to have ABI version with Electron installed in global:
          Screenshot Electron



          Or here when I want the Electron's version & ABI installed in my project:
          Screenshot Electron






          share|improve this answer















          You have to rebuild the package in your Electron's version.
          For example, here is the command I use to rebuild my C++ package for my Electron App :



          npm rebuild --runtime=electron --target=2.0.11 --disturl=https://atom.io/download/electron --abi=57


          You have to say to npm rebuild the runtime (electron in this case), the version target you want (2.0.11 in my case), the disturl is used to download Electron release and finally the ABI of your Electron's version (you can get this with this command: electron --abi)



          Hope this can help you :)



          [EDIT]



          Here the command to have ABI version with Electron installed in global:
          Screenshot Electron



          Or here when I want the Electron's version & ABI installed in my project:
          Screenshot Electron







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 20 '18 at 9:22

























          answered Nov 19 '18 at 10:56









          ToinaneToinane

          214




          214













          • electron --abi is not recognized as a command.

            – Lcukerd
            Nov 19 '18 at 18:05











          • If you don't have Electron installed in global, it's normal, so use "npx electron --abi" in your project with Electron, or install it in global "npm i -g electron"

            – Toinane
            Nov 20 '18 at 9:14











          • For the Electron v2.0, its ABI is 57

            – Toinane
            Nov 20 '18 at 9:26











          • I now get Found: [electron-v3.0-linux-x64-glibc,node-v64-linux-x64-glibc]. I removed node_modules and install 3.0.10 this time.

            – Lcukerd
            Nov 20 '18 at 10:10



















          • electron --abi is not recognized as a command.

            – Lcukerd
            Nov 19 '18 at 18:05











          • If you don't have Electron installed in global, it's normal, so use "npx electron --abi" in your project with Electron, or install it in global "npm i -g electron"

            – Toinane
            Nov 20 '18 at 9:14











          • For the Electron v2.0, its ABI is 57

            – Toinane
            Nov 20 '18 at 9:26











          • I now get Found: [electron-v3.0-linux-x64-glibc,node-v64-linux-x64-glibc]. I removed node_modules and install 3.0.10 this time.

            – Lcukerd
            Nov 20 '18 at 10:10

















          electron --abi is not recognized as a command.

          – Lcukerd
          Nov 19 '18 at 18:05





          electron --abi is not recognized as a command.

          – Lcukerd
          Nov 19 '18 at 18:05













          If you don't have Electron installed in global, it's normal, so use "npx electron --abi" in your project with Electron, or install it in global "npm i -g electron"

          – Toinane
          Nov 20 '18 at 9:14





          If you don't have Electron installed in global, it's normal, so use "npx electron --abi" in your project with Electron, or install it in global "npm i -g electron"

          – Toinane
          Nov 20 '18 at 9:14













          For the Electron v2.0, its ABI is 57

          – Toinane
          Nov 20 '18 at 9:26





          For the Electron v2.0, its ABI is 57

          – Toinane
          Nov 20 '18 at 9:26













          I now get Found: [electron-v3.0-linux-x64-glibc,node-v64-linux-x64-glibc]. I removed node_modules and install 3.0.10 this time.

          – Lcukerd
          Nov 20 '18 at 10:10





          I now get Found: [electron-v3.0-linux-x64-glibc,node-v64-linux-x64-glibc]. I removed node_modules and install 3.0.10 this time.

          – Lcukerd
          Nov 20 '18 at 10:10


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53276898%2ffailed-to-load-grpc-binary-module-because-it-was-not-installed-for-the-current%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Florida Star v. B. J. F.

          Danny Elfman

          Retrieve a Users Dashboard in Tumblr with R and TumblR. Oauth Issues