Expo error when trying to global install CLI after update












0















After I started Expo, I got the message I was running an a older version of the client and asked me to run npm install -g expo-cli , so I foolishly did.



After the install was finished I ran expo start and got the following question:



This command requires Expo CLI.
Do you want to install it globally [Y/n]?


To what I replied with: Y and got the following respond:



Installing the package 'expo-cli'...
events.js:167
throw er; // Unhandled 'error' event
^

Error: spawn npm ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:229:19)
at onErrorNT (internal/child_process.js:406:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:235:12)
at onErrorNT (internal/child_process.js:406:16)
at process._tickCallback (internal/process/next_tick.js:63:19)


I've tried:



expo diagnostics


But am met with the same response.



Anyone knows how I can solve this problem?










share|improve this question



























    0















    After I started Expo, I got the message I was running an a older version of the client and asked me to run npm install -g expo-cli , so I foolishly did.



    After the install was finished I ran expo start and got the following question:



    This command requires Expo CLI.
    Do you want to install it globally [Y/n]?


    To what I replied with: Y and got the following respond:



    Installing the package 'expo-cli'...
    events.js:167
    throw er; // Unhandled 'error' event
    ^

    Error: spawn npm ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:229:19)
    at onErrorNT (internal/child_process.js:406:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)
    Emitted 'error' event at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:235:12)
    at onErrorNT (internal/child_process.js:406:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)


    I've tried:



    expo diagnostics


    But am met with the same response.



    Anyone knows how I can solve this problem?










    share|improve this question

























      0












      0








      0








      After I started Expo, I got the message I was running an a older version of the client and asked me to run npm install -g expo-cli , so I foolishly did.



      After the install was finished I ran expo start and got the following question:



      This command requires Expo CLI.
      Do you want to install it globally [Y/n]?


      To what I replied with: Y and got the following respond:



      Installing the package 'expo-cli'...
      events.js:167
      throw er; // Unhandled 'error' event
      ^

      Error: spawn npm ENOENT
      at Process.ChildProcess._handle.onexit (internal/child_process.js:229:19)
      at onErrorNT (internal/child_process.js:406:16)
      at process._tickCallback (internal/process/next_tick.js:63:19)
      Emitted 'error' event at:
      at Process.ChildProcess._handle.onexit (internal/child_process.js:235:12)
      at onErrorNT (internal/child_process.js:406:16)
      at process._tickCallback (internal/process/next_tick.js:63:19)


      I've tried:



      expo diagnostics


      But am met with the same response.



      Anyone knows how I can solve this problem?










      share|improve this question














      After I started Expo, I got the message I was running an a older version of the client and asked me to run npm install -g expo-cli , so I foolishly did.



      After the install was finished I ran expo start and got the following question:



      This command requires Expo CLI.
      Do you want to install it globally [Y/n]?


      To what I replied with: Y and got the following respond:



      Installing the package 'expo-cli'...
      events.js:167
      throw er; // Unhandled 'error' event
      ^

      Error: spawn npm ENOENT
      at Process.ChildProcess._handle.onexit (internal/child_process.js:229:19)
      at onErrorNT (internal/child_process.js:406:16)
      at process._tickCallback (internal/process/next_tick.js:63:19)
      Emitted 'error' event at:
      at Process.ChildProcess._handle.onexit (internal/child_process.js:235:12)
      at onErrorNT (internal/child_process.js:406:16)
      at process._tickCallback (internal/process/next_tick.js:63:19)


      I've tried:



      expo diagnostics


      But am met with the same response.



      Anyone knows how I can solve this problem?







      expo






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 18 '18 at 17:37









      SalmanSalman

      29219




      29219
























          2 Answers
          2






          active

          oldest

          votes


















          0














          I restarted my laptop and ran npm install -g expo-cli this somehow solved the problem.






          share|improve this answer































            -1














            A quick around would be to remove expo and expo.cmd in node_modules/.bin since it seems to be using the expo in node_modules/.bin and not the global one.






            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',
              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%2f53363716%2fexpo-error-when-trying-to-global-install-cli-after-update%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









              0














              I restarted my laptop and ran npm install -g expo-cli this somehow solved the problem.






              share|improve this answer




























                0














                I restarted my laptop and ran npm install -g expo-cli this somehow solved the problem.






                share|improve this answer


























                  0












                  0








                  0







                  I restarted my laptop and ran npm install -g expo-cli this somehow solved the problem.






                  share|improve this answer













                  I restarted my laptop and ran npm install -g expo-cli this somehow solved the problem.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Dec 6 '18 at 11:30









                  SalmanSalman

                  29219




                  29219

























                      -1














                      A quick around would be to remove expo and expo.cmd in node_modules/.bin since it seems to be using the expo in node_modules/.bin and not the global one.






                      share|improve this answer




























                        -1














                        A quick around would be to remove expo and expo.cmd in node_modules/.bin since it seems to be using the expo in node_modules/.bin and not the global one.






                        share|improve this answer


























                          -1












                          -1








                          -1







                          A quick around would be to remove expo and expo.cmd in node_modules/.bin since it seems to be using the expo in node_modules/.bin and not the global one.






                          share|improve this answer













                          A quick around would be to remove expo and expo.cmd in node_modules/.bin since it seems to be using the expo in node_modules/.bin and not the global one.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Nov 18 '18 at 18:01









                          Beth MwangiBeth Mwangi

                          12




                          12






























                              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%2f53363716%2fexpo-error-when-trying-to-global-install-cli-after-update%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







                              這個網誌中的熱門文章

                              Xamarin.form Move up view when keyboard appear

                              Post-Redirect-Get with Spring WebFlux and Thymeleaf

                              Anylogic : not able to use stopDelay()