npm i -g node-inspector ERR

[olegator1]

When I try to install npm i -g node-inspector ERR , i'v take this issue:

npm ERR! TypeError: Object # has no method 'match'
npm ERR! at Object.scriptpath_ (/usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:138:23)
npm ERR! at Array.forEach (native)
npm ERR! at scriptpath (/usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:132:19)
npm ERR! at /usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:119:33
npm ERR! at Array.forEach (native)
npm ERR! at extras (/usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:118:21)
npm ERR! at parseJson (/usr/local/lib/node_modules

[timoxley]

@olegator1 I just managed to install it, can you gist the full output please?

[domenic]

I am pretty sure this was fixed in recent versions of npm. Also, please paste the whole error log when you get an error.

[0Bu]

The same here. Gist with output log & npm-debug.log: https://gist.github.com/olbura/8400099

The cause seems to be in blanket->pattern of the strong-data-uri dependency:
https://github.com/strongloop/strong-data-uri/blob/master/package.json#L9

[olegator1]

npm i -g node-inspector
info trying registry request attempt 1 at 22:37:48
http GET https://registry.npmjs.org/node-inspector
http 304 https://registry.npmjs.org/node-inspector
info trying registry request attempt 1 at 22:37:50
http GET https://registry.npmjs.org/async
info trying registry request attempt 1 at 22:37:51
http GET https://registry.npmjs.org/socket.io
info trying registry request attempt 1 at 22:37:51
http GET https://registry.npmjs.org/glob
info trying registry request attempt 1 at 22:37:51
http GET https://registry.npmjs.org/rc
info trying registry request attempt 1 at 22:37:51
http GET https://registry.npmjs.org/express
info trying registry request attempt 1 at 22:37:51
http GET https://registry.npmjs.org/debug
info trying registry request attempt 1 at 22:37:51
http GET https://registry.npmjs.org/strong-data-uri
http 304 https://registry.npmjs.org/async
http 304 https://registry.npmjs.org/glob
http 304 https://registry.npmjs.org/express
http 304 https://registry.npmjs.org/socket.io
http 304 https://registry.npmjs.org/strong-data-uri
npm http GET https://registry.npmjs.org/strong-data-uri/-/strong-data-uri-0.1.0.tgz
http 304 https://registry.npmjs.org/rc
http 304 https://registry.npmjs.org/debug
npm http 200 https://registry.npmjs.org/strong-data-uri/-/strong-data-uri-0.1.0.tgz
npm ERR! TypeError: Object # has no method 'match'
npm ERR! at Object.scriptpath_ (/usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:138:23)
npm ERR! at Array.forEach (native)
npm ERR! at scriptpath (/usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:132:19)
npm ERR! at /usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:119:33
npm ERR! at Array.forEach (native)
npm ERR! at extras (/usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:118:21)
npm ERR! at parseJson (/usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:87:17)
npm ERR! at /usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:59:33
npm ERR! at fs.js:266:14
npm ERR! at /usr/local/lib/node_modules/npm/node_modules/read-installed/node_modules/read-package-json/node_modules/graceful-fs/graceful-fs.js:103:5
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR! http://github.com/isaacs/npm/issues

npm ERR! System Linux 2.6.39-400.212.1.el6uek.x86_64
npm ERR! command "node" "/usr/local/bin/npm" "i" "-g" "node-inspector"
npm ERR! cwd /root/Desktop
npm ERR! node -v v0.10.24
npm ERR! npm -v 1.3.23
npm ERR! type undefined_method
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /root/Desktop/npm-debug.log
npm ERR! not ok code 0

[bajtos]

Looks like a duplicate of strongloop/strong-data-uri#1. The user was able to fix the problem by reinstalling npm.

[0Bu]

Hi Miroslav, i don't think this is the issue of strong-data-uri, the bug is reproduceable on fresh ubuntu with vagrant (http://files.vagrantup.com/precise32.box) too:

• sudo apt-get update && sudo apt-get install make g++
• wget http://nodejs.org/dist/v0.10.24/node-v0.10.24.tar.gz && tar xzf node-v0.10.24.tar.gz
• cd node-v0.10.24/ && ./configure && make && sudo make install
• npm -v -> 1.3.21
• sudo npm up -g
• npm -v -> 1.3.23
• now update with npm@1.3.23 sudo npm up -g
• sudo npm i -g node-inspector

The output:

info trying registry request attempt 1 at 11:53:15
http GET https://registry.npmjs.org/node-inspector
http 200 https://registry.npmjs.org/node-inspector
npm http GET https://registry.npmjs.org/node-inspector/-/node-inspector-0.7.0-1.tgz
npm http 200 https://registry.npmjs.org/node-inspector/-/node-inspector-0.7.0-1.tgz
info trying registry request attempt 1 at 11:53:20
http GET https://registry.npmjs.org/rc
info trying registry request attempt 1 at 11:53:20
http GET https://registry.npmjs.org/strong-data-uri
info trying registry request attempt 1 at 11:53:20
http GET https://registry.npmjs.org/async
info trying registry request attempt 1 at 11:53:20
http GET https://registry.npmjs.org/debug
info trying registry request attempt 1 at 11:53:21
http GET https://registry.npmjs.org/glob
info trying registry request attempt 1 at 11:53:21
http GET https://registry.npmjs.org/socket.io
info trying registry request attempt 1 at 11:53:21
http GET https://registry.npmjs.org/express
http 304 https://registry.npmjs.org/async
http 200 https://registry.npmjs.org/rc
http 200 https://registry.npmjs.org/debug
npm http GET https://registry.npmjs.org/rc/-/rc-0.3.3.tgz
npm http GET https://registry.npmjs.org/debug/-/debug-0.7.4.tgz
http 200 https://registry.npmjs.org/strong-data-uri
npm http GET https://registry.npmjs.org/strong-data-uri/-/strong-data-uri-0.1.0.tgz
http 304 https://registry.npmjs.org/glob
http 200 https://registry.npmjs.org/socket.io
npm http GET https://registry.npmjs.org/socket.io/-/socket.io-0.9.16.tgz
npm http 200 https://registry.npmjs.org/rc/-/rc-0.3.3.tgz
npm http 200 https://registry.npmjs.org/debug/-/debug-0.7.4.tgz
npm http 200 https://registry.npmjs.org/strong-data-uri/-/strong-data-uri-0.1.0.tgz
npm http 200 https://registry.npmjs.org/socket.io/-/socket.io-0.9.16.tgz
npm ERR! TypeError: Object #<Object> has no method 'match'
npm ERR!     at Object.scriptpath_ (/usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:138:23)
npm ERR!     at Array.forEach (native)
npm ERR!     at scriptpath (/usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:132:19)
npm ERR!     at /usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:119:33
npm ERR!     at Array.forEach (native)
npm ERR!     at extras (/usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:118:21)
npm ERR!     at parseJson (/usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:87:17)
npm ERR!     at /usr/local/lib/node_modules/npm/node_modules/read-package-json/read-json.js:59:33
npm ERR!     at fs.js:266:14
npm ERR!     at /usr/local/lib/node_modules/npm/node_modules/read-installed/node_modules/read-package-json/node_modules/graceful-fs/graceful-fs.js:103:5
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/isaacs/npm/issues>

npm ERR! System Linux 3.2.0-23-generic-pae
npm ERR! command "node" "/usr/local/bin/npm" "i" "-g" "node-inspector"
npm ERR! cwd /vagrant/node-v0.10.24
npm ERR! node -v v0.10.24
npm ERR! npm -v 1.3.23
npm ERR! type undefined_method
http 200 https://registry.npmjs.org/express
npm http GET https://registry.npmjs.org/express/-/express-3.4.8.tgz
npm http 200 https://registry.npmjs.org/express/-/express-3.4.8.tgz
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /vagrant/node-v0.10.24/npm-debug.log
npm ERR! not ok code 0

In order to install node-inpspector just downgrade to npm@1.3.21 with sudo npm i -g npm@1.3.21, but this wouldn't fix the issue with npm@1.3.23

[isaacs]

Fixed in latest release.