Tracking: Warnings on console from npm install

[hansl]

We should not have warnings on the command line when people create a new project and npm install.

[Brocco]

Current status of dependencies (as of version 1.0.0-beta.26)

npm WARN deprecated minimatch (2 causes)

• karma-remap-istanbul causes a warning of a deprecated version of minimatch
  This is caused by an older version of karma-remap-istanbul and by remap-istanbul (a sub-dependency) using an older version of istanbul as well. Updating the CLI project's version of karma-remap-istanbul to v0.4.0 fixes the first dependency issue. To fix the other an update of istanbul within remap-istanbul would be needed.

• protractor causes a warning of a deprecated version of minimatch
  This is caused by jamine's reference to an older version of glob. This has been corrected in jasmine in version 2.5.1 (current version is 2.5.3).
  To make this correction the version of jasmine will need bumped in both protractor and jasminewd

npm WARN prefer global node-gyp

node-sass has node-gyp as a local dependency while it prefers to be a global dependency (code here)

[hansl]

@Brocco If we update protractor to 5, would that work?

[Brocco]

@hansl unfortunately not, both protractor and jasminewd have their versions of jasmine pinned to v2.4.1, even in release v5.0.0

The good news is that there are no documented breaking changes in jasmine between v2.4.1 and v2.5.3 so the upgrades should be seemless

[Brocco]

There is a remaining warning about a package that prefers to be installed globally (node-gyp)

npm WARN prefer global [email protected] should be installed with -g

This is a dependency of of node-sass.

[osnoser1]

#4575 [beta.31] npm WARN at installation in global

[Brocco]

At this point the only warning on installation (global or local) is when installing within a project there is a warning that node-gyp prefers to be installed globally, this is a dependency of node-sass.

[angular-automatic-lock-bot]

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.}