Not working with node-webkit

[goldfire]

Testing on node-webkit 0.10.x and 0.11.x, sock.js 1.0 fails to connect. However, reverting to 0.3.4 works perfectly. I've yet to figure out what might be causing this, but thought someone else might have run into this as well.

[brycekahle]

More details would be appreciated. I haven't done any testing with node-webkit, but I'm guessing it might set the Origin to something tricky.

[darshan-rambhia]

Is there any update on the Issue?

[brycekahle]

@bytekoders I'm waiting for more information from @goldfire. If you anyinformation, that would be a lot of help. I need way more detail before I can go about confirming the issue.

[brycekahle]

Closing due to insufficient information

[hgwood]

I'm running into this issue and investigating it. The problem arises because of browserify expecting either global or window to be defined, but not both like in node-webkit.

For example:

module.exports = global.WebSocket || global.MozWebSocket;

In SockJS' browser build, browserify replaces global by the expression typeof global !== "undefined" ? global : typeof self !== "undefined" ? self : typeof window !== "undefined" ? window : {} (see here). In a browser, this expression returnswindow. In node-webkit, global is defined and gets picked up, but it does not have a property WebSocket. Therefore, "All transports failed".

So this is effectively a problem between browserify and node-webkit. I'm still looking for the right way to fix, in particular if SockJS can do something about it or if the fix should be on the consumer side.

Browserify issue: browserify/browserify#1189
PR fixing said issue: browserify/insert-module-globals#48

Other possibly related issues: browserify/browserify#481, browserify/browserify#1025, browserify/browserify#834.

[hgwood]

Workaround: Object.setPrototypeOf(global, window).

[brycekahle]

It appears that browserify can fix this without needing SockJS to do anything specific.

[hgwood]

Yes, I agree.

[Slayer95]

This is fixed for me with nw.js 0.13-rc-2