Manifest file

error.log

npm http GET https://registry.npmjs.org/colors
npm http GET https://registry.npmjs.org/optimist
npm http GET https://registry.npmjs.org/pkginfo
npm http GET https://registry.npmjs.org/vows
npm http GET https://registry.npmjs.org/request
npm http GET https://registry.npmjs.org/async
npm http GET https://registry.npmjs.org/socket.io
npm http 304 https://registry.npmjs.org/colors
npm http 304 https://registry.npmjs.org/optimist
npm http 304 https://registry.npmjs.org/request
npm http 304 https://registry.npmjs.org/pkginfo
npm http 304 https://registry.npmjs.org/async
npm http 304 https://registry.npmjs.org/socket.io
npm http 304 https://registry.npmjs.org/vows
npm http GET https://registry.npmjs.org/socket.io/-/socket.io-0.6.18.tgz
npm http 200 https://registry.npmjs.org/socket.io/-/socket.io-0.6.18.tgz

npm ERR! SyntaxError: Unexpected token }
npm ERR!     at Object.parse (native)
npm ERR!     at Packer.readRules (/usr/lib/nodejs/npm/node_modules/fstream-npm/fstream-npm.js:174:31)
npm ERR!     at Packer.<anonymous> (/usr/lib/nodejs/npm/node_modules/fstream-npm/node_modules/fstream-ignore/ignore.js:132:22)
npm ERR!     at [object Object].<anonymous> (fs.js:123:5)
npm ERR!     at [object Object].emit (events.js:64:17)
npm ERR!     at fs.js:1181:12
npm ERR!     at Object.oncomplete (/usr/lib/nodejs/npm/node_modules/graceful-fs/graceful-fs.js:94:5)
npm ERR! 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! 
npm ERR! System Linux 2.6.38-020638-generic
npm ERR! command "node" "/usr/bin/npm" "install"
npm ERR! cwd /home/rspectre/Desktop/node-http-proxy
npm ERR! node -v v0.6.15
npm ERR! npm -v 1.1.16
npm ERR! type unexpected_token
npm ERR! arguments [ '}' ]
npm ERR! message Unexpected token }
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/rspectre/Desktop/node-http-proxy/npm-debug.log
npm not ok

package.json

{
  "name": "http-proxy",
  "version": "0.8.0",
  "description": "A full-featured http reverse proxy for node.js",
  "author": "Charlie Robbins <[email protected]>",
  "contributors": [
    { "name": "Mikeal Rogers", "email": "[email protected]" }, 
    { "name": "Marak Squires", "email": "[email protected]" },
    { "name": "Fedor Indutny", "email": "[email protected]" },
    { "name": "Dominic Tarr", "email": "[email protected]" }
  ],
  "repository": {
    "type": "git",
    "url": "http://github.com/nodejitsu/node-http-proxy.git" 
  },
  "keywords": ["reverse", "proxy", "http"],
  "dependencies": {
    "colors": "0.x.x",
    "optimist": "0.2.x",
    "pkginfo": "0.2.x"
  },
  "devDependencies": {
    "request": "1.9.x",
    "vows": "0.5.x",
    "async": "0.1.x",
    "socket.io": "0.6.x"
  },
  "main": "./lib/node-http-proxy",
  "bin": { "node-http-proxy": "./bin/node-http-proxy" },
  "scripts": { 
    "test": "npm run-script test-http && npm run-script test-https && npm run-script test-core",
    "test-http": "vows --spec && vows --spec --target=secure",
    "test-https": "vows --spec --source=secure && vows --spec --source=secure --target=secure",
    "test-core": "test/core/run"
  },
  "engines": { "node": ">= 0.6.6" }
}

Is it possible to know in which context you created this gist ? We are having the same issue

Was showing how npm was dirtnapping on socket.io install. Never did figure out what the deal was.

Ok. Did you create this gist to mention on a github issue or stckoverflow or sth ? I would like to be able to follow this somehow. Cheers

Negative - was just showing the author of the module I was working with. Haven't really pursued a solution.

On Wed, Apr 18, 2012 at 12:23 PM, Ivan Maireaux < ***@***.*** > wrote: Ok. Did you create this gist to mention on a github issue or stckoverflow or sth ? I would like to be able to follow this somehow. Cheers --- Reply to this email directly or view it on GitHub: https://gist.github.com/2387930

## /rob - new york: +1 718 989 1458 - london: +44 20 7183 8695 - @dN0t

i'm temporarily hard-coding to socket.io 0.6.17 instead of 0.6.x in the package.json as a work-around

I've opened a pull request to use 0.6.17 until the project's ready to move to a more modern version of socket.io:

http-party/node-http-proxy#233