I have never used nodejs before. I just found out about the npm. If you wanted to install a package using npm, will you have to download the file first? If so, where do you put the file? would you place it in the same folder as the npm?
I tried to install faye with npm and this is what I got on the npm-debug.log:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'install',
1 verbose cli 'faye' ]
2 info using npm#2.7.4
3 info using node#v0.12.2
4 verbose node symlink C:\Program Files\nodejs\\node.exe
5 silly cache add args [ 'faye', null ]
6 verbose cache add spec faye
7 silly cache add parsed spec { raw: 'faye',
7 silly cache add scope: null,
7 silly cache add name: 'faye',
7 silly cache add rawSpec: '',
7 silly cache add spec: '*',
7 silly cache add type: 'range' }
8 verbose addNamed faye#*
9 silly addNamed semver.valid null
10 silly addNamed semver.validRange *
11 silly addNameRange { name: 'faye', range: '*', hasData: false }
12 silly mapToRegistry name faye
13 silly mapToRegistry using default registry
14 silly mapToRegistry registry https://registry.npmjs.org/
15 silly mapToRegistry uri https://registry.npmjs.org/faye
16 verbose addNameRange registry:https://registry.npmjs.org/faye not in flight; fetching
17 verbose request uri https://registry.npmjs.org/faye
18 verbose request no auth needed
19 info attempt registry request try #1 at 7:19:45 PM
20 verbose request id e2cc452cb2788a4b
21 http request GET https://registry.npmjs.org/faye
22 info retry will retry, error on last attempt: Error: connect EACCES
23 info attempt registry request try #2 at 7:19:55 PM
24 http request GET https://registry.npmjs.org/faye
25 info retry will retry, error on last attempt: Error: connect EACCES
26 info attempt registry request try #3 at 7:20:55 PM
27 http request GET https://registry.npmjs.org/faye
28 verbose stack Error: connect EACCES
28 verbose stack at exports._errnoException (util.js:746:11)
28 verbose stack at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1000:19)
29 verbose cwd C:\tito3
30 error Windows_NT 6.1.7601
31 error argv "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "faye"
32 error node v0.12.2
33 error npm v2.7.4
34 error code EACCES
35 error errno EACCES
36 error syscall connect
37 error Error: connect EACCES
37 error at exports._errnoException (util.js:746:11)
37 error at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1000:19)
37 error { [Error: connect EACCES] code: 'EACCES', errno: 'EACCES', syscall: 'connect' }
38 error Please try running this command again as root/Administrator.
39 verbose exit [ 1, true ]
Npm will download the relevant files for the module for you.
There are 2 modes of installing node modules using npm, either locally or globally. Locally (the default) means the modules are downloaded to a node_modules directory at the location you ran the command, so you would normally run this at the root of your app project. Globally (-g option) means it is downloaded to a location so it can be used by anything on your system I.e grunt_cli
The program files directory on windows is protected so you will need to run the command as an administrator, or run npm install from a non protect path such as c:\myapp
You might want to look at a package.json file, this is a file that allows you to list all your modules that you need for your app. Running just npm install in a location that contains a package.json will cause npm to read the file and download all your dependent modules for you.
Related
I recently installed node on my windows 8 computer and tested it and it seems to work fine. But when I try to install it I get this error
npm ERR! Windows_NT 6.2.9200
npm ERR! argv "C:\Program Files\nodejs\\node.exe" "C:\Program Files\nodejs
\node_modules\npm\bin\npm-cli.js" "install" "connect"
npm ERR! node v0.12.4
npm ERR! npm v2.10.1
npm ERR! code EACCES
npm ERR! errno EACCES
npm ERR! syscall connect
npm ERR! Error: connect EACCES
npm ERR! at exports._errnoException (util.js:746:11)
npm ERR! at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1010:19)
npm ERR! { [Error: connect EACCES] code: 'EACCES', errno: 'EACCES', syscall: 'c
onnect' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! Please include the following file with any support request:
npm ERR! C:\WINDOWS\system32\npm-debug.log
these are the contents of the npm-debug.log file from before I tried installing running cmd as administrator
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'install',
1 verbose cli 'connect' ]
2 info using npm#2.15.1
3 info using node#v4.4.3
4 verbose install initial load of C:\Users\owner\Desktop\Node.js\package.json
5 verbose readDependencies loading dependencies from C:\Users\owner\Desktop\Node.js\package.json
6 silly cache add args [ 'connect', null ]
7 verbose cache add spec connect
8 silly cache add parsed spec Result {
8 silly cache add raw: 'connect',
8 silly cache add scope: null,
8 silly cache add name: 'connect',
8 silly cache add rawSpec: '',
8 silly cache add spec: 'latest',
8 silly cache add type: 'tag' }
9 silly addNamed connect#latest
10 verbose addNamed "latest" is being treated as a dist-tag for connect
11 info addNameTag [ 'connect', 'latest' ]
12 silly mapToRegistry name connect
13 silly mapToRegistry using default registry
14 silly mapToRegistry registry https://registry.npmjs.org/
15 silly mapToRegistry data Result {
15 silly mapToRegistry raw: 'connect',
15 silly mapToRegistry scope: null,
15 silly mapToRegistry name: 'connect',
15 silly mapToRegistry rawSpec: '',
15 silly mapToRegistry spec: 'latest',
15 silly mapToRegistry type: 'tag' }
16 silly mapToRegistry uri https://registry.npmjs.org/connect
17 verbose addNameTag registry:https://registry.npmjs.org/connect not in flight; fetching
18 verbose request uri https://registry.npmjs.org/connect
19 verbose request no auth needed
20 info attempt registry request try #1 at 11:26:28 PM
21 verbose request id d04b099ed5c5d169
22 http request GET https://registry.npmjs.org/connect
23 info retry will retry, error on last attempt: Error: connect EACCES 23.235.40.162:443
24 info attempt registry request try #2 at 11:26:38 PM
25 http request GET https://registry.npmjs.org/connect
26 info retry will retry, error on last attempt: Error: connect EACCES 23.235.39.162:443
27 info attempt registry request try #3 at 11:27:38 PM
28 http request GET https://registry.npmjs.org/connect
29 verbose stack Error: connect EACCES 23.235.46.162:443
29 verbose stack at Object.exports._errnoException (util.js:870:11)
29 verbose stack at exports._exceptionWithHostPort (util.js:893:20)
29 verbose stack at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
30 verbose cwd C:\Users\owner\Desktop\Node.js
31 error Windows_NT 6.2.9200
32 error argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "connect"
33 error node v4.4.3
34 error npm v2.15.1
35 error code EACCES
36 error errno EACCES
37 error syscall connect
38 error Error: connect EACCES 23.235.46.162:443 38 error at Object.exports._errnoException (util.js:870:11)
38 error at exports._exceptionWithHostPort (util.js:893:20)
38 error at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
38 error { [Error: connect EACCES 23.235.46.162:443]
38 error code: 'EACCES',
38 error errno: 'EACCES',
38 error syscall: 'connect',
38 error address: '23.235.46.162',
38 error port: 443 }
39 error Please try running this command again as root/Administrator.
40 verbose exit [ 1, true ]
I have already tried running the command "npm install connect" as Administrator and got the same thing. Can anyone help?
The error occurs because you probably installed Node with root permissions but you're not executing npm with the same permissions. Permissions you used when installing Node will be required when doing things like writing in your npm directory (npm link, npm install -g, etc.).
The recommended way to fix this is by installing nvm-windows and using this to manage your Node installations. This prevents you from having to hack around the permissions on your machine.
I was looking for solutions to this problem in google.com, I read all related issues on this topic at stackoverflow.com. But the right answer is not found.
The problem is that for every command npm install -g (npm or yo or bower) go here such error:
C:\Users\User>npm install -g yo
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\
node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "yo"
npm ERR! node v4.2.1
npm ERR! npm v2.14.7
npm ERR! Invalid protocol: 192.168.10.1:
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\User\npm-debug.log
Installed operating system: Windows 7 (x86) Corporate.
Installed version Node.JS: 4.2.1 .
The content npm-debug.log file:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'install',
1 verbose cli '-g',
1 verbose cli 'yo' ]
2 info using npm#2.14.7
3 info using node#v4.2.1
4 verbose install initial load of C:\Users\User\AppData\Roaming\npm\package.json
5 verbose readDependencies loading dependencies from C:\Users\User\AppData\Roaming\npm\package.json
6 silly cache add args [ 'yo', null ]
7 verbose cache add spec yo
8 silly cache add parsed spec Result {
8 silly cache add raw: 'yo',
8 silly cache add scope: null,
8 silly cache add name: 'yo',
8 silly cache add rawSpec: '',
8 silly cache add spec: '*',
8 silly cache add type: 'range' }
9 silly addNamed yo#*
10 verbose addNamed "*" is a valid semver range for yo
11 silly addNameRange { name: 'yo', range: '*', hasData: false }
12 silly mapToRegistry name yo
13 silly mapToRegistry using default registry
14 silly mapToRegistry registry http://registry.npmjs.org/
15 silly mapToRegistry uri http://registry.npmjs.org/yo
16 verbose addNameRange registry:http://registry.npmjs.org/yo not in flight; fetching
17 verbose request uri http://registry.npmjs.org/yo
18 verbose request no auth needed
19 info attempt registry request try #1 at 16:59:12
20 verbose request id 4545121454874541214
21 http request GET http://registry.npmjs.org/yo
22 info retry will retry, error on last attempt: Error: Invalid protocol: 192.168.10.1:
23 info attempt registry request try #2 at 16:59:22
24 http request GET http://registry.npmjs.org/yo
25 info retry will retry, error on last attempt: Error: Invalid protocol: 192.168.10.1:
26 info attempt registry request try #3 at 17:00:22
27 http request GET http://registry.npmjs.org/yo
28 verbose stack Error: Invalid protocol: 192.168.10.1:
28 verbose stack at Request.init (C:\Program Files\nodejs\node_modules\npm\node_modules\request\request.js:461:31)
28 verbose stack at new Request (C:\Program Files\nodejs\node_modules\npm\node_modules\request\request.js:140:8)
28 verbose stack at request (C:\Program Files\nodejs\node_modules\npm\node_modules\request\index.js:55:10)
28 verbose stack at CachingRegistryClient.makeRequest (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-registry-client\lib\request.js:149:13)
28 verbose stack at C:\Program Files\nodejs\node_modules\npm\node_modules\npm-registry-client\lib\request.js:66:17
28 verbose stack at RetryOperation._fn (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-registry-client\lib\attempt.js:18:5)
28 verbose stack at null._onTimeout (C:\Program Files\nodejs\node_modules\npm\node_modules\retry\lib\retry_operation.js:49:10)
28 verbose stack at Timer.listOnTimeout (timers.js:92:15)
29 verbose cwd C:\Users\User
30 error Windows_NT 6.1.7601
31 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "yo"
32 error node v4.2.1
33 error npm v2.14.7
34 error Invalid protocol: 192.168.10.1:
35 error If you need help, you may report this error at:
35 error <https://github.com/npm/npm/issues>
36 verbose exit [ 1, true ]
Why leave such a mistake? What's the problem here? How to solve this problem? Thank you in advance for help
My computer connects Internet through a proxy server. By this, I changed the configuration npm on:
npm config set http-proxy http://192.168.10.1:3128
npm config set https-proxy https://192.168.10.1:3128
npm config set registry http://registry.npmjs.org/
npm config set strict-ssl=false
here is my solution
npm config set http-proxy http://192.168.10.1
I had the same problem while installing native scripts. Try using the following commands:
set http
set http_proxy=
This will help you.
I'm trying to republish a package using npm. I did update the package version in package.json, yet I get the following error:
npm ERR! publish Failed PUT 404
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs
\\node_modules\\npm\\bin\\npm-cli.js" "publish"
npm ERR! node v0.12.3
npm ERR! npm v2.9.1
npm ERR! code E404
npm ERR! 404 missing : #psychodelicgod/npm
npm ERR! 404
npm ERR! 404 '#psychodelicgod/npm' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\Michał Szydłowski\npm\npm-debug.log
and my debug.log:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'publish' ]
2 info using npm#2.9.1
3 info using node#v0.12.3
4 verbose node symlink C:\Program Files\nodejs\\node.exe
5 verbose publish [ '.' ]
6 silly cache add args [ '.', null ]
7 verbose cache add spec .
8 silly cache add parsed spec { raw: '.',
8 silly cache add scope: null,
8 silly cache add name: null,
8 silly cache add rawSpec: '.',
8 silly cache add spec: 'C:\\Users\\Michał Szydłowski\\npm',
8 silly cache add type: 'directory' }
9 verbose addLocalDirectory C:\Users\Michał Szydłowski\AppData\Roaming\npm-cache\#psychodelicgod\npm\1.0.2\package.tgz not in flight; packing
10 verbose tar pack [ 'C:\\Users\\Michał Szydłowski\\AppData\\Roaming\\npm-cache\\#psychodelicgod\\npm\\1.0.2\\package.tgz',
10 verbose tar pack 'C:\\Users\\Michał Szydłowski\\npm' ]
11 verbose tarball C:\Users\Michał Szydłowski\AppData\Roaming\npm-cache\#psychodelicgod\npm\1.0.2\package.tgz
12 verbose folder C:\Users\Michał Szydłowski\npm
13 info prepublish #psychodelicgod/npm#1.0.2
14 verbose addLocalTarball adding from inside cache C:\Users\Michał Szydłowski\AppData\Roaming\npm-cache\#psychodelicgod\npm\1.0.2\package.tgz
15 silly cache afterAdd #psychodelicgod/npm#1.0.2
16 verbose afterAdd C:\Users\Michał Szydłowski\AppData\Roaming\npm-cache\#psychodelicgod\npm\1.0.2\package\package.json not in flight; writing
17 verbose afterAdd C:\Users\Michał Szydłowski\AppData\Roaming\npm-cache\#psychodelicgod\npm\1.0.2\package\package.json written
18 silly publish { name: '#psychodelicgod/npm',
18 silly publish version: '1.0.2',
18 silly publish description: 'd',
18 silly publish main: 'index.js',
18 silly publish scripts: { test: 'node test.js' },
18 silly publish author: '',
18 silly publish license: 'ISC',
18 silly publish dependencies: { '#linclark/pkg': '^1.0.2' },
18 silly publish repository: { type: 'git', url: 'C:\\Users\\Michał Szydłowski\\npm' },
18 silly publish readme: 'Sample description.',
18 silly publish readmeFilename: 'README.md',
18 silly publish _id: '#psychodelicgod/npm#1.0.2',
18 silly publish _shasum: 'b66a8a42e64f0a2b8166ce511629e107d47ab027',
18 silly publish _from: '.' }
19 verbose getPublishConfig undefined
20 silly mapToRegistry name #psychodelicgod/npm
21 silly mapToRegistry scope (from package name) #psychodelicgod
22 verbose mapToRegistry no registry URL found in name for scope #psychodelicgod
23 silly mapToRegistry using default registry
24 silly mapToRegistry registry http://localhost:15443/
25 silly mapToRegistry uri http://localhost:15443/#psychodelicgod%2fnpm
26 verbose publish registryBase http://localhost:15443/
27 silly publish uploading C:\Users\Michał Szydłowski\AppData\Roaming\npm-cache\#psychodelicgod\npm\1.0.2\package.tgz
28 verbose request uri http://localhost:15443/#psychodelicgod%2fnpm
29 verbose request sending authorization for write operation
30 info attempt registry request try #1 at 13:11:50
31 verbose request id e5c460330af2176f
32 http request PUT http://localhost:15443/#psychodelicgod%2fnpm
33 http 404 http://localhost:15443/#psychodelicgod%2fnpm
34 verbose headers { 'content-type': 'application/json',
34 verbose headers date: 'Fri, 03 Jul 2015 11:11:50 GMT',
34 verbose headers connection: 'keep-alive',
34 verbose headers 'transfer-encoding': 'chunked' }
35 verbose request invalidating C:\Users\Michał Szydłowski\AppData\Roaming\npm-cache\localhost_15443\_40psychodelicgod_252fnpm on PUT
36 error publish Failed PUT 404
37 verbose stack Error: missing : #psychodelicgod/npm
37 verbose stack at CachingRegistryClient.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-registry-client\lib\request.js:247:14)
37 verbose stack at Request._callback (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-registry-client\lib\request.js:170:14)
37 verbose stack at Request.self.callback (C:\Program Files\nodejs\node_modules\npm\node_modules\request\request.js:368:22)
37 verbose stack at Request.emit (events.js:110:17)
37 verbose stack at Request.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\request\request.js:1219:14)
37 verbose stack at Request.emit (events.js:129:20)
37 verbose stack at IncomingMessage.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\request\request.js:1167:12)
37 verbose stack at IncomingMessage.emit (events.js:129:20)
37 verbose stack at _stream_readable.js:908:16
37 verbose stack at process._tickCallback (node.js:355:11)
38 verbose statusCode 404
39 verbose pkgid #psychodelicgod/npm
40 verbose cwd C:\Users\Michał Szydłowski\npm
41 error Windows_NT 6.3.9600
42 error argv "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "publish"
43 error node v0.12.3
44 error npm v2.9.1
45 error code E404
46 error 404 missing : #psychodelicgod/npm
46 error 404
46 error 404 '#psychodelicgod/npm' is not in the npm registry.
46 error 404 You should bug the author to publish it (or use the name yourself!)
46 error 404
46 error 404 Note that you can also install from a
46 error 404 tarball, folder, http url, or git url.
47 verbose exit [ 1, true ]
I've tried several similar answers here, but none of this is helping. Any ideas?
#To publish on npm registry
You need to create npm user. You can follow here.
In short
npm adduser
npm login
Do npm config ls to ensure that credentials are stored on your client.
Then try
npm publish.
To install it locally OR test packaging your module
You can try
tar -tf $(npm pack)
npm install <path/to/your/package.tgz>
I checked here and here for references.
I also had the same problem.
for me the email was not verified.
You can login on npmjs.org and verify the email.
I don't know, What happen in your code during installation package. Please check here : https://docs.npmjs.com/getting-started/creating-node-modules to take a look how to install package modules.
These are simple way to install package :
Publish your package to npm
Make a new directory outside of your project and cd into it
Run npm install <package>
Create a test.js file which requires the package and calls the method
Run node test.js. The message should be output.
From log, I have noticed following exception
36 error publish Failed PUT 404
37 verbose stack Error: missing : #psychodelicgod/npm
Either you seems to be logged out or You need to have registered npm adduser "psychodelicgod" as a username at the registry and be logged in to publish under that scope. Please have a look at "Working with scoped packages" and "publishing NPM Packages"
404 errors when publishing is mainly due to access errors. It could be an access token error or a read-write error. Please check your access settings on the organization package permissions page.
If you are publishing for the first time from your local machine, use npm login to create an access token on your account. Once logged in, the token will be automatically added to your global npmrc file and you can try publishing again.
If you are trying to update a package and seeing the 404 error, please enable read-write permission on your organization settings for the package.
If you are using a CI/CD pipeline tool, specifying the scope is mandatory and use the access token that has read-write permission.
There is (as of writing) a bug in npmjs.org's implementation of the npm server which does not provide useful information when a package fails to publish. If you're using npmjs.org within the scope of an organization, ensure that your user's permissions are read-write. This seems obvious, of course, but the error presented would indicate that the repository for which an update is being attempted is either non-existent, or at least invisible to the user attempting the publish. In fact, the user may be able to see the package when searching, but be told the package does not exist when attempting to publish.
Perhaps there is a similar issue with your npm server.
I've a problem with the installation for yeoman, bower, grunt and the latest npm version.
The latest version of NodeJS (0.12.2) is installed on my pc.
I have the npm version 2.7.4 but when I start the git bash in the nodejs folder and type "npm install npm" or "npm install npm#latest" then it gives an error message:
error Windows_NT 6.1.7601
error argv "c:\\Program Files\\nodejs\\node.exe" "c:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "npm#latest"
error node v0.12.2
error npm v2.7.4
error code ETIMEDOUT
error errno ETIMEDOUT
error syscall connect
error network connect ETIMEDOUT
error network This is most likely not a problem with npm itself
error network and is related to network connectivity.
error network In most cases you are behind a proxy or have bad network settings.
error network
error network If you are behind a proxy, please make sure that the
error network 'proxy' config is set properly. See: 'npm help config'
verbose exit [ 1, true ]
And the complete debug log:
0 info it worked if it ends with ok
1 verbose cli [ 'c:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'c:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'install',
1 verbose cli 'npm#latest' ]
2 info using npm#2.7.4
3 info using node#v0.12.2
4 warn package.json nodejs#0.12.2 No description
5 warn package.json nodejs#0.12.2 No repository field.
6 warn package.json nodejs#0.12.2 No README data
7 silly cache add args [ 'npm#latest', null ]
8 verbose cache add spec npm#latest
9 silly cache add parsed spec { raw: 'npm#latest',
9 silly cache add scope: null,
9 silly cache add name: 'npm',
9 silly cache add rawSpec: 'latest',
9 silly cache add spec: 'latest',
9 silly cache add type: 'tag' }
10 verbose addNamed npm#latest
11 silly addNamed semver.valid null
12 silly addNamed semver.validRange null
13 info addNameTag [ 'npm', 'latest' ]
14 silly mapToRegistry name npm
15 silly mapToRegistry using default registry
16 silly mapToRegistry registry https://registry.npmjs.org/
17 silly mapToRegistry uri https://registry.npmjs.org/npm
18 verbose addNameTag registry:https://registry.npmjs.org/npm not in flight; fetching
19 verbose request uri https://registry.npmjs.org/npm
20 verbose request no auth needed
21 info attempt registry request try #1 at 09:30:04
22 verbose request id 6fa6dc64e92e52cc
23 http request GET https://registry.npmjs.org/npm
24 info retry will retry, error on last attempt: Error: connect ETIMEDOUT
25 info attempt registry request try #2 at 09:30:35
26 http request GET https://registry.npmjs.org/npm
27 info retry will retry, error on last attempt: Error: connect ETIMEDOUT
28 info attempt registry request try #3 at 09:31:56
29 http request GET https://registry.npmjs.org/npm
30 verbose stack Error: connect ETIMEDOUT
30 verbose stack at exports._errnoException (util.js:746:11)
30 verbose stack at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1000:19)
31 verbose cwd c:\Program Files\nodejs
I've read some threads with problems of nodejs and found an ability to set the http proxy. Is that the solution?
I've solved my problem. To find out my proxy-server name on windows 7 I've opened command line of windows and type: netsh winhttp show proxy
Then I added these lines in the .npmrc data (path:C:\users\username)
registry=http://registry.npmjs.org/
strict-ssl=false
proxy=http://username:password#proxy.domain.com:8080/
https-proxy=http://username:password#proxy.domain.com:8080
It works fine :)
I am trying to install node.js on a LAN that is not connected to the web. I've installed node.js with no problems, but it appears that npm wants to go out to the web, http GET https://registry.npmjs.org/moment so I can't install the modules that I need.
Here is the npm-debug file that is produced:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'install',
1 verbose cli 'moment',
1 verbose cli '-g' ]
2 info using npm#1.1.69
3 info using node#v0.8.16
4 verbose node symlink C:\Program Files\nodejs\\node.exe
5 verbose read json C:\Documents and Settings\User.PALS-DADS\Application Data\npm\package.json
6 verbose read json C:\Documents and Settings\User.PALS-DADS\Application Data\npm\package.json
7 verbose cache add [ 'moment', null ]
8 silly cache add name=undefined spec="moment" args=["moment",null]
9 verbose parsed url { pathname: 'moment', path: 'moment', href: 'moment' }
10 silly lockFile b56def36-moment moment
11 verbose lock moment C:\Documents and Settings\User.PALS-DADS\Application Data\npm-cache\b56def36-moment.lock
12 silly lockFile b56def36-moment moment
13 verbose addNamed [ 'moment', '' ]
14 verbose addNamed [ null, '' ]
15 silly lockFile 42aa250a-moment moment#
16 verbose lock moment# C:\Documents and Settings\User.PALS-DADS\Application Data\npm-cache\42aa250a-moment.lock
17 silly addNameRange { name: 'moment', range: '', hasData: false }
18 verbose url raw moment
19 verbose url resolving [ 'https://registry.npmjs.org/', './moment' ]
20 verbose url resolved https://registry.npmjs.org/moment
21 info trying registry request attempt 1 at 16:47:42
22 http GET https://registry.npmjs.org/moment
23 info retry will retry, error on last attempt: Error: getaddrinfo ENOENT
24 info trying registry request attempt 2 at 16:47:52
25 http GET https://registry.npmjs.org/moment
26 info retry will retry, error on last attempt: Error: getaddrinfo ENOENT
27 info trying registry request attempt 3 at 16:48:52
28 http GET https://registry.npmjs.org/moment
29 silly lockFile 42aa250a-moment moment#
30 error Error: getaddrinfo ENOENT
30 error at errnoException (dns.js:31:11)
30 error at Object.onanswer [as oncomplete] (dns.js:123:16)
31 error If you need help, you may report this log at:
31 error
31 error or email it to:
31 error
32 error System Windows_NT 5.1.2600
33 error command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "moment" "-g"
34 error cwd C:\Documents and Settings\User.PALS-DADS\Desktop
35 error node -v v0.8.16
36 error npm -v 1.1.69
37 error syscall getaddrinfo
38 error code ENOTFOUND
39 error errno ENOTFOUND
40 verbose exit [ 1, true ]
How can I install modules without connecting to the net?
Thanks
If you take a look at the docs, you'll see that you can install packages by simply passing a filesystem path or URL to a tarball that contains the package you want to install.
npm install http://server.on.lan/moment.tgz
Of course, if the package in question specifies any dependencies, npm will try to fetch them from the web. moment doesn't have any, so you should be able to just download the tarball and install it.
However, if you want to install other packages which do have dependencies, you might be better off setting up a npm registry mirror on your LAN.