Marcel Laverdet
Marcel Laverdet
I've noticed some spooky behavior here specifically with the console.* functions. I tend to wrap all the console functions in closures for this reason. I'll leave this open for reference...
Yeah this is a known footgun. This also results in errors that don't have anywhere to go: ```js const ivm = require('isolated-vm'); const isolate = new ivm.Isolate(); const context =...
Probably the easiest solution I can suggest for now is to forward your handlers back to the nodejs isolate and invoke them explicitly using `apply` so that you can pass...
Yeah this is a known issue. If you wait long enough it should conceivably quit. What's happened here is the scheduler got filled up with a bunch of tasks from...
Hmm WSL is a really wonky environment. Can you try in CMD and let me know if it works? I may have to modify or disable this particular feature on...
To update on this I'm currently holding back a little bit on expanding module support because the development within nodejs and v8 is still pretty rapid. I think some semver-major...
For example if you wanted lodash available in your isolate you would put this in `webpack.config.js`: ```js module.exports = { entry: 'lodash', output: { library: 'lodash', }, }; ``` After...
Security concerns?
Yeah this test has been failing on travis-ci but I wasn't able to repro locally. More information about your platform would be helpful.
I tried to reproduce on my local Gentoo machine, a Docker VM, and an AWS Ubuntu VM. Actually Travis-CI is showing that `transfer-options.js` is failing on nodejs v16 as well:...