When running ‘npm install --save-dev nodemon’ I receive the following errors:
npm ERR! network getaddrinfo ENOTFOUND sinopia sinopia:4873
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Please include the following file with any support request:
npm ERR! /Users/user/front-end-dev-book/chattrbox/npm-debug.log
Here is the full debug log:
0 info it worked if it ends with ok
1 verbose cli [ '/Users/pgreen/.nvm/versions/node/v6.10.3/bin/node',
1 verbose cli '/Users/pgreen/.nvm/versions/node/v6.10.3/bin/npm',
1 verbose cli 'install',
1 verbose cli '--save-dev',
1 verbose cli 'nodemon' ]
2 info using npm@3.10.10
3 info using node@v6.10.3
4 silly loadCurrentTree Starting
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 silly fetchPackageMetaData nodemon
8 silly fetchNamedPackageData nodemon
9 silly mapToRegistry name nodemon
10 silly mapToRegistry using default registry
11 silly mapToRegistry registry http://sinopia:4873/
12 silly mapToRegistry data Result {
12 silly mapToRegistry raw: 'nodemon',
12 silly mapToRegistry scope: null,
12 silly mapToRegistry escapedName: 'nodemon',
12 silly mapToRegistry name: 'nodemon',
12 silly mapToRegistry rawSpec: '',
12 silly mapToRegistry spec: 'latest',
12 silly mapToRegistry type: 'tag' }
13 silly mapToRegistry uri http://sinopia:4873/nodemon
14 verbose request uri http://sinopia:4873/nodemon
15 verbose request no auth needed
16 info attempt registry request try #1 at 7:03:41 PM
17 verbose request using bearer token for auth
18 verbose request id 80759680cac195d1
19 http request GET http://sinopia:4873/nodemon
20 info retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND sinopia sinopia:4873
21 info attempt registry request try #2 at 7:03:51 PM
22 verbose request using bearer token for auth
23 http request GET http://sinopia:4873/nodemon
24 info retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND sinopia sinopia:4873
25 info attempt registry request try #3 at 7:04:51 PM
26 verbose request using bearer token for auth
27 http request GET http://sinopia:4873/nodemon
28 silly fetchPackageMetaData Error: getaddrinfo ENOTFOUND sinopia sinopia:4873
28 silly fetchPackageMetaData at errnoException (dns.js:28:10)
28 silly fetchPackageMetaData at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:76:26)
28 silly fetchPackageMetaData error for nodemon { Error: getaddrinfo ENOTFOUND sinopia sinopia:4873
28 silly fetchPackageMetaData at errnoException (dns.js:28:10)
28 silly fetchPackageMetaData at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:76:26)
28 silly fetchPackageMetaData code: 'ENOTFOUND',
28 silly fetchPackageMetaData errno: 'ENOTFOUND',
28 silly fetchPackageMetaData syscall: 'getaddrinfo',
28 silly fetchPackageMetaData hostname: 'sinopia',
28 silly fetchPackageMetaData host: 'sinopia',
28 silly fetchPackageMetaData port: '4873' }
29 silly rollbackFailedOptional Starting
30 silly rollbackFailedOptional Finishing
31 silly runTopLevelLifecycles Finishing
32 silly install printInstalled
33 verbose stack Error: getaddrinfo ENOTFOUND sinopia sinopia:4873
33 verbose stack at errnoException (dns.js:28:10)
33 verbose stack at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:76:26)
34 verbose cwd /Users/pgreen/front-end-dev-book/chattrbox
35 error Darwin 16.7.0
36 error argv "/Users/pgreen/.nvm/versions/node/v6.10.3/bin/node" "/Users/pgreen/.nvm/versions/node/v6.10.3/bin/npm" "install" "--save-dev" "nodemon"
37 error node v6.10.3
38 error npm v3.10.10
39 error code ENOTFOUND
40 error errno ENOTFOUND
41 error syscall getaddrinfo
42 error network getaddrinfo ENOTFOUND sinopia sinopia:4873
43 error network This is most likely not a problem with npm itself
43 error network and is related to network connectivity.
43 error network In most cases you are behind a proxy or have bad network settings.
43 error network
43 error network If you are behind a proxy, please make sure that the
43 error network 'proxy' config is set properly. See: 'npm help config'
44 verbose exit [ 1, true ]