I don't know if it is still an issue. I was experiencing the same nuisance with @angular/cli v1.1.2 on npm 4.1.2. I deleted the node_modules directory and then went on to updating npm (since this was a common cause in the past).
I wanted to upgrade npm to 5.0.3 (latest) but since I was using nvm it seems to have messed up the libraries. Thus, I reinstalled node.
Then, I went with
npm cache clean
npm rebuild
npm install - This one several times, since every time it threw an error with a different package
I don't know if it is still an issue. I was experiencing the same nuisance with
@angular/cli v1.1.2
onnpm 4.1.2
. I deleted thenode_modules
directory and then went on to updatingnpm
(since this was a common cause in the past).I wanted to upgrade
npm
to5.0.3
(latest) but since I was usingnvm
it seems to have messed up the libraries. Thus, I reinstallednode
.Then, I went with
npm cache clean
npm rebuild
npm install
- This one several times, since every time it threw an error with a different packageIn the end, every package was fine.
Hope this helps.
from terminal
Run the npm update after installing all peer dependencies and it will work.