Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- bash-3.2$ git clone https://github.com/creationix/nvm.git ~/.nvm && cd ~/.nvm && git checkout `git describe --abbrev=0 --tags`
- Cloning into '/Users/mona/.nvm'...
- remote: Counting objects: 4417, done.
- remote: Compressing objects: 100% (9/9), done.
- remote: Total 4417 (delta 1), reused 0 (delta 0), pack-reused 4408
- Receiving objects: 100% (4417/4417), 1.12 MiB | 608.00 KiB/s, done.
- Resolving deltas: 100% (2589/2589), done.
- Checking connectivity... done
- Note: checking out 'v0.31.0'.
- You are in 'detached HEAD' state. You can look around, make experimental
- changes and commit them, and you can discard any commits you make in this
- state without impacting any branches by performing another checkout.
- If you want to create a new branch to retain commits you create, you may
- do so (now or later) by using -b with the checkout command again. Example:
- git checkout -b new_branch_name
- HEAD is now at 2176894... v0.31.0
- bash-3.2$
- bash-3.2$ ls
- CONTRIBUTING.md Makefile bash_completion nvm-exec package.json
- LICENSE.md README.markdown install.sh nvm.sh test
- bash-3.2$ . ~/.nvm/nvm.sh
- bash-3.2$ vim ~/.bashrc
- syntastic: error: your shell /usr/local/bin/fish doesn't use traditional UNIX syntax for redirections
- Press ENTER or type command to continue
- bash-3.2$ source ~/.bashrc
- bash-3.2$ nvm install 4.0
- Downloading https://nodejs.org/dist/v4.0.0/node-v4.0.0-darwin-x64.tar.xz...
- ######################################################################## 100.0%
- Now using node v4.0.0 (npm v2.14.2)
- Creating default alias: default -> 4.0 (-> v4.0.0)
- bash-3.2$ nvm use 4.0
- Now using node v4.0.0 (npm v2.14.2)
- bash-3.2$ cd ..
- bash-3.2$ cd interviews/
- bash-3.2$ cd mean/
- bash-3.2$ ls
- app bower_components index.html package.json todomvc
- bower.json gulpfile.babel.js mean test
- bash-3.2$ yo meanjs
- You're using the official MEAN.JS generator.
- ? What mean.js version would you like to generate? 0.4.0
- 0.4.0
- ? In which folder would you like the project to be generated? This can be changed later. mean
- Cloning the MEAN repo.......
- Error: Command failed: /bin/sh -c git clone --branch v0.4.0 https://github.com/meanjs/mean.git mean
- fatal: destination path 'mean' already exists and is not an empty directory.
- bash-3.2$ sudo rm -rf mean/
- Password:
- bash-3.2$ yo meanjs
- You're using the official MEAN.JS generator.
- ? What mean.js version would you like to generate? 0.4.0
- 0.4.0
- ? In which folder would you like the project to be generated? This can be changed later. mean
- Cloning the MEAN repo.......
- ? What would you like to call your application? MEAN
- ? How would you describe your application? Full-Stack JavaScript with MongoDB, Express, AngularJS, and Node.js
- ? How would you describe your application in comma seperated key words? MongoDB, Express, AngularJS, Node.js
- ? What is your company/author name?
- ? Would you like to generate the article example CRUD module? Yes
- ? Would you like to generate the chat example module? Yes
- Running npm install for you....
- This may take a couple minutes.
- Error: Command failed: /bin/sh -c cd mean && npm install
- npm ERR! Darwin 14.5.0
- npm ERR! argv "/Users/mona/.nvm/versions/node/v4.0.0/bin/node" "/Users/mona/.nvm/versions/node/v4.0.0/bin/npm" "install"
- npm ERR! node v4.0.0
- npm ERR! npm v2.14.2
- npm ERR! code ETIMEDOUT
- npm ERR! errno ETIMEDOUT
- npm ERR! syscall connect
- npm ERR! network connect ETIMEDOUT 23.235.39.162:443
- npm ERR! network This is most likely not a problem with npm itself
- npm ERR! network and is related to network connectivity.
- npm ERR! network In most cases you are behind a proxy or have bad network settings.
- npm ERR! network
- npm ERR! network If you are behind a proxy, please make sure that the
- npm ERR! network 'proxy' config is set properly. See: 'npm help config'
- npm ERR! Please include the following file with any support request:
- npm ERR! /Users/mona/interviews/mean/mean/npm-debug.log
- at ChildProcess.exithandler (child_process.js:203:12)
- at emitTwo (events.js:87:13)
- at ChildProcess.emit (events.js:172:7)
- at maybeClose (internal/child_process.js:817:16)
- at Socket.<anonymous> (internal/child_process.js:319:11)
- at emitOne (events.js:77:13)
- at Socket.emit (events.js:169:7)
- at Pipe._onclose (net.js:469:12)
Advertisement
Add Comment
Please, Sign In to add comment