lamiastella

nvm

Mar 14th, 2016
595
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.21 KB | None | 0 0
  1. bash-3.2$ git clone https://github.com/creationix/nvm.git ~/.nvm && cd ~/.nvm && git checkout `git describe --abbrev=0 --tags`
  2. Cloning into '/Users/mona/.nvm'...
  3.  
  4. remote: Counting objects: 4417, done.
  5. remote: Compressing objects: 100% (9/9), done.
  6. remote: Total 4417 (delta 1), reused 0 (delta 0), pack-reused 4408
  7. Receiving objects: 100% (4417/4417), 1.12 MiB | 608.00 KiB/s, done.
  8. Resolving deltas: 100% (2589/2589), done.
  9. Checking connectivity... done
  10. Note: checking out 'v0.31.0'.
  11.  
  12. You are in 'detached HEAD' state. You can look around, make experimental
  13. changes and commit them, and you can discard any commits you make in this
  14. state without impacting any branches by performing another checkout.
  15.  
  16. If you want to create a new branch to retain commits you create, you may
  17. do so (now or later) by using -b with the checkout command again. Example:
  18.  
  19. git checkout -b new_branch_name
  20.  
  21. HEAD is now at 2176894... v0.31.0
  22. bash-3.2$
  23. bash-3.2$ ls
  24. CONTRIBUTING.md Makefile bash_completion nvm-exec package.json
  25. LICENSE.md README.markdown install.sh nvm.sh test
  26. bash-3.2$ . ~/.nvm/nvm.sh
  27. bash-3.2$ vim ~/.bashrc
  28. syntastic: error: your shell /usr/local/bin/fish doesn't use traditional UNIX syntax for redirections
  29. Press ENTER or type command to continue
  30. bash-3.2$ source ~/.bashrc
  31. bash-3.2$ nvm install 4.0
  32. Downloading https://nodejs.org/dist/v4.0.0/node-v4.0.0-darwin-x64.tar.xz...
  33. ######################################################################## 100.0%
  34. Now using node v4.0.0 (npm v2.14.2)
  35. Creating default alias: default -> 4.0 (-> v4.0.0)
  36. bash-3.2$ nvm use 4.0
  37. Now using node v4.0.0 (npm v2.14.2)
  38. bash-3.2$ cd ..
  39. bash-3.2$ cd interviews/
  40. bash-3.2$ cd mean/
  41. bash-3.2$ ls
  42. app bower_components index.html package.json todomvc
  43. bower.json gulpfile.babel.js mean test
  44. bash-3.2$ yo meanjs
  45. You're using the official MEAN.JS generator.
  46. ? What mean.js version would you like to generate? 0.4.0
  47. 0.4.0
  48. ? In which folder would you like the project to be generated? This can be changed later. mean
  49. Cloning the MEAN repo.......
  50. Error: Command failed: /bin/sh -c git clone --branch v0.4.0 https://github.com/meanjs/mean.git mean
  51. fatal: destination path 'mean' already exists and is not an empty directory.
  52.  
  53. bash-3.2$ sudo rm -rf mean/
  54. Password:
  55. bash-3.2$ yo meanjs
  56. You're using the official MEAN.JS generator.
  57. ? What mean.js version would you like to generate? 0.4.0
  58. 0.4.0
  59. ? In which folder would you like the project to be generated? This can be changed later. mean
  60. Cloning the MEAN repo.......
  61. ? What would you like to call your application? MEAN
  62. ? How would you describe your application? Full-Stack JavaScript with MongoDB, Express, AngularJS, and Node.js
  63. ? How would you describe your application in comma seperated key words? MongoDB, Express, AngularJS, Node.js
  64. ? What is your company/author name?
  65. ? Would you like to generate the article example CRUD module? Yes
  66. ? Would you like to generate the chat example module? Yes
  67. Running npm install for you....
  68. This may take a couple minutes.
  69. Error: Command failed: /bin/sh -c cd mean && npm install
  70. npm ERR! Darwin 14.5.0
  71. npm ERR! argv "/Users/mona/.nvm/versions/node/v4.0.0/bin/node" "/Users/mona/.nvm/versions/node/v4.0.0/bin/npm" "install"
  72. npm ERR! node v4.0.0
  73. npm ERR! npm v2.14.2
  74. npm ERR! code ETIMEDOUT
  75. npm ERR! errno ETIMEDOUT
  76. npm ERR! syscall connect
  77.  
  78. npm ERR! network connect ETIMEDOUT 23.235.39.162:443
  79. npm ERR! network This is most likely not a problem with npm itself
  80. npm ERR! network and is related to network connectivity.
  81. npm ERR! network In most cases you are behind a proxy or have bad network settings.
  82. npm ERR! network
  83. npm ERR! network If you are behind a proxy, please make sure that the
  84. npm ERR! network 'proxy' config is set properly. See: 'npm help config'
  85.  
  86. npm ERR! Please include the following file with any support request:
  87. npm ERR! /Users/mona/interviews/mean/mean/npm-debug.log
  88.  
  89. at ChildProcess.exithandler (child_process.js:203:12)
  90. at emitTwo (events.js:87:13)
  91. at ChildProcess.emit (events.js:172:7)
  92. at maybeClose (internal/child_process.js:817:16)
  93. at Socket.<anonymous> (internal/child_process.js:319:11)
  94. at emitOne (events.js:77:13)
  95. at Socket.emit (events.js:169:7)
  96. at Pipe._onclose (net.js:469:12)
Advertisement
Add Comment
Please, Sign In to add comment