-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JavaScript vm broken (bad Proxy implementation?) #309
Comments
Maybe the issue lays somewhere else. Take this script for example:
In stackblitz this works, in native NodeJS not. Since global should not be defined. Also "this" seems to be different than in native NodeJS. |
Thanks for reporting this issue. It seems to be a bug. |
Good news, this has been fixed and it's now available. Here's an example. I have also tested |
You guys are awesome! It works, thanks! |
@freehuntx Just a quick update that |
Describe the bug
When defining properties on a object returned by the vm, they behave differently than in NodeJS.
This breaks for example the testing framework Jest. (As you can see here: #293)
Example code:
Link to the blitz that caused the error
https://stackblitz.com/edit/node-7mnp6x
Steps to reproduce
node index
in the consoleExpected behavior
Console should print:
Screenshots
Platform
Additional context
I created this bug ticket as a result of this: #293
The text was updated successfully, but these errors were encountered: