angular-cli: Error in installation .

Please provide us with the following information:

  1. OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?) Mac OSX El Capitan

  2. Versions. Please run ng --version. If there’s nothing outputted, please run in a Terminal: node --version and paste the result here: node v4.4.7 angular-cli 1.0.0-beta.11-webpack.2

  3. Repro steps. Was this an app that wasn’t created using the CLI? What change did you do on your code? etc. Nothing

  4. The log given by the failure. Normally this include a stack trace and some more information. Can not install last 233632 verbose stack at /usr/local/lib/node_modules/npm/node_modules/read-installed/read-installed.js:263:14 233633 verbose cwd /Users/goriunov 233634 error Darwin 15.6.0 233635 error argv “/usr/local/bin/node” “/usr/local/bin/npm” “i” “-g” “angular-cli@1.0.0-beta.11-webpack.2” 233636 error node v4.4.7 233637 error npm v2.15.8 233638 error code EPEERINVALID 233639 error peerinvalid The package typescript@2.0.0 does not satisfy its siblings’ peerDependencies requirements! 233639 error peerinvalid Peer @angular/tsc-wrapped@0.2.2 wants typescript@^1.9.0-dev 233639 error peerinvalid Peer ts-helpers@1.1.1 wants typescript@>=1.8.0 || >=1.9.0-dev 233639 error peerinvalid Peer tslint@3.14.0 wants typescript@>=1.7.3 233640 verbose exit [ 1, true ]

  5. Mention any other details that might be useful. I just installed new OS and installed node after i run installation of Angular CLI and i could not do it


    Thanks! We’ll be in touch soon.

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Reactions: 2
  • Comments: 16 (4 by maintainers)

Most upvoted comments

I had the same problem trying to upgrade from angular-cli: 1.0.0-beta.10 to angular-cli@webpack

My environment: node v4.5.0, npm 2.15.9, Ubuntu 14.04.

Resolved when upgraded to node v6.4.0, npm 3.10.3.

After successful installation I’ve seen only following text in red: ├── UNMET PEER DEPENDENCY typescript@2.0.0

So loosely related to #1737 and #1046.

Same problem solved by using NPM3 for me