When debugging on GraalVM 1.0.0rc9 and in NetBeans 10 I don't see the SOURCE as JavaScript. Probably because it is Unnamed without any extension. Giving it app.js name fixes the problem.
put breakpoint before eval and invoke Debug Project action. Once the breakpoint (in Java code) is hit, use the new Toggle pause in GraalVM script action in debugger toolbar and once enabled, Continue. The execution stops at first line of your JavaScript. Since then your mixed Java+JavaScript debugging becomes reality, but it is better to see the source as JavaScript than unnamed one. For example the former allows one to add JavaScript breakpoints.
CC @entlicher, @geertjanw as this could be very nice demo showing how OracleLabs contribute to polyglot features of the IDE once NetBeans 10 is out.
When debugging on GraalVM 1.0.0rc9 and in NetBeans 10 I don't see the
SOURCEas JavaScript. Probably because it isUnnamedwithout any extension. Giving itapp.jsname fixes the problem.To reproduce start NetBeans 10 as:
put breakpoint before
evaland invoke Debug Project action. Once the breakpoint (in Java code) is hit, use the new Toggle pause in GraalVM script action in debugger toolbar and once enabled, Continue. The execution stops at first line of your JavaScript. Since then your mixed Java+JavaScript debugging becomes reality, but it is better to see the source as JavaScript than unnamed one. For example the former allows one to add JavaScript breakpoints.CC @entlicher, @geertjanw as this could be very nice demo showing how OracleLabs contribute to polyglot features of the IDE once NetBeans 10 is out.