nodists / nodist Goto Github PK

View Code? Open in Web Editor NEW

1.6K 62.0 209.0 17.19 MB

Natural node.js and npm version manager for windows.

License: MIT License

Shell 1.27% PowerShell 2.07% JavaScript 75.84% Go 12.83% Batchfile 0.47% NSIS 7.52%

javascript nodejs version-control version-manager

nodist's People

Contributors

Stargazers

Watchers

Forkers

meechn revskill10 lgi mazeme jdiamond nsbingham gratex fschwiet pat-li yskkym cycoph joeeames shakakira mamorh nkm8 me-soft yuqigong blzaugg dctse jakub-g skychoo ddropik eabglobal kevnz takumari85 sdovenor robrich gitter-badger caiotoon mndewitt yukisan kawasaki2013 cometcomet tombyrer cihejimba iulo cadconsultants tomoe-martop opdmmuto bhon03 gmahomarf marcbuils cloned2k16 maekztn jantimon fusion-com-au atoz-chevara genavarov kreativepy fluensh gzgogo ernsheong rlugojr snyk-community zhyt201 jepsonw cnpm hyleong karthizeyan maru2222 web725 kode-kitchen zbm2001 bitmybytes stradap acidburn0zzz clickap-ionic harendranathvegi9 niilante daisy0123 lance4git mahesh1 jasontangts javascriptexpert redisck afsarker yumetodo viking-man xlelou gin49 shimazu475 bsyslient parkyoungwoong kenjiohtsuka aaliabbaas vaginessa mscherer82 fullstackenviormentss sdtm1016 leaves-27 psymania shurikus2402 miki-ichikawa-wi outerwks pjobs astrata-eu zk47 ulterpendragon oacosmic connorchallis

nodist's Issues

How do I run the tests?

I am seeing some test failures, given I can change the result be installing node v0.8.0, I do not think I am running the tests correctly. Here is sample output. First 3 tests fail. Looking at the tests, I experiment and install v0.8.0. Then, only 2 tests fail.
My c:\tmp\v directory is empty, it looks like thats where test installs should go.

C:\src\nodist [master +1 ~0 -0 !]> .\node.exe .\test\cli-test.js
· ? ? ?·

    nodist list
      ? should list the installed version
        » expected expression to evaluate to true, but was false // cli-test.js:35

    nodist run
      ? should run the specified version
        » expected expression to evaluate to true, but was null // cli-test.js:44

    nodist rm
      ? should remove the specified version
        » expected expression to evaluate to true, but was false // cli-test.js:53
  ? Broken » 2 honored · 3 broken (27.894s)
  C:\src\nodist [master +1 ~0 -0 !]> .\bin\nodist.cmd
No builds installed, yet.
C:\src\nodist [master +1 ~0 -0 !]> .\bin\nodist.cmd + 0.8.0
0.8.0
C:\src\nodist [master +1 ~0 -0 !]> .\bin\nodist.cmd list
  0.8.0
C:\src\nodist [master +1 ~0 -0 !]> .\node.exe .\test\cli-test.js
· ? ? ··

    nodist list
      ? should list the installed version
        » expected expression to evaluate to true, but was false // cli-test.js:35

    nodist run
      ? should run the specified version
        » expected expression to evaluate to true, but was null // cli-test.js:44
  ? Broken » 3 honored · 2 broken (7.059s)

Issue on Windows Fresh install

C:\Utils\nodist>nodist update
        1 file(s) copied.
npm http GET https://registry.npmjs.org/npm
npm http 304 https://registry.npmjs.org/npm
npm http GET https://registry.npmjs.org/npm/1.3.8
npm http 304 https://registry.npmjs.org/npm/1.3.8
npm WARN package.json github-url-from-git@1.1.1 No repository field.
C:\Utils\nodist\bin\npm -> C:\Utils\nodist\bin\node_modules\npm\bin\npm-cli.js
npm@1.3.8 C:\Utils\nodist\bin\node_modules\npm
'C:\Utils\nodist\bin\\node_modules\npm\bin\npm-cli.js" update npm -g' is not recognized as an internal or external command,
operable program or batch file.
        1 file(s) moved.
npm http GET https://registry.npmjs.org/request
npm http GET https://registry.npmjs.org/semver
npm http GET https://registry.npmjs.org/rimraf
npm http GET https://registry.npmjs.org/mkdirp
npm http 304 https://registry.npmjs.org/semver
npm http 304 https://registry.npmjs.org/mkdirp
npm ERR! TypeError: Cannot read property 'from' of undefined
npm ERR!     at C:\Utils\nodist\bin\node_modules\npm\lib\outdated.js:159:36
npm ERR!     at C:\Utils\nodist\bin\node_modules\npm\lib\cache.js:591:30
npm ERR!     at exports.unlock (C:\Utils\nodist\bin\node_modules\npm\node_modules\lockfile\lockfile.js:55:41)
npm ERR!     at Object.oncomplete (fs.js:297:15)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Utils\\nodist\\bin\\\\node.exe" "C:\\Utils\\nodist\\bin\\node_modules\\npm\\cli.js" "update"
npm ERR! cwd C:\Utils\nodist
npm ERR! node -v v0.8.9
npm ERR! npm -v 1.3.8
npm ERR! type non_object_property_load
npm http 304 https://registry.npmjs.org/request
npm http 304 https://registry.npmjs.org/rimraf
npm ERR! TypeError: Cannot read property 'from' of undefined
npm ERR!     at C:\Utils\nodist\bin\node_modules\npm\lib\outdated.js:159:36
npm ERR!     at C:\Utils\nodist\bin\node_modules\npm\lib\cache.js:591:30
npm ERR!     at exports.unlock (C:\Utils\nodist\bin\node_modules\npm\node_modules\lockfile\lockfile.js:55:41)
npm ERR!     at Object.oncomplete (fs.js:297:15)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Utils\\nodist\\bin\\\\node.exe" "C:\\Utils\\nodist\\bin\\node_modules\\npm\\cli.js" "update"
npm ERR! cwd C:\Utils\nodist
npm ERR! node -v v0.8.9
npm ERR! npm -v 1.3.8
npm ERR! type non_object_property_load
npm ERR! TypeError: Cannot read property 'from' of undefined
npm ERR!     at C:\Utils\nodist\bin\node_modules\npm\lib\outdated.js:159:36
npm ERR!     at C:\Utils\nodist\bin\node_modules\npm\lib\cache.js:591:30
npm ERR!     at exports.unlock (C:\Utils\nodist\bin\node_modules\npm\node_modules\lockfile\lockfile.js:55:41)
npm ERR!     at Object.oncomplete (fs.js:297:15)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Utils\\nodist\\bin\\\\node.exe" "C:\\Utils\\nodist\\bin\\node_modules\\npm\\cli.js" "update"
npm ERR! cwd C:\Utils\nodist
npm ERR! node -v v0.8.9
npm ERR! npm -v 1.3.8
npm ERR! type non_object_property_load
npm ERR! TypeError: Cannot read property 'from' of undefined
npm ERR!     at C:\Utils\nodist\bin\node_modules\npm\lib\outdated.js:159:36
npm ERR!     at C:\Utils\nodist\bin\node_modules\npm\lib\cache.js:591:30
npm ERR!     at exports.unlock (C:\Utils\nodist\bin\node_modules\npm\node_modules\lockfile\lockfile.js:55:41)
npm ERR!     at Object.oncomplete (fs.js:297:15)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Utils\\nodist\\bin\\\\node.exe" "C:\\Utils\\nodist\\bin\\node_modules\\npm\\cli.js" "update"
npm ERR! cwd C:\Utils\nodist
npm ERR! node -v v0.8.9
npm ERR! npm -v 1.3.8
npm ERR! type non_object_property_load
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     C:\Utils\nodist\npm-debug.log
npm ERR! not ok code 0

C:\Utils\nodist>

Version activated in current env not propagated to npm


PS C:\tmp> nodist ls
> 0.10.24
  0.11.9

PS C:\tmp> nodist use latest
0.11.9

PS C:\projects\koa-test> npm install -save koa koa-common
[ - - - ]
npm WARN engine [email protected]: wanted: {"node":">= 0.11.9"} (current: {"node":"v0.10.24","npm":"1.3.21"})
[ - - - ]

Doing "nodist latest" instead of "nodist use latest" causes the warnings to disappear.

`nodist bin` is broken for generic versions

nodist bin stable outputs path\to\nodist\v\stable\node.exe

cannot find module 'semver'

I checked out the current build of nodist and added the path to the enviroment path. Nevertheless executing nodist in command line gets me the error:

'''module.js:340
throw err;
^
Error: Cannot find module 'semver'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:362:17)
at require (module.js:378:17)
at Object. (C:\Program Files (x86)\nodist\lib\versions.js:1:76)
at Module._compile (module.js:449:26)
at Object.Module._extensions..js (module.js:467:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:362:17)
'''

I solved this by moving the node_modules directory of nodist/bin/node_modules/npm/node_modules/semver/ to nodist/node_modules/

two node_modules directories, and binaries littered in the root

Now since you have stuffed node.exe to the root, I had to add it to the path, see previous bugs.

Suppose I have installed nodist to the: C:\nodist\

I run npm install -g less jshint recess uglify-js and all of the binaries gets installed to the root: C:\nodist\ and not to the C:\nodist\bin\

Also now I have two npm_modules:

C:\nodist\npm_modules and C:\nodist\bin\npm_modules

Whats going on here? Did you accidentally put the node.exe in the root, when you were supposed to put it bin?

Install failed

OS: Windows 7 64Bit
Command prompt as admin

npm ERR! [email protected] install: `bin\install.cmd`
npm ERR! `cmd "/c" "bin\\install.cmd"` failed with 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the nodist package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     bin\install.cmd
npm ERR! You can get their info via:
npm ERR!     npm owner ls nodist
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nod
ejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "nodist"
npm ERR! cwd C:\Users\***
npm ERR! node -v v0.8.1
npm ERR! npm -v 1.1.33
npm ERR! code ELIFECYCLE
npm ERR! message [email protected] install: `bin\install.cmd`
npm ERR! message `cmd "/c" "bin\\install.cmd"` failed with 1
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     C:\Users\***\npm-debug.log
npm ERR! not ok code 0

Cache the results of n.listAvailable

Update to npm 1.4.24 does not execute update script correctly

See npm/npm#6045. Here are the relevant parts:

@UltCombo:

I've just tried to update npm from version 1.4.23 (running npm update npm -g), at some point in the process it executes the following CLI command:

"C:\nodist\bin\\node_modules\npm\bin\npm-cli.js" update npm -g

Thing is, Windows simply ignores the #!/usr/bin/env node directive and opens the file with the given extension (.js)'s associated default executable (in my case, Sublime Text 3), so the update just breaks there.

I believe it should be easy to fix, simply prefix the command with node, so it would end up with:

node "path/to/npm-cli.js" update npm -g

@othiym23:

This is definitely a nodist issue and not an npm one – npm rewrites the shebangs itself and also won't invoke itself without a node binary on the command line. Ideally this command would be invoked via node.cmd, so it's possible there's some kind of PATH hijinx going on. Either way, this isn't an npm problem.

Cannot find module 'mkdirp'

No matter where I run nodist update from, the modules don't seem to be installing to the right location. Tried it in good ol command prompt, as well as the git bash shell. I checked the nodist folder where I install it and there are no modules in the node_modules folder. I also tried NPM installing using the package.json in the nodist root, but all I get is Invalid password errors on random modules.

Here is an example of the error:

C:\Users\Neo\Projects>nodist update
        1 file(s) copied.
npm WARN package.json [email protected] No README.md file found!
        1 file(s) moved.
npm http GET https://registry.npmjs.org/request
npm http GET https://registry.npmjs.org/semver
npm http GET https://registry.npmjs.org/rimraf
npm http GET https://registry.npmjs.org/mkdirp
npm http 401 https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/mkdirp
npm http 401 https://registry.npmjs.org/rimraf
npm http 401 https://registry.npmjs.org/semver
npm http 401 https://registry.npmjs.org/request
npm http 401 https://registry.npmjs.org/mkdirp

C:\Users\Neo\Projects>nodist + v0.10.8

module.js:340
    throw err;
          ^
Error: Cannot find module 'mkdirp'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:362:17)
    at require (module.js:378:17)
    at Object.<anonymous> (C:\Users\Neo\Projects\nodist\lib\nodist.js:27:18)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:362:17)

Global NPM packages

I'm a little confused as to how NPM global packages are supposed to work. NPM packages installed with the global -g flag seem to get put in the node_modules folder in the active Node version folder.
.../nodist/v/0.10.31/bower.cmd

As these folders aren't added to the PATH variable there is no way to actually call any of your standard tools like bower or grunt without manually adding them to your PATH. Is this the expected behaviour when installing global packages? As far as I can tell, there is a global NPM version and I would have expected global dependencies to be installed in nodist/node_modules or similar.

previous node installation : how to desinstall ?

I tried to install and use nodist, but i had a previous installation of node.

It seems to work, but when i tried to install phonegap later, it failed because it found the worng node version (0.8.9), despite node -v answers 0.10.2

What can i do ?

Do i have to make a complete node uninstall ?
If yes, how ?

'node' is not recognized as an internal or external command

I get error:

C:\Users\...>nodist update
npm http GET https://registry.npmjs.org/npm
npm http 304 https://registry.npmjs.org/npm
npm http GET https://registry.npmjs.org/npm/1.1.68
npm http 304 https://registry.npmjs.org/npm/1.1.68
C:\...\node\bin\npm -> C:\...\node\bin\node_modules\npm\bin\npm-cli.js
[email protected] C:\...\node\bin\node_modules\npm
The system cannot find the path specified.
'node' is not recognized as an internal or external command,
operable program or batch file.

Your installation instructions are missing a one important ingredient: Add ...path...\nodist\ to your path also, the bin is not enough since node.exe is in the root directory.

Now I tried to install it also by adding only bin/ to path, then going to root directory and running. It works, but node.exe is not added to the path. And also I couldn't get the nodist stable ... commands to work.

error: EBUSY on node.exe

I'm on windows 8.0. I removed node, used chocolately to install, and rebooted. I'm getting this error when trying to switch versions.

C:\apps\bath>nodist 0.11.13
Couldn't activate version 0.11.13 (EBUSY, open 'C:\Chocolatey\lib\nodist.0.4.6-beta\tools\nodist-master\bin\node.exe').
Sorry.

Now module Installation failed ..... throwing error in windows

npm install now -g

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 'now',
1 verbose cli '-g' ]
2 info using [email protected]
3 info using [email protected]
4 verbose node symlink C:\Program Files\nodejs\node.exe
5 verbose read json C:\Users\user\AppData\Roaming\npm\package.json
6 verbose read json C:\Users\user\AppData\Roaming\npm\package.json
7 verbose cache add [ 'now', null ]
8 silly cache add name=undefined spec="now" args=["now",null]
9 verbose parsed url { pathname: 'now', path: 'now', href: 'now' }
10 silly lockFile c9bc849a-now now
11 verbose lock now C:\Users\user\AppData\Roaming\npm-cache\c9bc849a-now.lock
12 silly lockFile c9bc849a-now now
13 verbose addNamed [ 'now', '' ]
14 verbose addNamed [ null, '' ]
15 silly lockFile 1193e862-now now@
16 verbose lock now@ C:\Users\user\AppData\Roaming\npm-cache\1193e862-now.lock
17 silly addNameRange { name: 'now', range: '', hasData: false }
18 verbose url raw now
19 verbose url resolving [ 'https://registry.npmjs.org/', './now' ]
20 verbose url resolved https://registry.npmjs.org/now
21 info trying registry request attempt 1 at 16:44:59
22 verbose etag "3Y8902A5BHD3AB8LKPLP99SC8"
23 http GET https://registry.npmjs.org/now
24 http 304 https://registry.npmjs.org/now
25 silly registry.get cb [ 304,
25 silly registry.get { server: 'CouchDB/1.2.0 (Erlang OTP/R15B)',
25 silly registry.get etag: '"3Y8902A5BHD3AB8LKPLP99SC8"',
25 silly registry.get date: 'Wed, 12 Sep 2012 11:15:03 GMT',
25 silly registry.get 'content-length': '0' } ]
26 verbose etag now from cache
27 silly addNameRange number 2 { name: 'now', range: '', hasData: true }
28 silly addNameRange versions [ 'now',
28 silly addNameRange [ '0.2.0',
28 silly addNameRange '0.2.1',
28 silly addNameRange '0.2.2',
28 silly addNameRange '0.2.3',
28 silly addNameRange '0.2.4',
28 silly addNameRange '0.3.0',
28 silly addNameRange '0.3.1',
28 silly addNameRange '0.3.2',
28 silly addNameRange '0.5.0',
28 silly addNameRange '0.5.1',
28 silly addNameRange '0.5.2',
28 silly addNameRange '0.5.3',
28 silly addNameRange '0.6.0',
28 silly addNameRange '0.6.1',
28 silly addNameRange '0.7.0',
28 silly addNameRange '0.7.1',
28 silly addNameRange '0.7.2',
28 silly addNameRange '0.7.3',
28 silly addNameRange '0.7.4',
28 silly addNameRange '0.7.5',
28 silly addNameRange '0.7.6',
28 silly addNameRange '0.8.0',
28 silly addNameRange '0.8.1' ] ]
29 verbose addNamed [ 'now', '0.8.1' ]
30 verbose addNamed [ '0.8.1', '0.8.1' ]
31 silly lockFile 00d2b6cb-now-0-8-1 [email protected]
32 verbose lock [email protected] C:\Users\user\AppData\Roaming\npm-cache\00d2b6cb-now-0-8-1.lock
33 verbose read json C:\Users\user\AppData\Roaming\npm-cache\now\0.8.1\package\package.json
34 silly lockFile 00d2b6cb-now-0-8-1 [email protected]
35 silly lockFile 1193e862-now now@
36 silly resolved [ { author: { name: 'Flotype' },
36 silly resolved name: 'now',
36 silly resolved description: 'NowJS: An easy to use real-time RPC library',
36 silly resolved version: '0.8.1',
36 silly resolved repository: { type: 'git', url: 'git://github.com/Flotype/now.git' },
36 silly resolved main: 'lib/server.js',
36 silly resolved engines: { node: '>= v0.4.0' },
36 silly resolved dependencies: { 'socket.io': '>= 0.8.7', 'node-proxy': '>= 0.4.0' },
36 silly resolved devDependencies: {},
36 silly resolved readme: 'Get NowJS http://www.nowjs.com/\n=========\n\n###NowJS makes realtime web apps really easy.\n\n\nGo to Github or \nDownload the master tgz\n\n\nInstall From npm\n----------------\n\nnpm install now or npm install now -g to install globally\n\n\n\nNowJS is a Node.js module. The client javascript (now.js) is served by the NowJS server.\n\n\nNowJS uses the excellent socket.io and node-proxy libraries.\n\n2 Step Setup\n==============\n\n1. On the server\n\n \n var httpServer = require('http').createServer(function(req, response){ /* Serve your static files / })\n httpServer.listen(8080);\n \n var nowjs = require("now");\n var everyone = nowjs.initialize(httpServer);\n \n everyone.now.logStuff = function(msg){\n console.log(msg);\n }\n \n__2. On the client_\n

\n<script type="text/javascript" src="http://localhost:8080/nowjs/now.js"></script>\n\n<script type="text/javascript">\n  now.ready(function(){\n    // "Hello World!" will print on server\n    now.logStuff("Hello World!");\n  });\n</script>\n

\n\nFAQ\n-------\n\n__Q: Can I pass in a callback or closure, for example, if the remote function is asynchronous?\n\nA: Yes. This is 100% supported\n\n\n__Q: How do I use NowJS with Express?\n\nA: Very easily. \n var app = express.createServer();\n app.listen(3000);\n var everyone = require("now").initialize(app);\n\n__Q: How do I disable WebSockets or only use xhr-polling?\n\nA: You can specifiy exactly which transports to use as an initialization options as follows:\n \n var nowjs = require("now");\n var everyone = nowjs.initialize(yourHttpServer, {socketio: {transports: ['xhr-polling', 'jsonp-polling']}});\n\n\n__Q: Error: " SyntaxError: Unexpected token *" / Can I statically host the now.js file?\n\nA: On the client side, make sure you link to now.js like this\n\n <script src="http://myserver:myport/nowjs/now.js"></script>\n\nYou do not need to host the file /nowjs/now.js. It is automatically hosted by the NowJS using the http server you pass into the .initialize(...) in your server code. If you choose to host now.js yourself, you can, but _do not use the version in github repo* you MUST save the file at http://myserver:myport/nowjs/now.js and host that, because it is automatically configured for your server.\n\nFurther Reading\n---------------\n\nNow that you have NowJS, try the NowJS User Manual and Quick Chat Example \n\nHave more questions? Please contact us:\nEmail: [email protected]\n\nIRC: #nowjs on freenode\n\nTwitter: @NowJSTeam',
36 silly resolved _id: '[email protected]',
36 silly resolved from: 'now' } ]
37 info install [email protected] into C:\Users\user\AppData\Roaming\npm
38 info installOne [email protected]
39 verbose from cache C:\Users\user\AppData\Roaming\npm-cache\now\0.8.1\package\package.json
40 info C:\Users\user\AppData\Roaming\npm\node_modules\now unbuild
41 verbose read json C:\Users\user\AppData\Roaming\npm\node_modules\now\package.json
42 verbose tar unpack C:\Users\user\AppData\Roaming\npm-cache\now\0.8.1\package.tgz
43 silly lockFile e4b54c2a-ata-Roaming-npm-node-modules-now C:\Users\user\AppData\Roaming\npm\node_modules\now
44 verbose lock C:\Users\user\AppData\Roaming\npm\node_modules\now C:\Users\user\AppData\Roaming\npm-cache\e4b54c2a-ata-Roaming-npm-node-modules-now.lock
45 silly gunzTarPerm modes [ '755', '644' ]
46 silly gunzTarPerm extractEntry package.json
47 silly gunzTarPerm modified mode [ 'package.json', 438, 420 ]
48 silly gunzTarPerm extractEntry LICENSE
49 silly gunzTarPerm modified mode [ 'LICENSE', 438, 420 ]
50 silly gunzTarPerm extractEntry examples/express_example/app.js
51 silly gunzTarPerm modified mode [ 'examples/express_example/app.js', 438, 420 ]
52 silly gunzTarPerm extractEntry examples/express_example/views/chat.ejs
53 silly gunzTarPerm modified mode [ 'examples/express_example/views/chat.ejs', 438, 420 ]
54 silly gunzTarPerm extractEntry examples/express_example/views/index.ejs
55 silly gunzTarPerm modified mode [ 'examples/express_example/views/index.ejs', 438, 420 ]
56 silly gunzTarPerm extractEntry examples/express_example/views/layout.ejs
57 silly gunzTarPerm modified mode [ 'examples/express_example/views/layout.ejs', 438, 420 ]
58 silly gunzTarPerm extractEntry examples/helloworld_example/helloworld_server.js
59 silly gunzTarPerm modified mode [ 'examples/helloworld_example/helloworld_server.js', 438, 420 ]
60 silly gunzTarPerm extractEntry examples/helloworld_example/helloworld.html
61 silly gunzTarPerm modified mode [ 'examples/helloworld_example/helloworld.html', 438, 420 ]
62 silly gunzTarPerm extractEntry examples/multiroomchat_example/multiroomchat_server.js
63 silly gunzTarPerm modified mode [ 'examples/multiroomchat_example/multiroomchat_server.js',
63 silly gunzTarPerm 438,
63 silly gunzTarPerm 420 ]
64 silly gunzTarPerm extractEntry examples/multiroomchat_example/multiroomchat.html
65 silly gunzTarPerm modified mode [ 'examples/multiroomchat_example/multiroomchat.html', 438, 420 ]
66 silly gunzTarPerm extractEntry examples/nodeclient_example/chat.js
67 silly gunzTarPerm modified mode [ 'examples/nodeclient_example/chat.js', 438, 420 ]
68 silly gunzTarPerm extractEntry examples/nodeclient_example/server.js
69 silly gunzTarPerm modified mode [ 'examples/nodeclient_example/server.js', 438, 420 ]
70 silly gunzTarPerm extractEntry examples/nodeclient_example/index.html
71 silly gunzTarPerm modified mode [ 'examples/nodeclient_example/index.html', 438, 420 ]
72 silly gunzTarPerm extractEntry dist/now.js
73 silly gunzTarPerm modified mode [ 'dist/now.js', 438, 420 ]
74 silly gunzTarPerm extractEntry doc/jsdoc/files.html
75 silly gunzTarPerm modified mode [ 'doc/jsdoc/files.html', 438, 420 ]
76 silly gunzTarPerm extractEntry doc/jsdoc/index.html
77 silly gunzTarPerm modified mode [ 'doc/jsdoc/index.html', 438, 420 ]
78 silly gunzTarPerm extractEntry doc/jsdoc/symbols/Group#now.html
79 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/Group#now.html', 438, 420 ]
80 silly gunzTarPerm extractEntry doc/jsdoc/symbols/Group.html
81 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/Group.html', 438, 420 ]
82 silly gunzTarPerm extractEntry doc/jsdoc/symbols/nowjs.html
83 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/nowjs.html', 438, 420 ]
84 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/now_lib_fileServer.js.html
85 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/now_lib_fileServer.js.html', 438, 420 ]
86 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/flotype_now_lib_fileServer.js.html
87 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/flotype_now_lib_fileServer.js.html',
87 silly gunzTarPerm 438,
87 silly gunzTarPerm 420 ]
88 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/flotype_now_lib_group.js.html
89 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/flotype_now_lib_group.js.html',
89 silly gunzTarPerm 438,
89 silly gunzTarPerm 420 ]
90 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/flotype_now_lib_handlers.js.html
91 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/flotype_now_lib_handlers.js.html',
91 silly gunzTarPerm 438,
91 silly gunzTarPerm 420 ]
92 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/flotype_now_lib_now.js.html
93 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/flotype_now_lib_now.js.html', 438, 420 ]
94 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/flotype_now_lib_nowUtil.js.html
95 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/flotype_now_lib_nowUtil.js.html',
95 silly gunzTarPerm 438,
95 silly gunzTarPerm 420 ]
96 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/flotype_now_lib_proxy.js.html
97 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/flotype_now_lib_proxy.js.html',
97 silly gunzTarPerm 438,
97 silly gunzTarPerm 420 ]
98 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/flotype_now_lib_scopeTable.js.html
99 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/flotype_now_lib_scopeTable.js.html',
99 silly gunzTarPerm 438,
99 silly gunzTarPerm 420 ]
100 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/flotype_now_lib_server.js.html
101 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/flotype_now_lib_server.js.html',
101 silly gunzTarPerm 438,
101 silly gunzTarPerm 420 ]
102 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/flotype_now_lib_support.js.html
103 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/flotype_now_lib_support.js.html',
103 silly gunzTarPerm 438,
103 silly gunzTarPerm 420 ]
104 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/flotype_now_lib_user.js.html
105 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/flotype_now_lib_user.js.html',
105 silly gunzTarPerm 438,
105 silly gunzTarPerm 420 ]
106 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/flotype_now_lib_function.js.html
107 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/flotype_now_lib_function.js.html',
107 silly gunzTarPerm 438,
107 silly gunzTarPerm 420 ]
108 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/now_lib_function.js.html
109 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/now_lib_function.js.html', 438, 420 ]
110 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/now_lib_group.js.html
111 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/now_lib_group.js.html', 438, 420 ]
112 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/now_lib_handlers.js.html
113 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/now_lib_handlers.js.html', 438, 420 ]
114 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/now_lib_now.js.html
115 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/now_lib_now.js.html', 438, 420 ]
116 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/now_lib_nowUtil.js.html
117 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/now_lib_nowUtil.js.html', 438, 420 ]
118 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/now_lib_proxy.js.html
119 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/now_lib_proxy.js.html', 438, 420 ]
120 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/now_lib_scopeTable.js.html
121 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/now_lib_scopeTable.js.html', 438, 420 ]
122 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/now_lib_server.js.html
123 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/now_lib_server.js.html', 438, 420 ]
124 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/now_lib_support.js.html
125 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/now_lib_support.js.html', 438, 420 ]
126 silly gunzTarPerm extractEntry doc/jsdoc/symbols/src/now_lib_user.js.html
127 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/src/now_lib_user.js.html', 438, 420 ]
128 silly gunzTarPerm extractEntry doc/jsdoc/symbols/User#now.html
129 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/User#now.html', 438, 420 ]
130 silly gunzTarPerm extractEntry doc/jsdoc/symbols/User#user.html
131 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/User#user.html', 438, 420 ]
132 silly gunzTarPerm extractEntry doc/jsdoc/symbols/User.html
133 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/User.html', 438, 420 ]
134 silly gunzTarPerm extractEntry doc/jsdoc/symbols/global.html
135 silly gunzTarPerm modified mode [ 'doc/jsdoc/symbols/global.html', 438, 420 ]
136 silly gunzTarPerm extractEntry doc/public/best_practices.md
137 silly gunzTarPerm modified mode [ 'doc/public/best_practices.md', 438, 420 ]
138 silly gunzTarPerm extractEntry doc/public/company.md
139 silly gunzTarPerm modified mode [ 'doc/public/company.md', 438, 420 ]
140 silly gunzTarPerm extractEntry doc/public/getting_started.md
141 silly gunzTarPerm modified mode [ 'doc/public/getting_started.md', 438, 420 ]
142 silly gunzTarPerm extractEntry doc/public/jobs.md
143 silly gunzTarPerm modified mode [ 'doc/public/jobs.md', 438, 420 ]
144 silly gunzTarPerm extractEntry doc/public/user_manual.md
145 silly gunzTarPerm modified mode [ 'doc/public/user_manual.md', 438, 420 ]
146 silly gunzTarPerm extractEntry bin/build.js
147 silly gunzTarPerm modified mode [ 'bin/build.js', 438, 420 ]
148 silly gunzTarPerm extractEntry bin/proxy.node
149 silly gunzTarPerm modified mode [ 'bin/proxy.node', 438, 420 ]
150 silly gunzTarPerm extractEntry lib/user.js
151 silly gunzTarPerm modified mode [ 'lib/user.js', 438, 420 ]
152 silly gunzTarPerm extractEntry lib/function.js
153 silly gunzTarPerm modified mode [ 'lib/function.js', 438, 420 ]
154 silly gunzTarPerm extractEntry lib/group.js
155 silly gunzTarPerm modified mode [ 'lib/group.js', 438, 420 ]
156 silly gunzTarPerm extractEntry lib/handlers.js
157 silly gunzTarPerm modified mode [ 'lib/handlers.js', 438, 420 ]
158 silly gunzTarPerm extractEntry lib/support.js
159 silly gunzTarPerm modified mode [ 'lib/support.js', 438, 420 ]
160 silly gunzTarPerm extractEntry lib/fileServer.js
161 silly gunzTarPerm modified mode [ 'lib/fileServer.js', 438, 420 ]
162 silly gunzTarPerm extractEntry lib/nowUtil.js
163 silly gunzTarPerm modified mode [ 'lib/nowUtil.js', 438, 420 ]
164 silly gunzTarPerm extractEntry lib/proxy.js
165 silly gunzTarPerm modified mode [ 'lib/proxy.js', 438, 420 ]
166 silly gunzTarPerm extractEntry lib/scopeTable.js
167 silly gunzTarPerm modified mode [ 'lib/scopeTable.js', 438, 420 ]
168 silly gunzTarPerm extractEntry lib/server.js
169 silly gunzTarPerm modified mode [ 'lib/server.js', 438, 420 ]
170 silly gunzTarPerm extractEntry lib/now.js
171 silly gunzTarPerm modified mode [ 'lib/now.js', 438, 420 ]
172 silly gunzTarPerm extractEntry lib/nodeclient/now.js
173 silly gunzTarPerm modified mode [ 'lib/nodeclient/now.js', 438, 420 ]
174 silly gunzTarPerm extractEntry lib/client/now.js
175 silly gunzTarPerm modified mode [ 'lib/client/now.js', 438, 420 ]
176 silly gunzTarPerm extractEntry .gitmodules
177 silly gunzTarPerm modified mode [ '.gitmodules', 438, 420 ]
178 silly gunzTarPerm extractEntry Makefile
179 silly gunzTarPerm modified mode [ 'Makefile', 438, 420 ]
180 silly gunzTarPerm extractEntry changelog.md
181 silly gunzTarPerm modified mode [ 'changelog.md', 438, 420 ]
182 silly gunzTarPerm extractEntry readme.md
183 silly gunzTarPerm modified mode [ 'readme.md', 438, 420 ]
184 verbose read json C:\Users\user\AppData\Roaming\npm\node_modules\now\package.json
185 silly lockFile e4b54c2a-ata-Roaming-npm-node-modules-now C:\Users\user\AppData\Roaming\npm\node_modules\now
186 info preinstall [email protected]
187 verbose from cache C:\Users\user\AppData\Roaming\npm\node_modules\now\package.json
188 verbose readDependencies using package.json deps
189 verbose from cache C:\Users\user\AppData\Roaming\npm\node_modules\now\package.json
190 verbose readDependencies using package.json deps
191 verbose cache add [ 'socket.io@>= 0.8.7', null ]
192 silly cache add name=undefined spec="socket.io@>= 0.8.7" args=["socket.io@>= 0.8.7",null]
193 verbose parsed url { pathname: 'socket.io@%3E=%200.8.7',
193 verbose parsed url path: 'socket.io@%3E=%200.8.7',
193 verbose parsed url href: 'socket.io@%3E=%200.8.7' }
194 silly cache add name="socket.io" spec=">= 0.8.7" args=["socket.io",">= 0.8.7"]
195 verbose parsed url { pathname: '%3E=%200.8.7',
195 verbose parsed url path: '%3E=%200.8.7',
195 verbose parsed url href: '%3E=%200.8.7' }
196 verbose addNamed [ 'socket.io', '>= 0.8.7' ]
197 verbose addNamed [ null, '>=0.8.7' ]
198 silly lockFile a92e7cf4-socket-io-0-8-7 socket.io@>= 0.8.7
199 verbose lock socket.io@>= 0.8.7 C:\Users\user\AppData\Roaming\npm-cache\a92e7cf4-socket-io-0-8-7.lock
200 verbose cache add [ 'node-proxy@>= 0.4.0', null ]
201 silly cache add name=undefined spec="node-proxy@>= 0.4.0" args=["node-proxy@>= 0.4.0",null]
202 verbose parsed url { pathname: 'node-proxy@%3E=%200.4.0',
202 verbose parsed url path: 'node-proxy@%3E=%200.4.0',
202 verbose parsed url href: 'node-proxy@%3E=%200.4.0' }
203 silly cache add name="node-proxy" spec=">= 0.4.0" args=["node-proxy",">= 0.4.0"]
204 verbose parsed url { pathname: '%3E=%200.4.0',
204 verbose parsed url path: '%3E=%200.4.0',
204 verbose parsed url href: '%3E=%200.4.0' }
205 verbose addNamed [ 'node-proxy', '>= 0.4.0' ]
206 verbose addNamed [ null, '>=0.4.0' ]
207 silly lockFile 592bcf82-node-proxy-0-4-0 node-proxy@>= 0.4.0
208 verbose lock node-proxy@>= 0.4.0 C:\Users\user\AppData\Roaming\npm-cache\592bcf82-node-proxy-0-4-0.lock
209 silly addNameRange { name: 'socket.io', range: '>=0.8.7', hasData: false }
210 silly addNameRange { name: 'node-proxy', range: '>=0.4.0', hasData: false }
211 verbose url raw node-proxy
212 verbose url resolving [ 'https://registry.npmjs.org/', './node-proxy' ]
213 verbose url resolved https://registry.npmjs.org/node-proxy
214 info trying registry request attempt 1 at 16:45:02
215 verbose etag "96MNE6GHEF4Y05AQ9KQIFITY"
216 http GET https://registry.npmjs.org/node-proxy
217 verbose url raw socket.io
218 verbose url resolving [ 'https://registry.npmjs.org/', './socket.io' ]
219 verbose url resolved https://registry.npmjs.org/socket.io
220 info trying registry request attempt 1 at 16:45:02
221 verbose etag "E6GKDZF2F5QT9AA4OYVR4QTAO"
222 http GET https://registry.npmjs.org/socket.io
223 http 304 https://registry.npmjs.org/socket.io
224 silly registry.get cb [ 304,
224 silly registry.get { server: 'CouchDB/1.2.0 (Erlang OTP/R15B)',
224 silly registry.get etag: '"E6GKDZF2F5QT9AA4OYVR4QTAO"',
224 silly registry.get date: 'Wed, 12 Sep 2012 11:15:06 GMT',
224 silly registry.get 'content-length': '0' } ]
225 verbose etag socket.io from cache
226 silly addNameRange number 2 { name: 'socket.io', range: '>=0.8.7', hasData: true }
227 silly addNameRange versions [ 'socket.io',
227 silly addNameRange [ '0.3.8',
227 silly addNameRange '0.4.0',
227 silly addNameRange '0.4.1',
227 silly addNameRange '0.5.1',
227 silly addNameRange '0.5.3',
227 silly addNameRange '0.6.0',
227 silly addNameRange '0.6.1',
227 silly addNameRange '0.6.3',
227 silly addNameRange '0.6.4',
227 silly addNameRange '0.6.5',
227 silly addNameRange '0.6.6',
227 silly addNameRange '0.6.7',
227 silly addNameRange '0.6.8',
227 silly addNameRange '0.6.9',
227 silly addNameRange '0.6.10',
227 silly addNameRange '0.6.11',
227 silly addNameRange '0.6.12',
227 silly addNameRange '0.6.14',
227 silly addNameRange '0.6.15',
227 silly addNameRange '0.6.16',
227 silly addNameRange '0.6.17',
227 silly addNameRange '0.6.18',
227 silly addNameRange '0.7.0',
227 silly addNameRange '0.7.1',
227 silly addNameRange '0.7.2',
227 silly addNameRange '0.7.3',
227 silly addNameRange '0.7.4',
227 silly addNameRange '0.7.5',
227 silly addNameRange '0.7.6',
227 silly addNameRange '0.7.7',
227 silly addNameRange '0.7.8',
227 silly addNameRange '0.7.9',
227 silly addNameRange '0.7.10',
227 silly addNameRange '0.7.11',
227 silly addNameRange '0.8.0',
227 silly addNameRange '0.8.1',
227 silly addNameRange '0.8.2',
227 silly addNameRange '0.8.3',
227 silly addNameRange '0.8.4',
227 silly addNameRange '0.8.5',
227 silly addNameRange '0.8.6',
227 silly addNameRange '0.8.7',
227 silly addNameRange '0.9.0',
227 silly addNameRange '0.9.1',
227 silly addNameRange '0.9.1-1',
227 silly addNameRange '0.9.2',
227 silly addNameRange '0.9.3',
227 silly addNameRange '0.9.4',
227 silly addNameRange '0.9.5',
227 silly addNameRange '0.9.6',
227 silly addNameRange '0.9.7',
227 silly addNameRange '0.9.8',
227 silly addNameRange '0.9.9',
227 silly addNameRange '0.9.10' ] ]
228 verbose addNamed [ 'socket.io', '0.9.10' ]
229 verbose addNamed [ '0.9.10', '0.9.10' ]
230 silly lockFile 5127d080-socket-io-0-9-10 [email protected]
231 verbose lock [email protected] C:\Users\user\AppData\Roaming\npm-cache\5127d080-socket-io-0-9-10.lock
232 verbose read json C:\Users\user\AppData\Roaming\npm-cache\socket.io\0.9.10\package\package.json
233 silly lockFile 5127d080-socket-io-0-9-10 [email protected]
234 silly lockFile a92e7cf4-socket-io-0-8-7 socket.io@>= 0.8.7
235 http 304 https://registry.npmjs.org/node-proxy
236 silly registry.get cb [ 304,
236 silly registry.get { server: 'CouchDB/1.2.0 (Erlang OTP/R15B)',
236 silly registry.get etag: '"96MNE6GHEF4Y05AQ9KQIFITY"',
236 silly registry.get date: 'Wed, 12 Sep 2012 11:15:09 GMT',
236 silly registry.get 'content-length': '0' } ]
237 verbose etag node-proxy from cache
238 silly addNameRange number 2 { name: 'node-proxy', range: '>=0.4.0', hasData: true }
239 silly addNameRange versions [ 'node-proxy',
239 silly addNameRange [ '0.3.1', '0.3.2', '0.4.0', '0.5.0', '0.5.1', '0.5.2', '0.6.0' ] ]
240 verbose addNamed [ 'node-proxy', '0.6.0' ]
241 verbose addNamed [ '0.6.0', '0.6.0' ]
242 silly lockFile 4095cacd-node-proxy-0-6-0 [email protected]
243 verbose lock [email protected] C:\Users\user\AppData\Roaming\npm-cache\4095cacd-node-proxy-0-6-0.lock
244 verbose read json C:\Users\user\AppData\Roaming\npm-cache\node-proxy\0.6.0\package\package.json
245 silly lockFile 4095cacd-node-proxy-0-6-0 [email protected]
246 silly lockFile 592bcf82-node-proxy-0-4-0 node-proxy@>= 0.4.0
247 silly resolved [ { name: 'socket.io',
247 silly resolved version: '0.9.10',
247 silly resolved description: 'Real-time apps made cross-browser & easy with a WebSocket-like API',
247 silly resolved homepage: 'http://socket.io',
247 silly resolved keywords: [ 'websocket', 'socket', 'realtime', 'socket.io', 'comet', 'ajax' ],
247 silly resolved author: { name: 'Guillermo Rauch', email: '[email protected]' },
247 silly resolved contributors: [ [Object], [Object], [Object], [Object] ],
247 silly resolved repository:
247 silly resolved { type: 'git',
247 silly resolved url: 'https://github.com/LearnBoost/socket.io.git' },
247 silly resolved dependencies:
247 silly resolved { 'socket.io-client': '0.9.10',
247 silly resolved policyfile: '0.0.4',
247 silly resolved redis: '0.7.2' },
247 silly resolved devDependencies:
247 silly resolved { expresso: '0.9.2',
247 silly resolved should: '',
247 silly resolved benchmark: '0.2.2',
247 silly resolved microtime: '0.1.3-1',
247 silly resolved colors: '0.5.1' },
247 silly resolved main: 'index',
247 silly resolved engines: { node: '>= 0.4.0' },
247 silly resolved scripts: { test: 'make test' },
247 silly resolved readme: '# Socket.IO\n\nSocket.IO is a Node.JS project that makes WebSockets and realtime possible in\nall browsers. It also enhances WebSockets by providing built-in multiplexing,\nhorizontal scalability, automatic JSON encoding/decoding, and more.\n\n## How to Install\n\nbash\nnpm install socket.io\n\n\n## How to use\n\nFirst, require socket.io:\n\njs\nvar io = require(\'socket.io\');\n\n\nNext, attach it to a HTTP/HTTPS server. If you're using the fantastic express\nweb framework:\n\n#### Express 3.x\n\n

js\nvar app = express()\n  , server = require(\'http\').createServer(app)\n  , io = io.listen(server);\n\nserver.listen(80);\n\nio.sockets.on(\'connection\', function (socket) {\n  socket.emit(\'news\', { hello: \'world\' });\n  socket.on(\'my other event\', function (data) {\n    console.log(data);\n  });\n});\n

\n\n#### Express 2.x\n\n

js\nvar app = express.createServer()\n  , io = io.listen(app);\n\napp.listen(80);\n\nio.sockets.on(\'connection\', function (socket) {\n  socket.emit(\'news\', { hello: \'world\' });\n  socket.on(\'my other event\', function (data) {\n    console.log(data);\n  });\n});\n

\n\nFinally, load it from the client side code:\n\n

html\n<script src="/socket.io/socket.io.js"></script>\n<script>\n  var socket = io.connect(\'http://localhost\');\n  socket.on(\'news\', function (data) {\n    console.log(data);\n    socket.emit(\'my other event\', { my: \'data\' });\n  });\n</script>\n

\n\nFor more thorough examples, look at the examples/ directory.\n\n## Short recipes\n\n### Sending and receiving events.\n\nSocket.IO allows you to emit and receive custom events.\nBesides connect, message and disconnect, you can emit custom events:\n\n

js\n// note, io.listen(<port>) will create a http server for you\nvar io = require(\'socket.io\').listen(80);\n\nio.sockets.on(\'connection\', function (socket) {\n  io.sockets.emit(\'this\', { will: \'be received by everyone\' });\n\n  socket.on(\'private message\', function (from, msg) {\n    console.log(\'I received a private message by \', from, \' saying \', msg);\n  });\n\n  socket.on(\'disconnect\', function () {\n    io.sockets.emit(\'user disconnected\');\n  });\n});\n

\n\n### Storing data associated to a client\n\nSometimes it's necessary to store data associated with a client that's\nnecessary for the duration of the session.\n\n#### Server side\n\n

js\nvar io = require(\'socket.io\').listen(80);\n\nio.sockets.on(\'connection\', function (socket) {\n  socket.on(\'set nickname\', function (name) {\n    socket.set(\'nickname\', name, function () { socket.emit(\'ready\'); });\n  });\n\n  socket.on(\'msg\', function () {\n    socket.get(\'nickname\', function (err, name) {\n      console.log(\'Chat message by \', name);\n    });\n  });\n});\n

\n\n#### Client side\n\n

html\n<script>\n  var socket = io.connect(\'http://localhost\');\n\n  socket.on(\'connect\', function () {\n    socket.emit(\'set nickname\', prompt(\'What is your nickname?\'));\n    socket.on(\'ready\', function () {\n      console.log(\'Connected !\');\n      socket.emit(\'msg\', prompt(\'What is your message?\'));\n    });\n  });\n</script>\n

\n\n### Restricting yourself to a namespace\n\nIf you have control over all the messages and events emitted for a particular\napplication, using the default / namespace works.\n\nIf you want to leverage 3rd-party code, or produce code to share with others,\nsocket.io provides a way of namespacing a socket.\n\nThis has the benefit of multiplexing a single connection. Instead of\nsocket.io using two WebSocket connections, it'll use one.\n\nThe following example defines a socket that listens on '/chat' and one for\n'/news':\n\n#### Server side\n\n

js\nvar io = require(\'socket.io\').listen(80);\n\nvar chat = io\n  .of(\'/chat\')\n  .on(\'connection\', function (socket) {\n    socket.emit(\'a message\', { that: \'only\', \'/chat\': \'will get\' });\n    chat.emit(\'a message\', { everyone: \'in\', \'/chat\': \'will get\' });\n  });\n\nvar news = io\n  .of(\'/news\');\n  .on(\'connection\', function (socket) {\n    socket.emit(\'item\', { news: \'item\' });\n  });\n

\n\n#### Client side:\n\n

html\n<script>\n  var chat = io.connect(\'http://localhost/chat\')\n    , news = io.connect(\'http://localhost/news\');\n\n  chat.on(\'connect\', function () {\n    chat.emit(\'hi!\');\n  });\n\n  news.on(\'news\', function () {\n    news.emit(\'woot\');\n  });\n</script>\n

\n\n### Sending volatile messages.\n\nSometimes certain messages can be dropped. Let's say you have an app that\nshows realtime tweets for the keyword bieber. \n\nIf a certain client is not ready to receive messages (because of network slowness\nor other issues, or because he's connected through long polling and is in the\nmiddle of a request-response cycle), if he doesn't receive ALL the tweets related\nto bieber your application won't suffer.\n\nIn that case, you might want to send those messages as volatile messages.\n\n#### Server side\n\n

js\nvar io = require(\'socket.io\').listen(80);\n\nio.sockets.on(\'connection\', function (socket) {\n  var tweets = setInterval(function () {\n    getBieberTweet(function (tweet) {\n      socket.volatile.emit(\'bieber tweet\', tweet);\n    });\n  }, 100);\n\n  socket.on(\'disconnect\', function () {\n    clearInterval(tweets);\n  });\n});\n

\n\n#### Client side\n\nIn the client side, messages are received the same way whether they're volatile\nor not.\n\n### Getting acknowledgements\n\nSometimes, you might want to get a callback when the client confirmed the message\nreception.\n\nTo do this, simply pass a function as the last parameter of .send or .emit.\nWhat's more, when you use .emit, the acknowledgement is done by you, which\nmeans you can also pass data along:\n\n#### Server side\n\n

js\nvar io = require(\'socket.io\').listen(80);\n\nio.sockets.on(\'connection\', function (socket) {\n  socket.on(\'ferret\', function (name, fn) {\n    fn(\'woot\');\n  });\n});\n

\n\n#### Client side\n\n

html\n<script>\n  var socket = io.connect(); // TIP: .connect with no args does auto-discovery\n  socket.on(\'connect\', function () { // TIP: you can avoid listening on

connect

 and listen on events directly too!\n    socket.emit(\'ferret\', \'tobi\', function (data) {\n      console.log(data); // data will be \'woot\'\n    });\n  });\n</script>\n

\n\n### Broadcasting messages\n\nTo broadcast, simply add a broadcast flag to emit and send method calls.\nBroadcasting means sending a message to everyone else except for the socket\nthat starts it.\n\n#### Server side\n\n

js\nvar io = require(\'socket.io\').listen(80);\n\nio.sockets.on(\'connection\', function (socket) {\n  socket.broadcast.emit(\'user connected\');\n  socket.broadcast.json.send({ a: \'message\' });\n});\n

\n\n### Rooms\n\nSometimes you want to put certain sockets in the same room, so that it's easy\nto broadcast to all of them together.\n\nThink of this as built-in channels for sockets. Sockets join and leave\nrooms in each socket.\n\n#### Server side\n\n

js\nvar io = require(\'socket.io\').listen(80);\n\nio.sockets.on(\'connection\', function (socket) {\n  socket.join(\'justin bieber fans\');\n  socket.broadcast.to(\'justin bieber fans\').emit(\'new fan\');\n  io.sockets.in(\'rammstein fans\').emit(\'new non-fan\');\n});\n

\n\n### Using it just as a cross-browser WebSocket\n\nIf you just want the WebSocket semantics, you can do that too.\nSimply leverage send and listen on the message event:\n\n#### Server side\n\n

js\nvar io = require(\'socket.io\').listen(80);\n\nio.sockets.on(\'connection\', function (socket) {\n  socket.on(\'message\', function () { });\n  socket.on(\'disconnect\', function () { });\n});\n

\n\n#### Client side\n\n

html\n<script>\n  var socket = io.connect(\'http://localhost/\');\n  socket.on(\'connect\', function () {\n    socket.send(\'hi\');\n\n    socket.on(\'message\', function (msg) {\n      // my msg\n    });\n  });\n</script>\n

\n\n### Changing configuration\n\nConfiguration in socket.io is TJ-style:\n\n#### Server side\n\n

js\nvar io = require(\'socket.io\').listen(80);\n\nio.configure(function () {\n  io.set(\'transports\', [\'websocket\', \'flashsocket\', \'xhr-polling\']);\n});\n\nio.configure(\'development\', function () {\n  io.set(\'transports\', [\'websocket\', \'xhr-polling\']);\n  io.enable(\'log\');\n});\n

\n\n## License \n\n(The MIT License)\n\nCopyright (c) 2011 Guillermo Rauch <[email protected]>\n\nPermission is hereby granted, free of charge, to any person obtaining\na copy of this software and associated documentation files (the\n'Software'), to deal in the Software without restriction, including\nwithout limitation the rights to use, copy, modify, merge, publish,\ndistribute, sublicense, and/or sell copies of the Software, and to\npermit persons to whom the Software is furnished to do so, subject to\nthe following conditions:\n\nThe above copyright notice and this permission notice shall be\nincluded in all copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,\nEXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF\nMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.\nIN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY\nCLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,\nTORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE\nSOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.\n',
247 silly resolved _id: '[email protected]',
247 silly resolved from: 'socket.io@>= 0.8.7' },
247 silly resolved { name: 'node-proxy',
247 silly resolved version: '0.6.0',
247 silly resolved description: 'A module for node implementing noSuchMethod-type handlers, such as object overloading, as part of the Harmony Catch-All Proxies specification found at http://wiki.ecmascript.org/doku.php?id=harmony:proxies',
247 silly resolved keywords: [ 'interceptor', 'proxy', 'overload', 'noSuchMethod' ],
247 silly resolved contributors: [ [Object], [Object], [Object] ],
247 silly resolved licenses: [ [Object] ],
247 silly resolved bugs: { url: 'http://github.com/samshull/node-proxy/issues' },
247 silly resolved implements: [ 'http://wiki.ecmascript.org/doku.php?id=harmony:proxies' ],
247 silly resolved engines: { node: '>=0.6', npm: '>= 1.1.17' },
247 silly resolved repositories: [ [Object] ],
247 silly resolved main: './lib/node-proxy.js',
247 silly resolved scripts:
247 silly resolved { install: 'node-gyp configure build',
247 silly resolved test: 'node test/test.js' },
247 silly resolved readme: 'node-proxy is an implementation of Harmony Proxies http://wiki.ecmascript.org/doku.php?id=harmony:proxies\nthat allows the developer to create "catch-all" property handlers for an object or a function in node.js.\n\nAuthor: Sam Shull \nRepository: http://github.com/samshull/node-proxy \nIssues: http://github.com/samshull/node-proxy/issues \n\n** This does not work appropriately in node versions 0.1.100 - 0.1.102. You will need to install node_version.h in $PREFIX/include/node\n\nMethods:\n\nObject create(ProxyHandler handler [, Object proto ] ) throws Error, TypeError\n\nFunction createFunction(ProxyHandler handler, Function callTrap [, Function constructTrap ] ) throws Error, TypeError\n\nBoolean isTrapping(Object obj) throws Error\n\n\nAdditional Methods (for ECMAScript 5 compatibliity): @see http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-262.pdf\n\nBoolean freeze(Object obj) throws Error, TypeError\n\nBoolean seal(Object obj) throws Error, TypeError\n\nBoolean preventExtensions(Object obj) throws Error, TypeError\n\nBoolean isFrozen(Object obj) throws Error, TypeError\n\nBoolean isSealed(Object obj) throws Error, TypeError\n\nBoolean isExtensible(Object obj) throws Error, TypeError\n\nPropertyDescriptor getOwnPropertyDescriptor(Object obj, String name) throws Error, TypeError\n\nBoolean defineProperty(Object obj, String name, PropertyDescriptor pd) throws Error, TypeError\n\nBoolean defineProperties(Object obj, Object descriptors) throws Error, TypeError\n\n\nMore methods:\n\nObject hidden(Object obj, String name [, Object value ] ) throws Error\n- Set or retrieve a hidden property on an Object\n\nObject clone(Object obj) throws Error\n- Create a shallow copy of an Object\n\nBoolean isProxy(Object obj)\n- determine if an object was created by Proxy\n\nBoolean setPrototype(Object obj, Object obj) throws Error\n-set the prototype of a given object to the second given object\n',
247 silly resolved _id: '[email protected]',
247 silly resolved _from: 'node-proxy@>= 0.4.0' } ]
248 info install [email protected] into C:\Users\user\AppData\Roaming\npm\node_modules\now
249 info install [email protected] into C:\Users\user\AppData\Roaming\npm\node_modules\now
250 info installOne [email protected]
251 info installOne [email protected]
252 verbose from cache C:\Users\user\AppData\Roaming\npm-cache\socket.io\0.9.10\package\package.json
253 info C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\socket.io unbuild
254 verbose read json C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\socket.io\package.json
255 verbose from cache C:\Users\user\AppData\Roaming\npm-cache\node-proxy\0.6.0\package\package.json
256 info C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\node-proxy unbuild
257 verbose read json C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\node-proxy\package.json
258 verbose tar unpack C:\Users\user\AppData\Roaming\npm-cache\socket.io\0.9.10\package.tgz
259 silly lockFile 8836df5b-dules-now-node-modules-socket-io C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\socket.io
260 verbose lock C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\socket.io C:\Users\user\AppData\Roaming\npm-cache\8836df5b-dules-now-node-modules-socket-io.lock
261 verbose tar unpack C:\Users\user\AppData\Roaming\npm-cache\node-proxy\0.6.0\package.tgz
262 silly lockFile 559c9f65-ules-now-node-modules-node-proxy C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\node-proxy
263 verbose lock C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\node-proxy C:\Users\user\AppData\Roaming\npm-cache\559c9f65-ules-now-node-modules-node-proxy.lock
264 silly gunzTarPerm modes [ '755', '644' ]
265 silly gunzTarPerm modes [ '755', '644' ]
266 silly gunzTarPerm extractEntry package.json
267 silly gunzTarPerm modified mode [ 'package.json', 438, 420 ]
268 silly gunzTarPerm extractEntry package.json
269 silly gunzTarPerm modified mode [ 'package.json', 438, 420 ]
270 silly gunzTarPerm extractEntry .npmignore
271 silly gunzTarPerm modified mode [ '.npmignore', 438, 420 ]
272 silly gunzTarPerm extractEntry LICENSE
273 silly gunzTarPerm modified mode [ 'LICENSE', 438, 420 ]
274 silly gunzTarPerm extractEntry index.js
275 silly gunzTarPerm modified mode [ 'index.js', 438, 420 ]
276 silly gunzTarPerm extractEntry .npmignore
277 silly gunzTarPerm modified mode [ '.npmignore', 438, 420 ]
278 silly gunzTarPerm extractEntry README.md
279 silly gunzTarPerm modified mode [ 'README.md', 438, 420 ]
280 silly gunzTarPerm extractEntry binding.gyp
281 silly gunzTarPerm modified mode [ 'binding.gyp', 438, 420 ]
282 silly gunzTarPerm extractEntry .travis.yml
283 silly gunzTarPerm modified mode [ '.travis.yml', 438, 420 ]
284 silly gunzTarPerm extractEntry benchmarks/decode.bench.js
285 silly gunzTarPerm modified mode [ 'benchmarks/decode.bench.js', 438, 420 ]
286 silly gunzTarPerm extractEntry examples/autoload-namespace/autoload-namespace.js
287 silly gunzTarPerm modified mode [ 'examples/autoload-namespace/autoload-namespace.js', 438, 420 ]
288 silly gunzTarPerm extractEntry examples/autoload-namespace/autoload-test.js
289 silly gunzTarPerm modified mode [ 'examples/autoload-namespace/autoload-test.js', 438, 420 ]
290 silly gunzTarPerm extractEntry benchmarks/encode.bench.js
291 silly gunzTarPerm modified mode [ 'benchmarks/encode.bench.js', 438, 420 ]
292 silly gunzTarPerm extractEntry benchmarks/runner.js
293 silly gunzTarPerm modified mode [ 'benchmarks/runner.js', 438, 420 ]
294 silly gunzTarPerm extractEntry History.md
295 silly gunzTarPerm modified mode [ 'History.md', 438, 420 ]
296 silly gunzTarPerm extractEntry examples/autoload-namespace/org/w3c/DOM/Document.js
297 silly gunzTarPerm modified mode [ 'examples/autoload-namespace/org/w3c/DOM/Document.js',
297 silly gunzTarPerm 438,
297 silly gunzTarPerm 420 ]
298 silly gunzTarPerm extractEntry examples/autoload-namespace/org/w3c/DOM/Document/String/Test.js
299 silly gunzTarPerm modified mode [ 'examples/autoload-namespace/org/w3c/DOM/Document/String/Test.js',
299 silly gunzTarPerm 438,
299 silly gunzTarPerm 420 ]
300 silly gunzTarPerm extractEntry lib/node-proxy.js
301 silly gunzTarPerm modified mode [ 'lib/node-proxy.js', 438, 420 ]
302 silly gunzTarPerm extractEntry LICENSE.txt
303 silly gunzTarPerm modified mode [ 'LICENSE.txt', 438, 420 ]
304 silly gunzTarPerm extractEntry lib/client.js
305 silly gunzTarPerm modified mode [ 'lib/client.js', 438, 420 ]
306 silly gunzTarPerm extractEntry lib/manager.js
307 silly gunzTarPerm modified mode [ 'lib/manager.js', 438, 420 ]
308 silly gunzTarPerm extractEntry src/node-proxy.cc
309 silly gunzTarPerm modified mode [ 'src/node-proxy.cc', 438, 420 ]
310 silly gunzTarPerm extractEntry src/node-proxy.h
311 silly gunzTarPerm modified mode [ 'src/node-proxy.h', 438, 420 ]
312 silly gunzTarPerm extractEntry lib/namespace.js
313 silly gunzTarPerm modified mode [ 'lib/namespace.js', 438, 420 ]
314 silly gunzTarPerm extractEntry lib/parser.js
315 silly gunzTarPerm modified mode [ 'lib/parser.js', 438, 420 ]
316 silly gunzTarPerm extractEntry test/test.js
317 silly gunzTarPerm modified mode [ 'test/test.js', 438, 420 ]
318 silly gunzTarPerm extractEntry lib/socket.io.js
319 silly gunzTarPerm modified mode [ 'lib/socket.io.js', 438, 420 ]
320 silly gunzTarPerm extractEntry lib/logger.js
321 silly gunzTarPerm modified mode [ 'lib/logger.js', 438, 420 ]
322 silly gunzTarPerm extractEntry lib/static.js
323 silly gunzTarPerm modified mode [ 'lib/static.js', 438, 420 ]
324 silly gunzTarPerm extractEntry lib/store.js
325 silly gunzTarPerm modified mode [ 'lib/store.js', 438, 420 ]
326 silly gunzTarPerm extractEntry lib/transport.js
327 silly gunzTarPerm modified mode [ 'lib/transport.js', 438, 420 ]
328 silly gunzTarPerm extractEntry lib/util.js
329 silly gunzTarPerm modified mode [ 'lib/util.js', 438, 420 ]
330 silly gunzTarPerm extractEntry lib/socket.js
331 silly gunzTarPerm modified mode [ 'lib/socket.js', 438, 420 ]
332 silly gunzTarPerm extractEntry lib/stores/memory.js
333 silly gunzTarPerm modified mode [ 'lib/stores/memory.js', 438, 420 ]
334 silly gunzTarPerm extractEntry lib/stores/redis.js
335 silly gunzTarPerm modified mode [ 'lib/stores/redis.js', 438, 420 ]
336 silly gunzTarPerm extractEntry lib/transports/flashsocket.js
337 silly gunzTarPerm modified mode [ 'lib/transports/flashsocket.js', 438, 420 ]
338 silly gunzTarPerm extractEntry lib/transports/htmlfile.js
339 silly gunzTarPerm modified mode [ 'lib/transports/htmlfile.js', 438, 420 ]
340 silly gunzTarPerm extractEntry lib/transports/http-polling.js
341 silly gunzTarPerm modified mode [ 'lib/transports/http-polling.js', 438, 420 ]
342 silly gunzTarPerm extractEntry lib/transports/http.js
343 silly gunzTarPerm modified mode [ 'lib/transports/http.js', 438, 420 ]
344 silly gunzTarPerm extractEntry lib/transports/index.js
345 silly gunzTarPerm modified mode [ 'lib/transports/index.js', 438, 420 ]
346 silly gunzTarPerm extractEntry lib/transports/jsonp-polling.js
347 silly gunzTarPerm modified mode [ 'lib/transports/jsonp-polling.js', 438, 420 ]
348 silly gunzTarPerm extractEntry lib/transports/websocket.js
349 silly gunzTarPerm modified mode [ 'lib/transports/websocket.js', 438, 420 ]
350 silly gunzTarPerm extractEntry lib/transports/xhr-polling.js
351 silly gunzTarPerm modified mode [ 'lib/transports/xhr-polling.js', 438, 420 ]
352 silly gunzTarPerm extractEntry lib/transports/websocket/default.js
353 silly gunzTarPerm modified mode [ 'lib/transports/websocket/default.js', 438, 420 ]
354 silly gunzTarPerm extractEntry lib/transports/websocket/hybi-07-12.js
355 silly gunzTarPerm modified mode [ 'lib/transports/websocket/hybi-07-12.js', 438, 420 ]
356 silly gunzTarPerm extractEntry lib/transports/websocket/hybi-16.js
357 silly gunzTarPerm modified mode [ 'lib/transports/websocket/hybi-16.js', 438, 420 ]
358 silly gunzTarPerm extractEntry lib/transports/websocket/index.js
359 silly gunzTarPerm modified mode [ 'lib/transports/websocket/index.js', 438, 420 ]
360 silly gunzTarPerm extractEntry Makefile
361 silly gunzTarPerm modified mode [ 'Makefile', 438, 420 ]
362 silly gunzTarPerm extractEntry Readme.md
363 silly gunzTarPerm modified mode [ 'Readme.md', 438, 420 ]
364 verbose read json C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\node-proxy\package.json
365 silly lockFile 559c9f65-ules-now-node-modules-node-proxy C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\node-proxy
366 info preinstall [email protected]
367 verbose from cache C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\node-proxy\package.json
368 verbose readDependencies using package.json deps
369 verbose from cache C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\node-proxy\package.json
370 verbose readDependencies using package.json deps
371 silly resolved []
372 verbose about to build C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\node-proxy
373 info build C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\node-proxy
374 verbose from cache C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\node-proxy\package.json
375 verbose linkStuff [ true,
375 verbose linkStuff 'C:\Users\user\AppData\Roaming\npm\node_modules',
375 verbose linkStuff false,
375 verbose linkStuff 'C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules' ]
376 info linkStuff [email protected]
377 verbose linkBins [email protected]
378 verbose linkMans [email protected]
379 verbose rebuildBundles [email protected]
380 info install [email protected]
381 verbose unsafe-perm in lifecycle true
382 silly exec cmd "/c" "node-gyp configure build"
383 silly cmd,/c,node-gyp configure build,C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\node-proxy spawning
384 verbose read json C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\socket.io\package.json
385 silly lockFile 8836df5b-dules-now-node-modules-socket-io C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\socket.io
386 info preinstall [email protected]
387 verbose from cache C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\socket.io\package.json
388 verbose readDependencies using package.json deps
389 verbose from cache C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\socket.io\package.json
390 verbose readDependencies using package.json deps
391 verbose cache add [ '[email protected]', null ]
392 silly cache add name=undefined spec="[email protected]" args=["[email protected]",null]
393 verbose parsed url { pathname: '[email protected]',
393 verbose parsed url path: '[email protected]',
393 verbose parsed url href: '[email protected]' }
394 silly cache add name="socket.io-client" spec="0.9.10" args=["socket.io-client","0.9.10"]
395 verbose parsed url { pathname: '0.9.10', path: '0.9.10', href: '0.9.10' }
396 verbose addNamed [ 'socket.io-client', '0.9.10' ]
397 verbose addNamed [ '0.9.10', '0.9.10' ]
398 silly lockFile 147e2402-socket-io-client-0-9-10 [email protected]
399 verbose lock [email protected] C:\Users\user\AppData\Roaming\npm-cache\147e2402-socket-io-client-0-9-10.lock
400 verbose cache add [ '[email protected]', null ]
401 silly cache add name=undefined spec="[email protected]" args=["[email protected]",null]
402 verbose parsed url { pathname: '[email protected]',
402 verbose parsed url path: '[email protected]',
402 verbose parsed url href: '[email protected]' }
403 silly cache add name="policyfile" spec="0.0.4" args=["policyfile","0.0.4"]
404 verbose parsed url { pathname: '0.0.4', path: '0.0.4', href: '0.0.4' }
405 verbose addNamed [ 'policyfile', '0.0.4' ]
406 verbose addNamed [ '0.0.4', '0.0.4' ]
407 silly lockFile 8b99131a-policyfile-0-0-4 [email protected]
408 verbose lock [email protected] C:\Users\user\AppData\Roaming\npm-cache\8b99131a-policyfile-0-0-4.lock
409 verbose cache add [ '[email protected]', null ]
410 silly cache add name=undefined spec="[email protected]" args=["[email protected]",null]
411 verbose parsed url { pathname: '[email protected]',
411 verbose parsed url path: '[email protected]',
411 verbose parsed url href: '[email protected]' }
412 silly cache add name="redis" spec="0.7.2" args=["redis","0.7.2"]
413 verbose parsed url { pathname: '0.7.2', path: '0.7.2', href: '0.7.2' }
414 verbose addNamed [ 'redis', '0.7.2' ]
415 verbose addNamed [ '0.7.2', '0.7.2' ]
416 silly lockFile b62421fe-redis-0-7-2 [email protected]
417 verbose lock [email protected] C:\Users\user\AppData\Roaming\npm-cache\b62421fe-redis-0-7-2.lock
418 verbose url raw socket.io-client/0.9.10
419 verbose url resolving [ 'https://registry.npmjs.org/', './socket.io-client/0.9.10' ]
420 verbose url resolved https://registry.npmjs.org/socket.io-client/0.9.10
421 info trying registry request attempt 1 at 16:45:08
422 verbose etag "DT1FIZVLJNN64WY9GPUQGYRJA"
423 http GET https://registry.npmjs.org/socket.io-client/0.9.10
424 verbose url raw redis/0.7.2
425 verbose url resolving [ 'https://registry.npmjs.org/', './redis/0.7.2' ]
426 verbose url resolved https://registry.npmjs.org/redis/0.7.2
427 info trying registry request attempt 1 at 16:45:08
428 verbose etag "8RDGSWIBIHSFU8YOWHHX2YC9W"
429 http GET https://registry.npmjs.org/redis/0.7.2
430 verbose url raw policyfile/0.0.4
431 verbose url resolving [ 'https://registry.npmjs.org/', './policyfile/0.0.4' ]
432 verbose url resolved https://registry.npmjs.org/policyfile/0.0.4
433 info trying registry request attempt 1 at 16:45:08
434 verbose etag "3G5JE6KEJPXIW1QGIC1YOI4IK"
435 http GET https://registry.npmjs.org/policyfile/0.0.4
436 info [email protected] Failed to exec install script
437 info C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\node-proxy unbuild
438 verbose from cache C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules\node-proxy\package.json
439 info preuninstall [email protected]
440 info uninstall [email protected]
441 verbose false,C:\Users\user\AppData\Roaming\npm\node_modules,C:\Users\user\AppData\Roaming\npm\node_modules\now\node_modules unbuild [email protected]
442 info postuninstall [email protected]
443 verbose about to build C:\Users\user\AppData\Roaming\npm\node_modules\now
444 info C:\Users\user\AppData\Roaming\npm\node_modules\now unbuild
445 verbose from cache C:\Users\user\AppData\Roaming\npm\node_modules\now\package.json
446 info preuninstall [email protected]
447 info uninstall [email protected]
448 verbose true,C:\Users\user\AppData\Roaming\npm\node_modules,C:\Users\user\AppData\Roaming\npm\node_modules unbuild [email protected]
449 info postuninstall [email protected]
450 error [email protected] install: node-gyp configure build
450 error cmd "/c" "node-gyp configure build" failed with 1
451 error Failed at the [email protected] install script.
451 error This is most likely a problem with the node-proxy package,
451 error not with npm itself.
451 error Tell the author that this fails on your system:
451 error node-gyp configure build
451 error You can get their info via:
451 error npm owner ls node-proxy
451 error There is likely additional logging output above.
452 error System Windows_NT 6.1.7600
453 error command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "now" "-g"
454 error cwd C:\projects\helloworld_example
455 error node -v v0.8.9
456 error npm -v 1.1.61
457 error code ELIFECYCLE
458 verbose exit [ 1, true ]

In command prompt, showing not ok code 0.......

It means "now" module is not installed.
Therefore my server file is throwing error in line

var nowjs = require('now');

Could not found "now" module.

My module is installing in default set path as "C:\Users\user\AppData\Roaming\npm\node_modules"
and I am creating helloword_server.js file in "C:\projects\helloworld_example".
In above server file I am requiring "now" module. But not working.

Please help me its very urgent.

npm ERR during fresh install -- probably due to broken npm version

Fresh install on Windows 7 x64 box gets me this:

PS C:\Users\bradw> nodist update
1 file(s) copied.
npm http GET https://registry.npmjs.org/npm
npm http 200 https://registry.npmjs.org/npm
npm http GET https://registry.npmjs.org/npm/-/npm-1.3.8.tgz
npm http 200 https://registry.npmjs.org/npm/-/npm-1.3.8.tgz
npm http GET https://registry.npmjs.org/npm/1.3.8
npm http 200 https://registry.npmjs.org/npm/1.3.8
npm http GET https://registry.npmjs.org/npm/-/npm-1.3.8.tgz
npm http 200 https://registry.npmjs.org/npm/-/npm-1.3.8.tgz
C:\nodist\bin\npm -> C:\nodist\bin\node_modules\npm\bin\npm-cli.js
[email protected] C:\nodist\bin\node_modules\npm
The system cannot find the path specified.
npm http GET https://registry.npmjs.org/npm
npm http 304 https://registry.npmjs.org/npm
npm http GET https://registry.npmjs.org/npm/1.3.8
npm http 304 https://registry.npmjs.org/npm/1.3.8
npm WARN package.json [email protected] No repository field.
C:\nodist\bin\npm -> C:\nodist\bin\node_modules\npm\bin\npm-cli.js
[email protected] C:\nodist\bin\node_modules\npm
1 file(s) moved.
npm http GET https://registry.npmjs.org/request
npm http GET https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/semver
npm http GET https://registry.npmjs.org/rimraf
npm http 200 https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz
npm http 200 https://registry.npmjs.org/rimraf
npm http GET https://registry.npmjs.org/rimraf/-/rimraf-2.2.2.tgz
npm http 200 https://registry.npmjs.org/semver
npm http GET https://registry.npmjs.org/semver/-/semver-2.1.0.tgz
npm http 200 https://registry.npmjs.org/mkdirp/-/mkdirp-0.3.5.tgz
npm http 200 https://registry.npmjs.org/request
npm http GET https://registry.npmjs.org/request/-/request-2.9.203.tgz
npm http 200 https://registry.npmjs.org/rimraf/-/rimraf-2.2.2.tgz
npm ERR! TypeError: Cannot read property 'from' of undefined
npm ERR! at C:\nodist\bin\node_modules\npm\lib\outdated.js:159:36
npm ERR! at C:\nodist\bin\node_modules\npm\lib\cache.js:591:30
npm ERR! at exports.unlock (C:\nodist\bin\node_modules\npm\node_modules\lockfile\lockfile.js:55:41)
npm ERR! at Object.oncomplete (fs.js:297:15)
npm ERR! If you need help, you may report this log at:
npm ERR! http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR! [email protected]

tests!

Write some tests, using vows!

nodemon doesn't work

Nodemon doesn't work with nodist. Neither if it's installed globally nor locally. Error output below:

D:\01_Development\sample>nodemon app.js
16 Aug 16:23:36 - [nodemon] v0.6.23
16 Aug 16:23:36 - [nodemon] watching: D:\01_Development\sample
16 Aug 16:23:36 - [nodemon] starting `node app.js`
CreateProcessW: The system cannot find the file specified.
16 Aug 16:23:36 - [nodemon] app crashed - waiting for file changes before starting...

Chcoclatey update error on nodist-beta

When I run cup all, Chocolatey prints an error message about nodist : "Unable to find package 'nodist-beta'.", and the update fails because of that. Could you please fix it?

nodist bash script for MinGW

There is still a bit of work to be done on this...

THe run command, etc.

Use command doesn't work when used from batch script

Error: No method "resolveToExe" encountered when running nodist use

I'm running on Windows. Most nodist commands work fine, but when I try to use the 'use' command, here is the error I get:

PS c:\code> nodist use 0.8.19
0.8.19

C:\tools\nodist\cli.js:203
      console.log(path.dirname(n.resolveToExe(v)));
                                 ^
TypeError: Object # has no method 'resolveToExe'
    at C:\tools\nodist\cli.js:203:34
    at nodist.install (C:\tools\nodist\lib\nodist.js:176:16)
    at nodist.listAvailable (C:\tools\nodist\lib\nodist.js:99:31)
    at nodist.install (C:\tools\nodist\lib\nodist.js:174:7)
    at nodist.listInstalled (C:\tools\nodist\lib\nodist.js:140:12)
    at ReaddirReq.Req.done (C:\tools\nodist\node_modules\rimraf\node_modules\graceful-fs\graceful-fs.js:142:5)
    at ReaddirReq.done (C:\tools\nodist\node_modules\rimraf\node_modules\graceful-fs\graceful-fs.js:89:22)
    at Object.oncomplete (fs.js:297:15)

how to install NPM modules with Nodist

When trying to install the npm modules with nodist, its not getting installed properly..
is any specific command to run that

Windows error

I have installed nodist since I noticed my node is out of date (0.6.2). So node was already installed. I followed the readme.

The update command ran without problem,

but running nodist stable or nodist dist throws an error in module.js on line 340 where mkdirp cannot be found.

Here is the stack trace .

mkdir on google shows some similar issues.

module.js:340 throw error, when running "nodist dist" or "nodist stable" or what ever

I couldn't run the nodist update with given instructions, but I managed to run it after I added nodist to path also (see bug: 18).

But now if I run anything like: "nodist dist" (or nodist stable) ... it gives me error:

C:\...\node>nodist dist

module.js:340
    throw err;
          ^
Error: Cannot find module 'mkdirp'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:362:17)
    at require (module.js:378:17)
    at Object.<anonymous> (C:\...\node\lib\nodist.js:27:18)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:362:17)

How do I install this thing, so that it works?

"x64" flag to "nodist add" command seems not to work

Windows 7 / 64 bit

Since this is the first time I'm using nodist, I've probably misunderstood something about this usage description (https://github.com/marcelklehr/nodist/blob/master/usage.txt):

nodist add [x64] Download the specified node version.

- - snip - - -

PS C:\tmp> nodist ls
No builds installed, yet.
PS C:\tmp> nodist add 0.10.24 x64
0.10.24
PS C:\tmp> node.exe -p -e "process.arch"
ia32

- - snap - - -

That is, although I asked for the 64 bit version to be installed, what I got was the 32 bit version.

node.cmd file provides unpleasant experience

When you use Ctrl+C to kill a node app, you get prompted with "Terminate batch job (Y/N)?".

The MinGW shell can't run .cmd files.

Looking through history, I see you used to copy the .exe files around but changed to use .cmd files. I think going back to that would solve both of these issues. Or is there a way to use links/junctions?

The system cannot find the batch label specified - end

The error occurs when calling nodist update from within another batchfile (call nodist update) which then results in terminatinating the calling batch file.
It happens because it is not allowed to use GOTO to jump out of a block:
https://github.com/marcelklehr/nodist/blob/master/bin/nodist.cmd#L30

nodist -v fails in PowerShell

I get the following error when running the nodist -v command from PowerShell. Issue appears to be in the bin/nodist.ps1 file added to fix the use command in PowerShell.

C:\nodist\bin\nodist.ps1 : Missing an argument for parameter 'ver'. Specify a parameter of type 'Syste
m.Object' and try again.
At line:1 char:10
+ nodist -v <<<<
    + CategoryInfo          : InvalidArgument: (:) [nodist.ps1], ParameterBindingException
    + FullyQualifiedErrorId : MissingArgument,nodist.ps1

Goto end after :update

otherwise, it'll try to install 'update'...

Fallback to other version adhering to user-provided spec, if the first can't be fetched

$ node --version
v0.10.29

$ nodist 0.8
Couldn't fetch 0.8.27: HTTP 404.
Sorry.

$ node --version
v0.10.29

404 error from the server shouldn't block me from switching the node version. It should fall back to the latest 0.8.x available.

I can work around this using nodist 0.8.26 (which I already have installed before) but nonetheless this, however rare it is, probably should be fixed.

nodist use error

>>nodist 0.11.13
0.11.13

>>nodist 0.10.30
0.10.30

>>nodist ls
> 0.10.30
  0.11.13

>>nodist use v0.11.13
0.11.13
Version spec didn't match any available version.
Sorry.

Cannot find module 'request'

I know the module not found is just from a botched NPM install but the log is confusing me.

Has anyone else ran into this? I have tried both the chocolately package and manual install on Windows 8 x64 and Windows 7 x64 with the same result on both.


C:\Users\JT4\nodist>nodist update
        1 file(s) copied.
npm http GET https://registry.npmjs.org/npm
npm http 401 https://registry.npmjs.org/npm
npm http GET https://registry.npmjs.org/npm
npm http 401 https://registry.npmjs.org/npm
        1 file(s) moved.
npm http GET https://registry.npmjs.org/rimraf
npm http GET https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/semver
npm http GET https://registry.npmjs.org/request
npm http 401 https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/mkdirp
npm http 401 https://registry.npmjs.org/request
npm http 401 https://registry.npmjs.org/rimraf
npm http 401 https://registry.npmjs.org/semver
npm http 401 https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/request/2.9.203
npm http GET https://registry.npmjs.org/semver/2.2.1
npm http GET https://registry.npmjs.org/rimraf/2.2.2
npm http GET https://registry.npmjs.org/mkdirp/0.3.5
npm http 401 https://registry.npmjs.org/mkdirp/0.3.5
npm http 401 https://registry.npmjs.org/request/2.9.203
npm ERR! Error: unauthorized User document conflicts must be resolved before the
 document is used for authentication purposes.: request/2.9.203
npm ERR!     at RegClient.<anonymous> (C:\Users\JT4\nodist\bin\node_modules\npm\
node_modules\npm-registry-client\lib\request.js:259:14)
npm ERR!     at Request.init.self.callback (C:\Users\JT4\nodist\bin\node_modules
\npm\node_modules\request\main.js:120:22)
npm ERR!     at Request.EventEmitter.emit (events.js:91:17)
npm ERR!     at Request.<anonymous> (C:\Users\JT4\nodist\bin\node_modules\npm\no
de_modules\request\main.js:648:16)
npm ERR!     at Request.EventEmitter.emit (events.js:115:20)
npm ERR!     at IncomingMessage.Request.start.self.req.self.httpModule.request.b
uffer (C:\Users\JT4\nodist\bin\node_modules\npm\node_modules\request\main.js:610
:14)
npm ERR!     at IncomingMessage.EventEmitter.emit (events.js:115:20)
npm ERR!     at IncomingMessage._emitEnd (http.js:366:10)
npm ERR!     at HTTPParser.parserOnMessageComplete [as onMessageComplete] (http.
js:149:23)
npm ERR!     at CleartextStream.socketOnData (http.js:1366:20)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <[email protected]>

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Users\\JT4\\nodist\\bin\\\\node.exe" "C:\\Users\\JT4\\nodi
st\\bin\\node_modules\\npm\\cli.js" "update"
npm ERR! cwd C:\Users\JT4\nodist
npm ERR! node -v v0.8.9
npm ERR! npm -v 1.1.68
npm http 401 https://registry.npmjs.org/rimraf/2.2.2
npm http 401 https://registry.npmjs.org/semver/2.2.1
[email protected] node_modules\mkdirp
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     C:\Users\JT4\nodist\npm-debug.log
npm ERR! not ok code 0

module.js:340
    throw err;
          ^
Error: Cannot find module 'request'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:362:17)
    at require (module.js:378:17)
    at Object.<anonymous> (C:\Users\JT4\nodist\lib\nodist.js:28:18)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:362:17)

wrong node version with chocolatey installed nodist

Ok.. this sounds a bit weird...
When I install nodist with git clone and setting Path variable, things seems to work properly.
But when I install nodist with chocolatey, which installs nodist v0.4.6, things get out of hand.
I can see that nodist latest/stable does copy the correct versions into the lib. However, everytime I run node --version, I end up having v0.8.9 (or the version of node that nodist uses internally).
After some investigation, it seems that C:\ProgramData\chocolatey\bin\node.exe that is created after installing nodist actually points to v0.8.9.
Perhaps the chocolatey installation script is buggy?

edit: I tried to replace the node.exe that nodist uses internally with other versions.. and running node --version actually changed as well... So I do think that the C:\ProgramData\chocolatey\bin\node.exe is calling the wrong node.exe file

Also.. cinst nodist -pre fails on the first run most of time.. And a second run should use the file downloaded from the first attempt and continue to install.

--update
Here is a section of the install log from chocolatey:

20140704-23:31:53 [DEBUG] Looking for executables in folder: C:\ProgramData\chocolatey\lib\nodist.0.4.6-beta
Adding batch files for any executables found to a location on PATH. In other words the executable will be available from ANY command line/powershell prompt.
20140704-23:31:53 [DEBUG] Found 3 exe files to possibly generate.
20140704-23:31:53 [DEBUG] Found 'C:\ProgramData\chocolatey\lib\nodist.0.4.6-beta\tools\nodist-master\bin\node.exe' for batch redirect
20140704-23:31:54 [DEBUG] Running 'Generate-BinFile' for node with path:'C:\ProgramData\chocolatey\lib\nodist.0.4.6-beta\tools\nodist-master\bin\node.exe'|$useStart:False|$command:
20140704-23:31:54 [DEBUG] Calling C:\ProgramData\chocolatey\chocolateyinstall\tools\shimgen.exe -o "C:\ProgramData\chocolatey\bin\node.exe" -p "..\lib\nodist.0.4.6-beta\tools\nodist-master\bin\node.exe"
20140704-23:31:54 [CHOCO] Added C:\ProgramData\chocolatey\bin\node.exe shim pointed to '..\lib\nodist.0.4.6-beta\tools\nodist-master\bin\node.exe'.
20140704-23:31:54 [DEBUG] Found 'C:\ProgramData\chocolatey\lib\nodist.0.4.6-beta\tools\nodist-master\v\0.10.29\node.exe' for batch redirect
20140704-23:31:54 [DEBUG] Running 'Generate-BinFile' for node with path:'C:\ProgramData\chocolatey\lib\nodist.0.4.6-beta\tools\nodist-master\v\0.10.29\node.exe'|$useStart:False|$command:
20140704-23:31:54 [DEBUG] Calling C:\ProgramData\chocolatey\chocolateyinstall\tools\shimgen.exe -o "C:\ProgramData\chocolatey\bin\node.exe" -p "..\lib\nodist.0.4.6-beta\tools\nodist-master\v\0.10.29\node.exe"
20140704-23:31:54 [CHOCO] Added C:\ProgramData\chocolatey\bin\node.exe shim pointed to '..\lib\nodist.0.4.6-beta\tools\nodist-master\v\0.10.29\node.exe'.
20140704-23:31:54 [DEBUG] Found 'C:\ProgramData\chocolatey\lib\nodist.0.4.6-beta\tools\nodist-master\node.exe' for batch redirect
20140704-23:31:54 [DEBUG] Running 'Generate-BinFile' for node with path:'C:\ProgramData\chocolatey\lib\nodist.0.4.6-beta\tools\nodist-master\node.exe'|$useStart:False|$command:
20140704-23:31:54 [DEBUG] Calling C:\ProgramData\chocolatey\chocolateyinstall\tools\shimgen.exe -o "C:\ProgramData\chocolatey\bin\node.exe" -p "..\lib\nodist.0.4.6-beta\tools\nodist-master\node.exe"
20140704-23:31:54 [CHOCO] Added C:\ProgramData\chocolatey\bin\node.exe shim pointed to '..\lib\nodist.0.4.6-beta\tools\nodist-master\node.exe'.
20140704-23:31:54 [DEBUG] Evaluating NuGet output for line: 
20140704-23:31:55 [CHOCO] Finished installing 'nodist' and dependencies - if errors not shown in console, none detected. Check log for errors if unsure.

So chocolatey creates the redirects automatically? But points to the wrong node.exe...

-Update:
ok... according to chocolatey wiki, for the .exe files to not be batch redirected, you have to have a file with .ignore suffix. So for each node.exe that is not supposed to be used, there has to be a node.exe.ignore in the same directory. I guess you need a node.exe.ignore next to the one nodist uses internally, and for each version of node fetched, create a node.exe.ignore file alongside it as well.
Hopefully this issue can be fixed soon and pushed onto chocolatey.

Support x64 (automatic detection)

Detect x64 automatically

chocolatey package should use batch file redirects rather than modify the path variable

The chocolatey package could use this improvement, and it will be easier once some work-in-progress in chocolatey are done. Reference: #23

`selfupdate` doesn't work under Git Bash/msysGit

While looking into why nodist selfupdate was not working for me, I discovered that files: nodist\bin\nodist (sh) and nodist\bin\nodist.cmd contain different logic.

For example, if I run nodist selfupdate under Git Bash, rather than a vanilla Windows Command Prompt (CMD.exe), the entire nodist.cmd file is skipped and nodist gets executed immediately. So in this case, selfupdate, gets passed to nodist\cli.js, and it believes I'm trying to set the global Node version to "selfupdate", like you would with "stable" or "latest".

This errors with the message:

Version spec didn't match any available version.
Sorry.

If I write out the spec that's being used (#64):

nodist/lib/versions.js
...
if(!v) return cb(new Error('Version spec, "' + version_spec + '",  didn\'t match any available version'));

...it comes out as

Version spec, "selfupdate",  didn't match any available version.
Sorry.

Could the logic in nodist.cmd be either;

ported into nodist\bin\nodist,
or ported into nodist\cli.js?

I believe this would allow selfupdate to work, as intended, under Git Bash.

Cannot find module 'osenv'; initial install.

I had a previous version of both node and npm on a WinXP box. I uninstalled node but not npm. Not sure if this was the issue. After cloning the repository, adding path and running 'nodist update', I'm getting this error:

module.js:340
    throw err;
          ^
Error: Cannot find module 'osenv'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:362:17)
    at require (module.js:378:17)
    at Object.<anonymous> (C:\BAT\nodist\bin\node_modules\npm\node_modules\npmconf\config-defs.js:10:13)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:362:17)

module.js:340
    throw err;
          ^
Error: Cannot find module 'osenv'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:362:17)
    at require (module.js:378:17)
    at Object.<anonymous> (C:\BAT\nodist\bin\node_modules\npm\node_modules\npmconf\config-defs.js:10:13)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:362:17)

A complete wipe and retry would be fine, but I'm not quite sure if it's necessary or exactly how to go about it. Just delete any 'npm_modules' folders I have? Thanks in advance for any help.

EDIT:
This is a non-issue. Complete removal of old npm allowed normal installation. Sorry for the panic button mode. Please close.

npm install failed

C:\Documents and Settings\Administrator>npm install -g nodist
npm http GET https://registry.npmjs.org/nodist
npm http 304 https://registry.npmjs.org/nodist
npm http GET https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/optimist
npm http GET https://registry.npmjs.org/request
npm http 304 https://registry.npmjs.org/request
npm http 304 https://registry.npmjs.org/optimist
npm http 304 https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/wordwrap
npm http 304 https://registry.npmjs.org/wordwrap

> [email protected] install C:\Documents and Settings\Administrator\Application Data\
npm\node_modules\nodist
> copy bin\bin.cmd %npm_config_prefix%\nodist.cmd

The syntax of the command is incorrect.

> [email protected] preuninstall C:\Documents and Settings\Administrator\Application
Data\npm\node_modules\nodist
> del %npm_config_prefix%\nodist.cmd

The system cannot find the path specified.
npm WARN continuing anyway [email protected] preuninstall: `del %npm_config_prefix%\n
odist.cmd`
npm WARN continuing anyway `cmd "/c" "del %npm_config_prefix%\\nodist.cmd"` fail
ed with 1
npm ERR! [email protected] install: `copy bin\bin.cmd %npm_config_prefix%\nodist.cmd`

npm ERR! `cmd "/c" "copy bin\\bin.cmd %npm_config_prefix%\\nodist.cmd"` failed w
ith 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the nodist package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     copy bin\bin.cmd %npm_config_prefix%\nodist.cmd
npm ERR! You can get their info via:
npm ERR!     npm owner ls nodist
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 5.1.2600
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nod
ejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "nodist"
npm ERR! cwd C:\Documents and Settings\Administrator
npm ERR! node -v v0.8.1
npm ERR! npm -v 1.1.33
npm ERR! code ELIFECYCLE
npm ERR! message [email protected] install: `copy bin\bin.cmd %npm_config_prefix%\nod
ist.cmd`
npm ERR! message `cmd "/c" "copy bin\\bin.cmd %npm_config_prefix%\\nodist.cmd"`
failed with 1
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     C:\Documents and Settings\Administrator\npm-debug.log
npm ERR! not ok code 0

Please help.
Thanks!

Allow version nubers like v0.8

Update fails with exceptions

Followed the instructions on the front page:

git clone
add bin directory to path
run 'nodist update'

I get:

C:\dev>nodist update
        1 file(s) copied.

module.js:340
    throw err;
          ^
Error: Cannot find module './polyfills.js'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:362:17)
    at require (module.js:378:17)
    at Object.<anonymous> (c:\Dev\nodist\bin\node_modules\npm\node_modules\graceful-fs\graceful-fs.js:8:1)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:362:17)
        1 file(s) moved.
Install dependencies...

module.js:340
    throw err;
          ^
Error: Cannot find module './polyfills.js'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:362:17)
    at require (module.js:378:17)
    at Object.<anonymous> (c:\Dev\nodist\bin\node_modules\npm\node_modules\graceful-fs\graceful-fs.js:8:1)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:362:17)
Installing latest stable version...

module.js:340
    throw err;
          ^
Error: Cannot find module 'mkdirp'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:362:17)
    at require (module.js:378:17)
    at Object.<anonymous> (c:\Dev\nodist\lib\nodist.js:27:18)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:362:17)

`npm install -g` doesn't work

... since bin's arent in PATH

Readme file is not clear about node installation existence drawbacks

Don't install node beforehand!

Two questions: why, what?

Documentation lacks explanation on drawbacks when node.js is already installed with a binary.

Should be node.js uninstalled before using nodist?

Place the code in a directory for use. It is not recommended to use Program Files since you will need to run all your commands in administrator mode. Instead use c:/nodist or similar.

What if nodist will be installed to %HOMEDRIVE%%HOMEPATH%\.nodist, the same place where .nvmw is installed by default without clattering the %HOMEDRIVE%

why not add instructions to set system wide environment variable with setx, e.g.:

setx /M PATH "%HOMEDRIVE%%HOMEPATH%\.nodist;%PATH%"

Thanks

nodist gives error "\Microsoft was unexpected at this time."

In Windows 7 Professional

Download master zipball
Unzip to C:\nodist
Open command processor (either regular or with "Run as administrator")
cd C:\nodist\bin
nodist

Output: \Microsoft was unexpected at this time.

This happens regardless of any arguments I've tried, such as --help or + 0.8.6

Per the installation instructions, I've also tried adding C:\nodist\bin\ to my system path. Same result, except I can reproduce the error no matter what my current working directory is.

Doesn't seem to run through Cygwin

I get the following error.

/../node.exe: No such file or directory/cygdrive/c/nodist/bin

It's a minor issue really, works fine through CMD.

Support for .node-version files

This would require the implementation of something very much like nodenv's shim:
https://github.com/OiNutter/nodenv#understanding-shims

(I tried this with a batch file before, but it turned out it doesn't work that well with deamons and that kinda stuff)

.node-version files are convenient and very useful, though.
If anyone wants to look into it, feel free

(@fschwiet ;) )

Looking for a different approach to the current implementation.

uses always old node version(v0.8.9) for node-gyp to install native modules

D:\git\dcc\dcc-setup>nodist v0.10.13
0.10.13

D:\git\dcc\dcc-setup>node -v
v0.10.13

D:\git\dcc\dcc-setup>npm -v
1.3.7

D:\git\dcc\dcc-setup>npm install pm-notify
npm http GET https://registry.npmjs.org/pm-notify
npm http 304 https://registry.npmjs.org/pm-notify

> [email protected] preinstall D:\git\dcc\dcc-setup\node_modules\pm-notify
> node-gyp rebuild


D:\git\dcc\dcc-setup\node_modules\pm-notify>node "C:\Users\adriano.raiano\.nodist\bin\node_modules\n
pm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild
gyp http GET http://nodejs.org/dist/v0.8.9/node-v0.8.9.tar.gz
gyp http 200 http://nodejs.org/dist/v0.8.9/node-v0.8.9.tar.gz
gyp http GET http://nodejs.org/dist/v0.8.9/node.lib
gyp http GET http://nodejs.org/dist/v0.8.9/x64/node.lib
gyp http 200 http://nodejs.org/dist/v0.8.9/node.lib
gyp http 200 http://nodejs.org/dist/v0.8.9/x64/node.lib
Die Projekte in dieser Projektmappe werden nacheinander erstellt. Um eine parallele Erstellung zu er
möglichen, müssen Sie den Schalter "/m" hinzufügen.
  pm.cpp
  pm_win.cpp
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\xlocale(323): warning C4530: C++ exc
eption handler used, but unwind semantics are not enabled. Specify /EHsc [D:\git\dcc\dcc-setup\node
_modules\pm-notify\build\pm.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\cstdio(48): warning C4995: 'gets': n
ame was marked as #pragma deprecated [D:\git\dcc\dcc-setup\node_modules\pm-notify\build\pm.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\cstdio(52): warning C4995: 'sprintf'
: name was marked as #pragma deprecated [D:\git\dcc\dcc-setup\node_modules\pm-notify\build\pm.vcxpr
oj]
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\cstdio(55): warning C4995: 'vsprintf
': name was marked as #pragma deprecated [D:\git\dcc\dcc-setup\node_modules\pm-notify\build\pm.vcxp
roj]
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\cstring(21): warning C4995: 'strcat'
: name was marked as #pragma deprecated [D:\git\dcc\dcc-setup\node_modules\pm-notify\build\pm.vcxpr
oj]
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\cstring(22): warning C4995: 'strcpy'
: name was marked as #pragma deprecated [D:\git\dcc\dcc-setup\node_modules\pm-notify\build\pm.vcxpr
oj]
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\cwchar(30): warning C4995: 'swprintf
': name was marked as #pragma deprecated [D:\git\dcc\dcc-setup\node_modules\pm-notify\build\pm.vcxp
roj]
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\cwchar(31): warning C4995: 'vswprint
f': name was marked as #pragma deprecated [D:\git\dcc\dcc-setup\node_modules\pm-notify\build\pm.vcx
proj]
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\cwchar(33): warning C4995: 'wcscat':
 name was marked as #pragma deprecated [D:\git\dcc\dcc-setup\node_modules\pm-notify\build\pm.vcxpro
j]
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\cwchar(35): warning C4995: 'wcscpy':
 name was marked as #pragma deprecated [D:\git\dcc\dcc-setup\node_modules\pm-notify\build\pm.vcxpro
j]
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\xlocale(323): warning C4530: C++ exc
eption handler used, but unwind semantics are not enabled. Specify /EHsc [D:\git\dcc\dcc-setup\node
_modules\pm-notify\build\pm.vcxproj]
C:\Users\adriano.raiano\.node-gyp\0.8.9\deps\v8\include\v8.h(178): warning C4506: no definition for
 inline function 'v8::Persistent<T> v8::Persistent<T>::New(v8::Handle<T>)' [D:\git\dcc\dcc-setup\no
de_modules\pm-notify\build\pm.vcxproj]
          with
          [
              T=v8::Object
          ]
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\string(757): warning C4995: 'swprint
f': name was marked as #pragma deprecated [D:\git\dcc\dcc-setup\node_modules\pm-notify\build\pm.vcx
proj]
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\string(766): warning C4995: 'swprint
f': name was marked as #pragma deprecated [D:\git\dcc\dcc-setup\node_modules\pm-notify\build\pm.vcx
proj]
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\string(775): warning C4995: 'swprint
f': name was marked as #pragma deprecated [D:\git\dcc\dcc-setup\node_modules\pm-notify\build\pm.vcx
proj]
C:\Users\adriano.raiano\.node-gyp\0.8.9\deps\v8\include\v8.h(178): warning C4506: no definition for
 inline function 'v8::Persistent<T> v8::Persistent<T>::New(v8::Handle<T>)' [D:\git\dcc\dcc-setup\no
de_modules\pm-notify\build\pm.vcxproj]
          with
          [
              T=v8::Object
          ]
     Creating library D:\git\dcc\dcc-setup\node_modules\pm-notify\build\Release\pm.lib and object D
  :\git\dcc\dcc-setup\node_modules\pm-notify\build\Release\pm.exp
  Generating code
  Finished generating code
  pm.vcxproj -> D:\git\dcc\dcc-setup\node_modules\pm-notify\build\Release\\pm.node
npm http GET https://registry.npmjs.org/bindings/1.1.0
npm http 304 https://registry.npmjs.org/bindings/1.1.0
[email protected] node_modules\pm-notify
└── [email protected]

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.