I have so far been unsuccessful in getting node.js integrated. I got a basic "hello, world" server running initially, and I have the dev version of this module partially running. I tried both the "recommended release" and the dev. I'm getting a "TypeError: Object #
has no method 'getAgent'" on "server.js:108 agent: http.getAgent(settings.backend.host, settings.backend.port),". I haven't been able to find any issue on this. I get it whenever I access the website from any browser, and the server crashes.
If I comment out that line, the server runs without crashing. It seems to work fine when I access the site using IE, there are messages back and forth as expected. However, if I use Chrome or Firefox, I get a constant never ending stream of "warn - client not handshaken client should reconnect". From what I've been able to find, it sounds like that may be a socket.io issue, but I haven't seen any resolution. I'm using socket.io 0.8.5. Do I need to downgrade? Is there something else I'm doing wrong that no one else seems to be having these problems? Thanks!
Comments
Comment #1
julien commentedYes your node version is too recent, try the 0.4.7
Comment #2
Anonymous (not verified) commentedjust committed a fix for this, we don't need to use getAgent().
Comment #3
olevelo commentedFinally! For any others with problems, it seems you have to have node.js 0.4.7 and socket.io 0.8.4. I do see that getAgent has been added back in. Otherwise the latest node.js might work...
Comment #4
olevelo commentedSo much for that...Chrome is working fine now, but Firefox is still doing the exact same thing with the endless stream of "client not handshaken...".
Comment #5
triviab commentedHi, what is the actual version dream team then, in order to have a working environment ?
Nodejs module : 7.x-1.x-dev (based on this thread)
Node@0.4.7 (based on this thread)
(based on the README in nodejs drupal module) connect@1.1.4 + express@2.4.3 : but express seems to require connect@>1.5.2 while downgrading connect to 1.1.4
socket.io@0.8.4 (based on this thread)
Could you enlighten me on those compatibilities ?
Comment #6
vishun commentedI'm experiencing the same issue as the original poster on 6.x-1.x-dev while trying to utilize Node.js v0.6.0 and socket.io v.8 (via npm install). I think it would be a good idea to clarify on the project page or README.txt what versions this module is compatible with.