Unable to install Firebase in ionic 4 on OS X











up vote
0
down vote

favorite












Followed instructions in Firebase documentation and executed:



sudo npm install firebase --save


I am getting the following errors. Any help would be appreciated. Previously I have successfully installed firebase on ionic 3. However, this may have nothing to do with ionic.



1564 verbose Darwin 18.2.0
1565 verbose argv "/usr/local/bin/node" "/Users/syedtariq/.npm-global/bin/npm" "install"
1566 verbose node v11.0.0
1567 verbose npm v6.4.1
1568 error code ELIFECYCLE
1569 error errno 1
1570 error grpc@1.16.0 install: `node-pre-gyp install --fallback-to-build --library=static_library`
1570 error Exit status 1
1571 error Failed at the grpc@1.16.0 install script.
1571 error This is probably not a problem with npm. There is likely additional logging output above.
1572 verbose exit [ 1, true ]









share|improve this question




























    up vote
    0
    down vote

    favorite












    Followed instructions in Firebase documentation and executed:



    sudo npm install firebase --save


    I am getting the following errors. Any help would be appreciated. Previously I have successfully installed firebase on ionic 3. However, this may have nothing to do with ionic.



    1564 verbose Darwin 18.2.0
    1565 verbose argv "/usr/local/bin/node" "/Users/syedtariq/.npm-global/bin/npm" "install"
    1566 verbose node v11.0.0
    1567 verbose npm v6.4.1
    1568 error code ELIFECYCLE
    1569 error errno 1
    1570 error grpc@1.16.0 install: `node-pre-gyp install --fallback-to-build --library=static_library`
    1570 error Exit status 1
    1571 error Failed at the grpc@1.16.0 install script.
    1571 error This is probably not a problem with npm. There is likely additional logging output above.
    1572 verbose exit [ 1, true ]









    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      Followed instructions in Firebase documentation and executed:



      sudo npm install firebase --save


      I am getting the following errors. Any help would be appreciated. Previously I have successfully installed firebase on ionic 3. However, this may have nothing to do with ionic.



      1564 verbose Darwin 18.2.0
      1565 verbose argv "/usr/local/bin/node" "/Users/syedtariq/.npm-global/bin/npm" "install"
      1566 verbose node v11.0.0
      1567 verbose npm v6.4.1
      1568 error code ELIFECYCLE
      1569 error errno 1
      1570 error grpc@1.16.0 install: `node-pre-gyp install --fallback-to-build --library=static_library`
      1570 error Exit status 1
      1571 error Failed at the grpc@1.16.0 install script.
      1571 error This is probably not a problem with npm. There is likely additional logging output above.
      1572 verbose exit [ 1, true ]









      share|improve this question















      Followed instructions in Firebase documentation and executed:



      sudo npm install firebase --save


      I am getting the following errors. Any help would be appreciated. Previously I have successfully installed firebase on ionic 3. However, this may have nothing to do with ionic.



      1564 verbose Darwin 18.2.0
      1565 verbose argv "/usr/local/bin/node" "/Users/syedtariq/.npm-global/bin/npm" "install"
      1566 verbose node v11.0.0
      1567 verbose npm v6.4.1
      1568 error code ELIFECYCLE
      1569 error errno 1
      1570 error grpc@1.16.0 install: `node-pre-gyp install --fallback-to-build --library=static_library`
      1570 error Exit status 1
      1571 error Failed at the grpc@1.16.0 install script.
      1571 error This is probably not a problem with npm. There is likely additional logging output above.
      1572 verbose exit [ 1, true ]






      firebase ionic-framework npm






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 11 at 15:10









      Frank van Puffelen

      223k25363389




      223k25363389










      asked Nov 11 at 15:05









      Syed Tariq

      1,82612028




      1,82612028
























          2 Answers
          2






          active

          oldest

          votes

















          up vote
          2
          down vote



          accepted










          It fails because it cannot install the native C++ gRCP add-on. Try to use the grcp-node module instead which does not require native C++ addon.



          edit: grpc has some issues with node@11 see: issue You need to downgrade to node@10






          share|improve this answer























          • Thank you for the suggestion. I am not sure how to fix this issue. It works fine when I build an ionic 3 app. On the ionc 3 app, the file package.json has no reference to grpc. The package-lock.json has a reference to grpc version 1.13.1.
            – Syed Tariq
            Nov 11 at 15:49










          • Some of your primary dependency requires it. Do you say, that you can build your app on different platform, but when you try to build on your laptop it fails?
            – lependu
            Nov 11 at 15:56












          • I am only building on a macbook pro with macOD Mojave Vesion 10.14.2 Beta. As I indicated, the installation works fine if I use ionic 3.
            – Syed Tariq
            Nov 11 at 16:11










          • Correction: I am having the problem BOTH on ionic 3 and 4. This suggests that something changed in my environment. It may have been triggered by an OS update. I will try reverting to a previous OS version and see it it helps.
            – Syed Tariq
            Nov 11 at 16:35










          • what node version do you use? Ah I see, it is node@11 I edited my answer, you need to downgrade to node@10
            – lependu
            Nov 11 at 16:36




















          up vote
          0
          down vote













          another solutionThis is an issue that is very widely issued on the github site by numerous persons. The solution recommended by lependu (falling back to an LTS version of node) worked in one project. In another project a similar error started when I did a 'sudo npm install'. Very frustrating. I finally found an additional solution which worked: enter link description here. It required me to add to the npm install command as follows:



          sudo npm install --unsafe-perm=true --allow-root





          share|improve this answer





















            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',
            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%2f53250028%2funable-to-install-firebase-in-ionic-4-on-os-x%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            2
            down vote



            accepted










            It fails because it cannot install the native C++ gRCP add-on. Try to use the grcp-node module instead which does not require native C++ addon.



            edit: grpc has some issues with node@11 see: issue You need to downgrade to node@10






            share|improve this answer























            • Thank you for the suggestion. I am not sure how to fix this issue. It works fine when I build an ionic 3 app. On the ionc 3 app, the file package.json has no reference to grpc. The package-lock.json has a reference to grpc version 1.13.1.
              – Syed Tariq
              Nov 11 at 15:49










            • Some of your primary dependency requires it. Do you say, that you can build your app on different platform, but when you try to build on your laptop it fails?
              – lependu
              Nov 11 at 15:56












            • I am only building on a macbook pro with macOD Mojave Vesion 10.14.2 Beta. As I indicated, the installation works fine if I use ionic 3.
              – Syed Tariq
              Nov 11 at 16:11










            • Correction: I am having the problem BOTH on ionic 3 and 4. This suggests that something changed in my environment. It may have been triggered by an OS update. I will try reverting to a previous OS version and see it it helps.
              – Syed Tariq
              Nov 11 at 16:35










            • what node version do you use? Ah I see, it is node@11 I edited my answer, you need to downgrade to node@10
              – lependu
              Nov 11 at 16:36

















            up vote
            2
            down vote



            accepted










            It fails because it cannot install the native C++ gRCP add-on. Try to use the grcp-node module instead which does not require native C++ addon.



            edit: grpc has some issues with node@11 see: issue You need to downgrade to node@10






            share|improve this answer























            • Thank you for the suggestion. I am not sure how to fix this issue. It works fine when I build an ionic 3 app. On the ionc 3 app, the file package.json has no reference to grpc. The package-lock.json has a reference to grpc version 1.13.1.
              – Syed Tariq
              Nov 11 at 15:49










            • Some of your primary dependency requires it. Do you say, that you can build your app on different platform, but when you try to build on your laptop it fails?
              – lependu
              Nov 11 at 15:56












            • I am only building on a macbook pro with macOD Mojave Vesion 10.14.2 Beta. As I indicated, the installation works fine if I use ionic 3.
              – Syed Tariq
              Nov 11 at 16:11










            • Correction: I am having the problem BOTH on ionic 3 and 4. This suggests that something changed in my environment. It may have been triggered by an OS update. I will try reverting to a previous OS version and see it it helps.
              – Syed Tariq
              Nov 11 at 16:35










            • what node version do you use? Ah I see, it is node@11 I edited my answer, you need to downgrade to node@10
              – lependu
              Nov 11 at 16:36















            up vote
            2
            down vote



            accepted







            up vote
            2
            down vote



            accepted






            It fails because it cannot install the native C++ gRCP add-on. Try to use the grcp-node module instead which does not require native C++ addon.



            edit: grpc has some issues with node@11 see: issue You need to downgrade to node@10






            share|improve this answer














            It fails because it cannot install the native C++ gRCP add-on. Try to use the grcp-node module instead which does not require native C++ addon.



            edit: grpc has some issues with node@11 see: issue You need to downgrade to node@10







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Nov 12 at 9:18

























            answered Nov 11 at 15:16









            lependu

            669314




            669314












            • Thank you for the suggestion. I am not sure how to fix this issue. It works fine when I build an ionic 3 app. On the ionc 3 app, the file package.json has no reference to grpc. The package-lock.json has a reference to grpc version 1.13.1.
              – Syed Tariq
              Nov 11 at 15:49










            • Some of your primary dependency requires it. Do you say, that you can build your app on different platform, but when you try to build on your laptop it fails?
              – lependu
              Nov 11 at 15:56












            • I am only building on a macbook pro with macOD Mojave Vesion 10.14.2 Beta. As I indicated, the installation works fine if I use ionic 3.
              – Syed Tariq
              Nov 11 at 16:11










            • Correction: I am having the problem BOTH on ionic 3 and 4. This suggests that something changed in my environment. It may have been triggered by an OS update. I will try reverting to a previous OS version and see it it helps.
              – Syed Tariq
              Nov 11 at 16:35










            • what node version do you use? Ah I see, it is node@11 I edited my answer, you need to downgrade to node@10
              – lependu
              Nov 11 at 16:36




















            • Thank you for the suggestion. I am not sure how to fix this issue. It works fine when I build an ionic 3 app. On the ionc 3 app, the file package.json has no reference to grpc. The package-lock.json has a reference to grpc version 1.13.1.
              – Syed Tariq
              Nov 11 at 15:49










            • Some of your primary dependency requires it. Do you say, that you can build your app on different platform, but when you try to build on your laptop it fails?
              – lependu
              Nov 11 at 15:56












            • I am only building on a macbook pro with macOD Mojave Vesion 10.14.2 Beta. As I indicated, the installation works fine if I use ionic 3.
              – Syed Tariq
              Nov 11 at 16:11










            • Correction: I am having the problem BOTH on ionic 3 and 4. This suggests that something changed in my environment. It may have been triggered by an OS update. I will try reverting to a previous OS version and see it it helps.
              – Syed Tariq
              Nov 11 at 16:35










            • what node version do you use? Ah I see, it is node@11 I edited my answer, you need to downgrade to node@10
              – lependu
              Nov 11 at 16:36


















            Thank you for the suggestion. I am not sure how to fix this issue. It works fine when I build an ionic 3 app. On the ionc 3 app, the file package.json has no reference to grpc. The package-lock.json has a reference to grpc version 1.13.1.
            – Syed Tariq
            Nov 11 at 15:49




            Thank you for the suggestion. I am not sure how to fix this issue. It works fine when I build an ionic 3 app. On the ionc 3 app, the file package.json has no reference to grpc. The package-lock.json has a reference to grpc version 1.13.1.
            – Syed Tariq
            Nov 11 at 15:49












            Some of your primary dependency requires it. Do you say, that you can build your app on different platform, but when you try to build on your laptop it fails?
            – lependu
            Nov 11 at 15:56






            Some of your primary dependency requires it. Do you say, that you can build your app on different platform, but when you try to build on your laptop it fails?
            – lependu
            Nov 11 at 15:56














            I am only building on a macbook pro with macOD Mojave Vesion 10.14.2 Beta. As I indicated, the installation works fine if I use ionic 3.
            – Syed Tariq
            Nov 11 at 16:11




            I am only building on a macbook pro with macOD Mojave Vesion 10.14.2 Beta. As I indicated, the installation works fine if I use ionic 3.
            – Syed Tariq
            Nov 11 at 16:11












            Correction: I am having the problem BOTH on ionic 3 and 4. This suggests that something changed in my environment. It may have been triggered by an OS update. I will try reverting to a previous OS version and see it it helps.
            – Syed Tariq
            Nov 11 at 16:35




            Correction: I am having the problem BOTH on ionic 3 and 4. This suggests that something changed in my environment. It may have been triggered by an OS update. I will try reverting to a previous OS version and see it it helps.
            – Syed Tariq
            Nov 11 at 16:35












            what node version do you use? Ah I see, it is node@11 I edited my answer, you need to downgrade to node@10
            – lependu
            Nov 11 at 16:36






            what node version do you use? Ah I see, it is node@11 I edited my answer, you need to downgrade to node@10
            – lependu
            Nov 11 at 16:36














            up vote
            0
            down vote













            another solutionThis is an issue that is very widely issued on the github site by numerous persons. The solution recommended by lependu (falling back to an LTS version of node) worked in one project. In another project a similar error started when I did a 'sudo npm install'. Very frustrating. I finally found an additional solution which worked: enter link description here. It required me to add to the npm install command as follows:



            sudo npm install --unsafe-perm=true --allow-root





            share|improve this answer

























              up vote
              0
              down vote













              another solutionThis is an issue that is very widely issued on the github site by numerous persons. The solution recommended by lependu (falling back to an LTS version of node) worked in one project. In another project a similar error started when I did a 'sudo npm install'. Very frustrating. I finally found an additional solution which worked: enter link description here. It required me to add to the npm install command as follows:



              sudo npm install --unsafe-perm=true --allow-root





              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                another solutionThis is an issue that is very widely issued on the github site by numerous persons. The solution recommended by lependu (falling back to an LTS version of node) worked in one project. In another project a similar error started when I did a 'sudo npm install'. Very frustrating. I finally found an additional solution which worked: enter link description here. It required me to add to the npm install command as follows:



                sudo npm install --unsafe-perm=true --allow-root





                share|improve this answer












                another solutionThis is an issue that is very widely issued on the github site by numerous persons. The solution recommended by lependu (falling back to an LTS version of node) worked in one project. In another project a similar error started when I did a 'sudo npm install'. Very frustrating. I finally found an additional solution which worked: enter link description here. It required me to add to the npm install command as follows:



                sudo npm install --unsafe-perm=true --allow-root






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 13 at 20:18









                Syed Tariq

                1,82612028




                1,82612028






























                    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.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • 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%2f53250028%2funable-to-install-firebase-in-ionic-4-on-os-x%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

                    Full-time equivalent

                    Bicuculline

                    さくらももこ