Windows 7 x64 , running a cygwin console
As a forewarning, we are moving the CLI npm package to "@angular/cli" with the next release,
which will only support Node 6.9 and greater. This package will be officially deprecated
shortly after.To disable this warning use "ng set --global warnings.packageDeprecation=false".
angular-cli: 1.0.0-beta.28.3
node: 6.9.1
os: win32 x64
I just installed it:
$ npm install -g angular-cli
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
C:\Users\Hubert\AppData\Roaming\npm\ng -> C:\Users\Hubert\AppData\Roaming\npm\node_modules\angular-cli\bin\ng[email protected] install C:\Users\Hubert\AppData\Roaming\npm\node_modules\angular-cli\node_modules\node-sass
node scripts/install.jsDownloading binary from https://github.com/sass/node-sass/releases/download/v4.5.0/win32-x64-48_binding.node
Download complete
Binary saved to C:\Users\Hubert\AppData\Roaming\npm\node_modules\angular-cli\node_modules\node-sass\vendor\win32-x64-48\binding.node
Caching binary to C:\Users\Hubert\AppData\Roaming\npm-cache\node-sass\4.5.0\win32-x64-48_binding.node[email protected] postinstall C:\Users\Hubert\AppData\Roaming\npm\node_modules\angular-cli\node_modules\node-sass
node scripts/build.jsBinary found at C:\Users\Hubert\AppData\Roaming\npm\node_modules\angular-cli\node_modules\node-sass\vendor\win32-x64-48\binding.node
Testing binary
Binary is fine
C:\Users\Hubert\AppData\Roaming\npm[list of all packages]
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\angular-cli\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN @angular/[email protected] requires a peer of rxjs@^5.0.1 but none was installed.
In addition to above:
$ npm -g list | grep angular
+-- [email protected]
| +-- @angular-cli/[email protected]
| | +-- @angular/[email protected]
| +-- @angular-cli/[email protected]
| +-- @angular/[email protected]
| +-- @angular/[email protected]
| +-- @angular/[email protected]
npm ERR! peer dep missing: rxjs@^5.0.1, required by @angular/[email protected]
npm ERR! extraneous: [email protected] C:\Users\Hubert\AppData\Roaming\npm\node_modules\angular-cli\node_modules\@angular-cli\ast-tools\node_modules\tsickle
I was able to run ng new myapp without problem.
Pretty sure this was fixed in #4465
Ok! So I manually made this edit from commit in C:\Users\Hubert\AppData\Roaming\npm\node_modules\angular-cli\package.json
and did npm -g update angular-cli but still get error:
npm ERR! missing: rxjs@^5.0.1, required by [email protected]
What else should I do?
Still getting extraneous error during npm ls.
@angular/cli: 1.0.0-beta.30
node: 7.2.1
os: win32 x64
@angular/common: 2.4.6
@angular/compiler: 2.4.6
@angular/core: 2.4.6
@angular/forms: 2.4.6
@angular/http: 2.4.6
@angular/platform-browser: 2.4.6
@angular/platform-browser-dynamic: 2.4.6
@angular/material: 2.0.0-beta.1
@angular/router: 3.4.6
@angular/cli: 1.0.0-beta.30
@angular/compiler-cli: 2.4.6
npm ERR! extraneous: [email protected] [REDACTED]\e-forms\node_modules\@angular-cli\ast-tools\node_modules\tsickle
Btw, you should use the new package name @angular/cli instead of angular-cli. angular-cli is beta 28.3 while @angular/cli is beta 30.
Just now installed cli and got the following error:
npm WARN @angular/[email protected] requires a peer of rxjs@^5.0.1 but none was installed.
Just installed angular-cli now and got the same error.
"npm WARN @angular/[email protected] requires a peer of rxjs@^5.0.1 but none was installed."
However, rxjs was installed with later version.
npm show rxjs version
5.1.0
@mickeyjohn Be aware that npm show is actually showing information from NPM registry, not locally installed modules. Try npm ls rxjs for local modules.
I am getting the same errors for a globally installed @angular/cli.
same here on "npm install -g @angular/cli"
npm WARN @angular/[email protected] requires a peer of rxjs@^5.0.1 but none was installed.
I had this problem and solved updating angular cli following these steps:
https://github.com/angular/angular-cli#updating-angular-cli
I chose to overwrite package.json and other files whose I didnt modify before.
I also installed rxjs globally if the problem persist
This kind of solved it for me (running osx 10.12.2), i had an old version installed so did:
➜ ~ npm uninstall -g angular-cli @angular/cli
➜ ~ npm cache clean
➜ ~ npm install -g @angular/cli@latest
But unfortunately still got:
npm WARN @angular/[email protected] requires a peer of rxjs@^5.0.1 but none was installed.
Running ng help just crashed because of missing rxjs modules. So i just did:
➜ ~ npm install -g rxjs
/usr/local/lib
└─┬ [email protected]
└── [email protected]
After this the cli works correctly....
Doing npm install -g rxjs helped to get rid of rxj peer error, but the extraneous was still there.
So I did what @slapers wrote and that got rid of extraneous, but peer rxjs WARN (not ERR) came back:
npm WARN @angular/[email protected] requires a peer of rxjs@^5.0.1 but none was installed
@Koshmaar Have you tried
npm uninstall -g angular-cli
npm uninstall -g @angular/cli
npm cache clean
npm install -g @angular/cli
I just did that, first updating npm to 4.2 , and this time
$ npm -g list | grep angular
+-- @angular/[email protected]
| +-- UNMET PEER DEPENDENCY @angular/compiler@^2.3.1 || >=4.0.0-beta <5.0.0
| +-- UNMET PEER DEPENDENCY @angular/compiler-cli@^2.3.1 || >=4.0.0-beta <5.0.0
| +-- UNMET PEER DEPENDENCY @angular/core@^2.3.1 || >=4.0.0-beta <5.0.0
| +-- UNMET PEER DEPENDENCY @angular/tsc-wrapped@^0.5.0
npm ERR! peer dep missing: @angular/compiler@^2.3.1 || >=4.0.0-beta <5.0.0, required by @ngtools/[email protected]
npm ERR! peer dep missing: @angular/compiler-cli@^2.3.1 || >=4.0.0-beta <5.0.0, required by @ngtools/[email protected]
npm ERR! peer dep missing: @angular/core@^2.3.1 || >=4.0.0-beta <5.0.0, required by @ngtools/[email protected]
npm ERR! peer dep missing: @angular/tsc-wrapped@^0.5.0, required by @ngtools/[email protected]
So to fix that I should do npm install -g @angular/compiler etc ? I'd prefer to avoid having @angular in global namespace, just have it in local, but if there's no other way...
@Koshmaar
No, I would not worry about it.
I have installed @angular/cli many times, I can create apps, ng test and ng serve them.
If I was you, I would not try very hard to appease every warning to make it go away.
Sure, it is annoying to see all those "UNMET PEER DEPENDENCY THIS and THAT"; however. you can ignore them and move on.
If you create a new app, inspect what the package.json contains, you actually see it has
...
"dependencies": {
"@angular/common": "^2.4.0",
"@angular/compiler": "^2.4.0",
"@angular/core": "^2.4.0",
...
},
"devDependencies": {
"@angular/cli": "1.0.0-beta.31",
"@angular/compiler-cli": "^2.4.0",
....
}
We've fixed these warnings since. Sorry about that folks.
I started off fresh from with new application from scratch and was able to get a clean result with
npm list -g --depth=0
Following are the steps.
1) Uninstall angular-cli from global scope
This will remove old version of angular cli which has been deprecated and renamed to @angular/cli
npm uninstall -g angular-cli
npm cache clean
npm uninstall --save-dev angular-cli
2) Install @angular/cli at both global scope and current applications local scope
Global package:
npm uninstall -g @angular/cli
npm cache clean
npm install -g @angular/cli@latest
Local project package:
npm install --save-dev @angular/cli@latest
Here is the result of command: npm list -g --depth=0
C:\Users\
+-- @angular/[email protected]
+-- [email protected]
+-- [email protected]
+-- [email protected]
`-- [email protected]
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
_This action has been performed automatically by a bot._
Most helpful comment
I started off fresh from with new application from scratch and was able to get a clean result with
npm list -g --depth=0
Following are the steps.
1) Uninstall angular-cli from global scope
This will remove old version of angular cli which has been deprecated and renamed to @angular/cli
npm uninstall -g angular-cli
npm cache clean
npm uninstall --save-dev angular-cli
2) Install @angular/cli at both global scope and current applications local scope
Global package:
npm uninstall -g @angular/cli
npm cache clean
npm install -g @angular/cli@latest
Local project package:
npm install --save-dev @angular/cli@latest