OS: Windows 10
NPM version: 3.10.5
Node version: v4.4.7
angular-cli version: 1.0.0-beta.10
I get the following warnings during installation:
$ npm install -g angular-cli
npm WARN deprecated [email protected]: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated [email protected]: This package has been discontinued in favor of lodash@^4.0.0.
npm WARN deprecated [email protected]: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated [email protected]: to-iso-string has been deprecated, use @segment/to-iso-string instead.
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
C:\Users\jh\AppData\Roaming\npm\ng -> C:\Users\jh\AppData\Roaming\npm\node_modules\angular-cli\bin\ng
C:\Users\jh\AppData\Roaming\npm
`-- [email protected]
Should I ignore them? How could I fix this?
This bothers me, too. But I think that our only option is to wait for the package maintainers to get their dependencies straight. Ignore it and hope for a update soon
Dupe of https://github.com/angular/angular-cli/issues/837. Basically yeah, until a lot of dependencies of dependencies are updated, these errors will be hard to get rid of.
# npm --version
@nidzrai
npm install -g angular-cli
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
_here are few steps that worked for me ._
# npm --version
npm update -g nvm
node -v
npm install -g angular cli