-
Notifications
You must be signed in to change notification settings - Fork 355
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
setTimeout from NodeJS does not work #209
Comments
Without looking directly at the code I do believe that you may need to implement these functions yourself. If I figure something out I will post back here! |
Well, I thought so, but still it is irritating that the function is there, but doesn't work as expected. It would probably be better to remove it from the environment to hint people at the fact that they have to implement it themselves. |
It seems like many of the NodeJS things never worked properly. We are reducing the scope of this project to V8 on Android. If someone wants to build a downstream project that builds and maintains NodeJS support, I would be happy to help them set that up. Unfortunately, I don't have the cycles do that though and I think it's better to be honest about the work I can do. Please see #441 for more information. |
as #406 say. I can't figure out how to not release the object... |
I tried the following snippet in a NodeJS environment and in J2V8 NodeJS:
In my local node installation the output was what I would expect:
In J2V8 though, the output was just this:
OS: Linux x64
J2V8 version: 4.6.0
The text was updated successfully, but these errors were encountered: