-
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
Upgrade to newer V8 and NodeJS #527
Comments
👍 Curious as well, I'd love to use this project if it's still being kept up |
Same here, we had plans to use J2V8 with node-red, but node-red requires node.js v8 or superior and recommends v12. We could help if some instructions are shared. |
Have you had a look at, or made any progress on, this since November? This came up in discussion on the "descope project" issue #441 (see also #469 and #477) about a year earlier, but Node support has since been removed in the shift to a new v8 base version. I too was interested in using j2v8 with Node-RED, and I did get an earlier version running back in 2018 (see #437 - some components such as mqtt caused a JVM crash). We've been looking for a solution, for a while, to embed script execution within a JVM (integrating better with our existing code), and Node-RED has the added bonus of a user interface and a big community. But the whole concept of scripting engines within regular JVMs seems to have fallen out of favour and $WORK is still too resource constrained to be able to maintain one by ourselves at present. |
For anyone looking for a Linux/Windows alternative, I'd suggest taking a look at https://github.com/caoccao/Javet |
Are there any plans to upgrade to a newer V8 and most important NodeJS?. NodeJS production is at 12.X and most JavaScript libraries do require NodeJS > 10.X.
Thank you.
The text was updated successfully, but these errors were encountered: