Npm WARN deprecated minimatch@2.0.10 : upgrade to minimum 3.0.2

Question

$ npm update minimatch@3.0.2

$ npm update -d
npm info it worked if it ends with ok
npm info using npm@2.11.3
npm info using node@v0.12.7
npm info attempt registry request try #1 at 5:33:55 PM
npm http request GET https://registry.npmjs.org/jshint
npm http 200 https://registry.npmjs.org/jshint
npm info ok


$ npm install jshint
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher                                                                                                                 to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher                                                                                                                 to avoid a RegExp DoS issue
jshint@2.9.2 node_modules\jshint
├── strip-json-comments@1.0.4
├── exit@0.1.2
├── shelljs@0.3.0
├── console-browserify@1.1.0 (date-now@0.1.4)
├── lodash@3.7.0
├── minimatch@2.0.10 (brace-expansion@1.1.5)
├── htmlparser2@3.8.3 (domelementtype@1.3.0, entities@1.0.0, domhandler@2.3.0, d                                                                                                                omutils@1.5.1, readable-stream@1.1.14)
└── cli@0.6.6 (glob@3.2.11)

Answer 1

npm install -g minimatch@3.0.2

try this .... should work

Answer 2

Sorry for the late reply..

 sudo npm install 

Try this .. it works for me to install npm

Use this to upgrade.

sudo npm install -g npm@3

Answer 3

( OSX)

sudo chown -R $USER/usr/local

Answer 4

node v4.4.7 sudo chown -R $USER/usr/local .

Answer 5

.  npm + minimatch@3.0.4   sudo npm install -g minimatch@3.0.4 . .

Answer 6

responseJS bebel script npm . . , .

cmd:

npm babelify babel-preset-env

Answer 7

Although chown- one of the ways to achieve this, I always considered it the least favorable. Instead, to change the owner of the system files, it makes sense to run npm config set prefix $HOME/.node_modules. This will configure npm to search yours node_modulesin your home directory, not globally.

See https://docs.npmjs.com/getting-started/fixing-npm-permissions .