Dependency deprecated

[space-curiosity]

Steps to reproduce

On npm install got warnings for Dependency deprecated

What I expected

What happened instead

Got warning on npm install. here are the list of warnings:

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]: Critical security bug fixed in v7.0.0 - read more at electron/packager#333
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]: Copy its ~20 LOC directly into your code instead.
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.
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]: Deprecated, use jstransformer
npm WARN deprecated [email protected]: this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN deprecated [email protected]: cross-spawn no longer requires a build toolchain, use it instead!
npm WARN deprecated [email protected]: lodash@<3.0.0 is no longer maintained. Upgrade to lodash@^4.0.0.
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.
npm WARN prefer global [email protected] should be installed with -g

OS version

windows 10

Screenshot / Video

[dmsnell]

Thanks @space-curiosity. Some of these are probably legitimate while others are probably stuck this way due to being dependencies of dependencies.

Are you looking to start contributing? This would make for some great first PRs. You can use a convenient tool npm check updates to see which dependencies are out of date. Then, probably one or a few at a time, submit a PR to update the versions. We only need to make sure that we test functionality for regressions on version bumps. Before testing, it's good to rm -rf node_modules to clear out lingering state.

[owcz]

Here's the state of the current dependency warnings:

$ npm install
npm WARN deprecated [email protected]: Use uuid module instead
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN prefer global [email protected] should be installed with -g

1. node-uuid: Latest Simperium is in use. Blocked by Update uuid to version 3.0.0 Simperium/node-simperium#44.

$ npm ls node-uuid
[email protected]
└─┬ [email protected]
  └── [email protected] 

2. minimatch: Update [email protected] in Fix minimatch dependency error #542. Creates new unmet dependency warning for ajv discussed here: Missing peer dependency: ajv@>=5.0.3-beta.0 electron-userland/electron-builder#1344. Non-issue?

$ npm ls minimatch
[email protected] 
├─┬ [email protected]
│ └── [email protected] 
└─┬ [email protected]
  └─┬ [email protected]
    └─┬ [email protected]
      └── [email protected] 

3. node-gyp: Tried to add "preinstall": "npm install -g node-gyp", which failed. Blocked by why depend on node-gyp sass/node-sass#1740.

$ npm ls node-gyp
[email protected]
└─┬ [email protected]
  └── [email protected]