Shouldn't dispose of iframe after run

[amasad]

trafficstars

In node vm:

var c = vm.createContext({});
vm.runInContext('Array.foo = 1', c);
assert(1 === vm.runInContext('Array.foo'));

And that's not the case in this module because it disposes of iframe (real context) after each run.

[pluma]

Interesting. Closer inspection of node's context objects reveals that upon running something in a context the context object receives its own (non-enumerable) copy of every global, which is not identical with the current global.

I think the problem is that vm-browserify only copies properties which were already on the context before the eval or were introduced by the eval'd code.

[amasad]

It seems very hard to match the exact behavior on both so I wrote a more simplified module: context-eval

[tcql]

it seems that the iframe disposal also prevents you from running async code inside a context, which breaks some stuff I wanted to do