-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
V8 differences between NW.js 0.15.3 and Node.js 6.2.2 #5025
Comments
can't run firmata.js(including serialport) perfectly in nw.js |
@childwho You can ask questions in our mailing list https://groups.google.com/forum/#!forum/nwjs-general. And if you believe it's a bug, please submit a new issue with necessary details, including your sample app, NW.js version and OS. |
Is possible to refactor the code to avoid having to use the nw-gyp hack? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Following is the comparison of V8.h between NW.js 0.15.3 (v8 version: 5.1.281.65) and Node.js 6.2.2 (v8 version 5.0.71.52):
It will cause
IsUndefined()
and many APIs returns bad value when used in native modules built directly with node-gyp or npm.One example is Sqlite3. When sqlite3 is built with node-gyp directly using Node.js 6.2.2, following sample app failed to run and threw
Callback expected
error atdb.run()
, which means it requires a callback function. However it runs without problem with Node.js 6.2.2 directly.The text was updated successfully, but these errors were encountered: