How to fix wanted: {“node”:“>=4”} (current: {“node”:“0.10.25”,“npm”:“1.4.21”}) on...












2















When i tried to install npm install -g react-native-cli
then i faced an error like below :



npm WARN engine react-native-cli@1.0.0: wanted: {"node":">=4"} (current: {"node":"0.10.25","npm":"1.4.21"})
npm ERR! tar.unpack untar error /home/putuguna/.npm/react-native-cli/1.0.0/package.tgz
npm ERR! Error: EACCES, mkdir '/usr/local/lib/node_modules'
npm ERR! { [Error: EACCES, mkdir '/usr/local/lib/node_modules']
npm ERR! errno: 3,
npm ERR! code: 'EACCES',
npm ERR! path: '/usr/local/lib/node_modules',
npm ERR! fstream_type: 'Directory',
npm ERR! fstream_path: '/usr/local/lib/node_modules/react-native-cli',
npm ERR! fstream_class: 'DirWriter',
npm ERR! fstream_stack:
npm ERR! [ '/usr/lib/nodejs/fstream/lib/writer.js:171:23',
npm ERR! '/usr/lib/nodejs/mkdirp/index.js:46:53',
npm ERR! 'Object.oncomplete (fs.js:107:15)' ] }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! System Linux 4.2.0-16-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "react-native-cli"
npm ERR! cwd /home/putuguna
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.4.21
npm ERR! path /usr/local/lib/node_modules
npm ERR! fstream_path /usr/local/lib/node_modules/react-native-cli
npm ERR! fstream_type Directory
npm ERR! fstream_class DirWriter
npm ERR! code EACCES
npm ERR! errno 3
npm ERR! stack Error: EACCES, mkdir '/usr/local/lib/node_modules'
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:171:23
npm ERR! fstream_stack /usr/lib/nodejs/mkdirp/index.js:46:53
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/putuguna/npm-debug.log
npm ERR! not ok code 0


Could you help me for solve my problem



Update :



One thing that i know, i should update my node js version. I have done, by this way :



curl -sL https://deb.nodesource.com/setup_4.x | sudo -E bash -
sudo apt-get install -y nodejs


But the error above appears again. please help










share|improve this question

























  • Consider installing Node 6.x instead of Node 4.x. askubuntu.com/questions/786272/…

    – Thomas Ward
    Oct 7 '16 at 19:41
















2















When i tried to install npm install -g react-native-cli
then i faced an error like below :



npm WARN engine react-native-cli@1.0.0: wanted: {"node":">=4"} (current: {"node":"0.10.25","npm":"1.4.21"})
npm ERR! tar.unpack untar error /home/putuguna/.npm/react-native-cli/1.0.0/package.tgz
npm ERR! Error: EACCES, mkdir '/usr/local/lib/node_modules'
npm ERR! { [Error: EACCES, mkdir '/usr/local/lib/node_modules']
npm ERR! errno: 3,
npm ERR! code: 'EACCES',
npm ERR! path: '/usr/local/lib/node_modules',
npm ERR! fstream_type: 'Directory',
npm ERR! fstream_path: '/usr/local/lib/node_modules/react-native-cli',
npm ERR! fstream_class: 'DirWriter',
npm ERR! fstream_stack:
npm ERR! [ '/usr/lib/nodejs/fstream/lib/writer.js:171:23',
npm ERR! '/usr/lib/nodejs/mkdirp/index.js:46:53',
npm ERR! 'Object.oncomplete (fs.js:107:15)' ] }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! System Linux 4.2.0-16-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "react-native-cli"
npm ERR! cwd /home/putuguna
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.4.21
npm ERR! path /usr/local/lib/node_modules
npm ERR! fstream_path /usr/local/lib/node_modules/react-native-cli
npm ERR! fstream_type Directory
npm ERR! fstream_class DirWriter
npm ERR! code EACCES
npm ERR! errno 3
npm ERR! stack Error: EACCES, mkdir '/usr/local/lib/node_modules'
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:171:23
npm ERR! fstream_stack /usr/lib/nodejs/mkdirp/index.js:46:53
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/putuguna/npm-debug.log
npm ERR! not ok code 0


Could you help me for solve my problem



Update :



One thing that i know, i should update my node js version. I have done, by this way :



curl -sL https://deb.nodesource.com/setup_4.x | sudo -E bash -
sudo apt-get install -y nodejs


But the error above appears again. please help










share|improve this question

























  • Consider installing Node 6.x instead of Node 4.x. askubuntu.com/questions/786272/…

    – Thomas Ward
    Oct 7 '16 at 19:41














2












2








2








When i tried to install npm install -g react-native-cli
then i faced an error like below :



npm WARN engine react-native-cli@1.0.0: wanted: {"node":">=4"} (current: {"node":"0.10.25","npm":"1.4.21"})
npm ERR! tar.unpack untar error /home/putuguna/.npm/react-native-cli/1.0.0/package.tgz
npm ERR! Error: EACCES, mkdir '/usr/local/lib/node_modules'
npm ERR! { [Error: EACCES, mkdir '/usr/local/lib/node_modules']
npm ERR! errno: 3,
npm ERR! code: 'EACCES',
npm ERR! path: '/usr/local/lib/node_modules',
npm ERR! fstream_type: 'Directory',
npm ERR! fstream_path: '/usr/local/lib/node_modules/react-native-cli',
npm ERR! fstream_class: 'DirWriter',
npm ERR! fstream_stack:
npm ERR! [ '/usr/lib/nodejs/fstream/lib/writer.js:171:23',
npm ERR! '/usr/lib/nodejs/mkdirp/index.js:46:53',
npm ERR! 'Object.oncomplete (fs.js:107:15)' ] }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! System Linux 4.2.0-16-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "react-native-cli"
npm ERR! cwd /home/putuguna
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.4.21
npm ERR! path /usr/local/lib/node_modules
npm ERR! fstream_path /usr/local/lib/node_modules/react-native-cli
npm ERR! fstream_type Directory
npm ERR! fstream_class DirWriter
npm ERR! code EACCES
npm ERR! errno 3
npm ERR! stack Error: EACCES, mkdir '/usr/local/lib/node_modules'
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:171:23
npm ERR! fstream_stack /usr/lib/nodejs/mkdirp/index.js:46:53
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/putuguna/npm-debug.log
npm ERR! not ok code 0


Could you help me for solve my problem



Update :



One thing that i know, i should update my node js version. I have done, by this way :



curl -sL https://deb.nodesource.com/setup_4.x | sudo -E bash -
sudo apt-get install -y nodejs


But the error above appears again. please help










share|improve this question
















When i tried to install npm install -g react-native-cli
then i faced an error like below :



npm WARN engine react-native-cli@1.0.0: wanted: {"node":">=4"} (current: {"node":"0.10.25","npm":"1.4.21"})
npm ERR! tar.unpack untar error /home/putuguna/.npm/react-native-cli/1.0.0/package.tgz
npm ERR! Error: EACCES, mkdir '/usr/local/lib/node_modules'
npm ERR! { [Error: EACCES, mkdir '/usr/local/lib/node_modules']
npm ERR! errno: 3,
npm ERR! code: 'EACCES',
npm ERR! path: '/usr/local/lib/node_modules',
npm ERR! fstream_type: 'Directory',
npm ERR! fstream_path: '/usr/local/lib/node_modules/react-native-cli',
npm ERR! fstream_class: 'DirWriter',
npm ERR! fstream_stack:
npm ERR! [ '/usr/lib/nodejs/fstream/lib/writer.js:171:23',
npm ERR! '/usr/lib/nodejs/mkdirp/index.js:46:53',
npm ERR! 'Object.oncomplete (fs.js:107:15)' ] }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! System Linux 4.2.0-16-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "react-native-cli"
npm ERR! cwd /home/putuguna
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.4.21
npm ERR! path /usr/local/lib/node_modules
npm ERR! fstream_path /usr/local/lib/node_modules/react-native-cli
npm ERR! fstream_type Directory
npm ERR! fstream_class DirWriter
npm ERR! code EACCES
npm ERR! errno 3
npm ERR! stack Error: EACCES, mkdir '/usr/local/lib/node_modules'
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:171:23
npm ERR! fstream_stack /usr/lib/nodejs/mkdirp/index.js:46:53
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/putuguna/npm-debug.log
npm ERR! not ok code 0


Could you help me for solve my problem



Update :



One thing that i know, i should update my node js version. I have done, by this way :



curl -sL https://deb.nodesource.com/setup_4.x | sudo -E bash -
sudo apt-get install -y nodejs


But the error above appears again. please help







nodejs npm






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 7 '16 at 10:50









Android Dev

10.7k63359




10.7k63359










asked Oct 7 '16 at 10:27









R BesarR Besar

11112




11112













  • Consider installing Node 6.x instead of Node 4.x. askubuntu.com/questions/786272/…

    – Thomas Ward
    Oct 7 '16 at 19:41



















  • Consider installing Node 6.x instead of Node 4.x. askubuntu.com/questions/786272/…

    – Thomas Ward
    Oct 7 '16 at 19:41

















Consider installing Node 6.x instead of Node 4.x. askubuntu.com/questions/786272/…

– Thomas Ward
Oct 7 '16 at 19:41





Consider installing Node 6.x instead of Node 4.x. askubuntu.com/questions/786272/…

– Thomas Ward
Oct 7 '16 at 19:41










2 Answers
2






active

oldest

votes


















0














In case you didn't already, you might want to have a look at the instructions by nodesource.



It looks like you're running Ubuntu 14.04. An upgrade to 16.04 would solve the problem, if this is an option for you.






share|improve this answer































    0














    I had some issues because while the older version was run by the command node, the new version was renamed to nodejs.



    So node never unreturned an error but launched the older version. nodejs worked fine. I had to do a bit of soft linking to fix this.



    I've forgotten the exact procedure but you can run following to see if both exist but point to different programs



    which node
    which nodejs





    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "89"
      };
      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%2faskubuntu.com%2fquestions%2f834167%2fhow-to-fix-wanted-node-4-current-node0-10-25-npm1-4-21-o%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














      In case you didn't already, you might want to have a look at the instructions by nodesource.



      It looks like you're running Ubuntu 14.04. An upgrade to 16.04 would solve the problem, if this is an option for you.






      share|improve this answer




























        0














        In case you didn't already, you might want to have a look at the instructions by nodesource.



        It looks like you're running Ubuntu 14.04. An upgrade to 16.04 would solve the problem, if this is an option for you.






        share|improve this answer


























          0












          0








          0







          In case you didn't already, you might want to have a look at the instructions by nodesource.



          It looks like you're running Ubuntu 14.04. An upgrade to 16.04 would solve the problem, if this is an option for you.






          share|improve this answer













          In case you didn't already, you might want to have a look at the instructions by nodesource.



          It looks like you're running Ubuntu 14.04. An upgrade to 16.04 would solve the problem, if this is an option for you.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Oct 7 '16 at 18:57









          Thomas W.Thomas W.

          13415




          13415

























              0














              I had some issues because while the older version was run by the command node, the new version was renamed to nodejs.



              So node never unreturned an error but launched the older version. nodejs worked fine. I had to do a bit of soft linking to fix this.



              I've forgotten the exact procedure but you can run following to see if both exist but point to different programs



              which node
              which nodejs





              share|improve this answer




























                0














                I had some issues because while the older version was run by the command node, the new version was renamed to nodejs.



                So node never unreturned an error but launched the older version. nodejs worked fine. I had to do a bit of soft linking to fix this.



                I've forgotten the exact procedure but you can run following to see if both exist but point to different programs



                which node
                which nodejs





                share|improve this answer


























                  0












                  0








                  0







                  I had some issues because while the older version was run by the command node, the new version was renamed to nodejs.



                  So node never unreturned an error but launched the older version. nodejs worked fine. I had to do a bit of soft linking to fix this.



                  I've forgotten the exact procedure but you can run following to see if both exist but point to different programs



                  which node
                  which nodejs





                  share|improve this answer













                  I had some issues because while the older version was run by the command node, the new version was renamed to nodejs.



                  So node never unreturned an error but launched the older version. nodejs worked fine. I had to do a bit of soft linking to fix this.



                  I've forgotten the exact procedure but you can run following to see if both exist but point to different programs



                  which node
                  which nodejs






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Oct 7 '16 at 19:31









                  R.S.R.S.

                  16118




                  16118






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Ask Ubuntu!


                      • 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%2faskubuntu.com%2fquestions%2f834167%2fhow-to-fix-wanted-node-4-current-node0-10-25-npm1-4-21-o%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

                      Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

                      ComboBox Display Member on multiple fields

                      Is it possible to collect Nectar points via Trainline?