Cannot require from node

[indexzero]

node.js:134
        throw e; // process.nextTick error, or 'error' event on first tick
        ^
ReferenceError: document is not defined
    at new Socket (/Users/Charlie/Nodejitsu/node-http-proxy/node_modules/socket.io/node_modules/socket.io-client/lib/socket.js:24:5)
    at Object.connect (/Users/Charlie/Nodejitsu/node-http-proxy/node_modules/socket.io/node_modules/socket.io-client/lib/io.js:169:16)
    at Object.<anonymous> (/Users/Charlie/Nodejitsu/node-http-proxy/examples/standalone-websocket-proxy.js:98:21)
    at Module._compile (module.js:407:26)
    at Object..js (module.js:413:10)
    at Module.load (module.js:339:31)
    at Function._load (module.js:298:12)
    at Array.<anonymous> (module.js:426:10)
    at EventEmitter._tickCallback (node.js:126:26)

Seems like the line in question is: https://github.com/LearnBoost/Socket.IO/blob/master/lib/socket.js#L26

I can define document as a global, but that seems wrong. What's the best approach here?

[indexzero]

The code I'm using is quite simple. I've taken the npm socket.io package as a dependency and:

  var path = require('path');

  var ioPath = path.join(__dirname, '..', 'node_modules', 'socket.io');

  require.paths.unshift(path.join(ioPath, 'node_modules', 'socket.io-client', 'lib'));

  var parser = require('socket.io/lib/parser'),
      io = require('socket.io'),
      client = require('socket.io-client');

  var socket = client.connect('http://localhost:8081');

[rauchg]

This is a bug.

[indexzero]

Thanks for the quick response. Seems like there are a lot of calls to window and document that are causing intermittent errors.

[indexzero]

@fat @guille Any progress on this? I see a potential fix from @3rd-Eden

[3rd-Eden]

@indexzero that was still a commit from the 0.6 branch for some odd reason it ended up here, there haven't been much progress here. read as none but it will be solved soon once we fixed all major issues we encountered with the 0.7 release

[sgodzayc]

@indexzero @3rd-Eden
is there a quick fix? i need to migrate from 0.6 to 0.7

[3rd-Eden]

@sgodzayc Not really, but there are alternate ways of communicating with a socket.io server, we have created some tools for our test suite https://github.com/LearnBoost/socket.io/blob/master/test/common.js

which allows you to do a handshake, and communicate with the server.
See https://github.com/LearnBoost/socket.io/blob/master/test/transports.websocket.test.js#L22-57 for a implementation.

But I'm gonna start on this once I finished my EventSource transport. Because I really want to use the socket.io-client for our test suites as well.

[angermanmichael]

thanks very much for working on this after EventSource transport is finished. also, if you do not mind, could you publish an email to the news group saying this is now working --- I think there are probably a number of people anxiously awaiting this feature. thanks again, michael

[bewa]

when would this bug fixed?

[indexzero]

Oh snap! I didn't even notice this got fixed. Hello new hotness