When one runs NetBeans on GraalVM, a "bubble" is shown asking whether to activate `node` from the GraalVM. If agreed, then the `node` execution shall happen on GraalVM's node implementation - including debugging with the JVM.
If one is using non-GraalVM's node, then the special GraalVM node support shall be inactive (apparently it is not). CCing Martin. -jt Dne středa 18. května 2022 20:23:02 CEST, Matthias Bläsing napsal(a): > Hi, > > I wanted to try to fix the NodeJS Debugger and noticed, that the > GraalVM support squats over it. It is a bit surprising, that on a > NodeJS it is assumed, that I want to start GraalVM. > > Given, that the common runtime for JS code in Web development and also > backend development is node, I assume, that this should get priority. > Before I begin to work on removing GraalVM from this, how was this > planned to work out or was nodeJS support just ignored? > > This is what I saw: > > "/usr/bin/node" > "--jvm.agentlib:jdwp=transport=dt_socket,address=44067,server=n,suspend=y" > "/home/matthias/tmp/NodeJsApplication/main.js" > > Seeing jvm parameters on a node invocation is IMHO a corner case. > > Greetings > > Matthias > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
