This repository has been archived by the owner on Nov 8, 2024. It is now read-only.
forked from mdp/pitboss
-
Notifications
You must be signed in to change notification settings - Fork 1
When using Node 8, the console is available for the sandboxed code #13
Comments
Seems like specifically the |
honzajavorek
added a commit
to apiaryio/dredd
that referenced
this issue
Jan 11, 2018
@honzajavorek that is the reason why i've add so you can pass it as param.
|
honzajavorek
added a commit
to apiaryio/dredd
that referenced
this issue
Jan 11, 2018
@tu1ly I have libraries defined as follows: {
...
libraries: {'_log': customObject}
...
} According to my tests, that doesn't prevent const code = `
// make console unavailable
try {
// node >= 8
console = undefined;
} catch (_exc) {
// node < 8
var console = undefined;
}
runSandboxedUserCode(); // the actual sandboxed code
` |
3 tasks
@honzajavorek |
Nope, I want it unavailable in node >= 8 😄 |
honzajavorek
added a commit
to apiaryio/dredd
that referenced
this issue
Jan 18, 2018
honzajavorek
added a commit
to apiaryio/dredd
that referenced
this issue
Jan 18, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The last example (
test3
) demonstrates that while in Node 6 theconsole
is considered as not defined within the sandboxed code, in Node 8 it is suddenly available. Why is this happening?The text was updated successfully, but these errors were encountered: