socket.io dosn't run in VM "sandboxed-module"

[mStirner]

Hay, i have a little problem.

I cant use socket.io inside a node js VM.
When i run it i become this error: "TypeError: Cannot read property 'prototype' of undefined"

/home/marc/NetBeansProjects/Project/node_modules/socket.io-client/node_modules/json3/lib/json3.js:50
var objectProto = Object.prototype,
^
TypeError: Cannot read property 'prototype' of undefined
at runInContext (/home/marc/NetBeansProjects/Project/node_modules/socket.io-client/node_modules/json3/lib/json3.js:50:29)

As VM i use the module "sandboxed-module"

[mStirner]

I found a "Quick & Dirty" Solution:

The problem is the "json3" module.
I added in the function "runInContext" (path: json3/lib/json3.js) before:

context || (context = root["Object"]());
exports || (exports = root["Object"]());

this line:

root = global;

final:

root = global;
context || (context = root["Object"]());
exports || (exports = root["Object"]());

Now it works, but is this the fine way ?
Or have i problems with the configuration of the vm ?

[nkzawa]

This one https://github.com/felixge/node-sandboxed-module ? I'm not familiar with the module, but that sounds the issue of vm module to me.

[mStirner]

Yep., it is the module.
What do the vm wrong ?

[nkzawa]

I'm not sure if the vm module is wrong, but I don't think we can do something to solve the problem. Can you create the issue on node-sandboxed-module or json3 instead?

[mStirner]

json3 module issues: bestiejs/json3#86
vm module issues: felixge/node-sandboxed-module#55

[dozoisch]

I'm hitting exactly the same issue in a WebWorker with socket.io-client@1.4.5. Trying to figure out a work around. The issue seems to originate from json3. At least I can still downgrade back to socket.io-client@1.3.7, it was working fine on that version.

[ghost]

@dozoisch cheers, looking at a workaround as well but rolling back to 1.3.7 sorted the issue for now.

👍

[chge]

It's sandboxed-module issue.

[darrachequesne]

That issue was closed automatically. Please check if your issue is fixed with the latest release, and reopen if needed (with a fiddle reproducing the issue if possible).