I am trying to install the
npm install node-red-contrib-simple-message-queue
I cut/pasted that into my machine.
I get an error:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node',
1 verbose cli '/usr/bin/npm',
1 verbose cli 'install',
1 verbose cli 'node-red-contrib-simple-message-queue' ]
2 info using npm@5.6.0
3 info using node@v8.11.3
4 verbose npm-session 94545e99123dfdfa
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 silly fetchPackageMetaData error for node-red-contrib-simple-message-queue@latest request to https://registry.npmjs.org/node-red-contrib-simple-message-queue failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443
8 verbose type system
9 verbose stack FetchError: request to https://registry.npmjs.org/node-red-contrib-simple-message-queue failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443
9 verbose stack at ClientRequest.req.on.err (/usr/lib/node_modules/npm/node_modules/pacote/node_modules/make-fetch-happen/node_modules/node-fetch-npm/src/index.js:68:14)
9 verbose stack at emitOne (events.js:116:13)
9 verbose stack at ClientRequest.emit (events.js:211:7)
9 verbose stack at TLSSocket.socketErrorListener (_http_client.js:387:9)
9 verbose stack at emitOne (events.js:116:13)
9 verbose stack at TLSSocket.emit (events.js:211:7)
9 verbose stack at emitErrorNT (internal/streams/destroy.js:64:8)
9 verbose stack at _combinedTickCallback (internal/process/next_tick.js:138:11)
9 verbose stack at process._tickCallback (internal/process/next_tick.js:180:9)
10 verbose cwd /home/pi/.node-red
11 verbose Linux 4.9.52+
12 verbose argv "/usr/bin/node" "/usr/bin/npm" "install" "node-red-contrib-simple-message-queue"
13 verbose node v8.11.3
14 verbose npm v5.6.0
15 error code ENOTFOUND
16 error errno ENOTFOUND
17 error network request to https://registry.npmjs.org/node-red-contrib-simple-message-queue failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443
18 error network This is a problem related to network connectivity.
18 error network In most cases you are behind a proxy or have bad network settings.
18 error network
18 error network If you are behind a proxy, please make sure that the
18 error network 'proxy' config is set properly. See: 'npm help config'
19 verbose exit [ 1, true ]