Last Friday we announced the availability of IntellIJ IDEA 13.1 RC2, a new release candidate for IntelliJ IDEA 13.1 bringing final support for Java 8. In other awesome news, besides coding assistance for Java 8 the new build also provides a built-in debugger for JDK8’s Nashorn. Nashorn is the new lightweight high-performance JavaScript runtime built on top of JVM.
With IntelliJ IDEA 13.1 RC2, now you can add breakpoints to your Nashorn scripts and go through them when debugging your Java application. Let’s see how it works on a simple example. Here we have an application which loads a Java interface implementation from in a Nashorn script. The interface has a “sayHello” method with a single String parameter and returning a String.
If we open the Nashorn script, we’ll see an almost regular JavaScript file. The only difference here is that this scripts accesses the Java runtime to instantiate an instance of the “demo.HelloHelper” Java class and to define an implementation for the “demo.HelloWorld” interface. Let’s add a breakpoint here to stop when the script is running.
When we run the application in the Debug mode, it stops at our breakpoint so we can see the state of local variables and step through the script statements.
Then we stop at another breakpoint we added, but already on the Java side. Here we can see the state of the “demo.HelloWorld” instance, returned by the script.
Now if we call the Step Into action, we’ll be able to step inside the script.
Note that here we use an instance of “demo.HelloHelper” Java class to get a “prefix.” This means that if we use the Step Into action again, we’ll get back to the Java side.
Also notice, that the Frames tab shows the exact stack of the invoked methods from both Java and Narshorn code.
As you can see, with IntelliJ IDEA it’s really easy to debug your Nashorn scripts. We’ll hope this feature will come useful for you as Nashorn is a very powerful tool for scripting your Java application.
As always your feedback is very welcome in our discussion forum and your bug reports in our issue tracker. Time’s limited though, as the release is just around the corner.
Develop with Pleasure!
Hi Andrey,
I have upgraded my IntelliJ to 13.1. But not sure it’s the RC2 you mentioned above, could you please confirm?
I tried to sample codes here, which can’t pass the compile since class HelloWorld can not be located in Java code.
Please give some hints.
Thanks
Harry
It should work with 13.1. Can you share your code sample? You can send it to andrey.cheptsov at gmail.com.
Had the same problem, the ‘HelloWorld’ interface isn’t show in the article:
public interface HelloWorld {
public String sayHello(String name);
}
Someone posted the same example to github here:
https://github.com/jbandi/Nashorn/tree/master/01-HelloNashorn
I have tried this github example in Intellij 2017 Ultimate, but the debugger does not step into the javascript file. Instead, the following is shown in the stacktrace (Frames): sayHello:-1, HelloWorld$$NashornJavaAdapter
Is this nashorn debugging still functioning in Intellij 2017?
Also, just in case someone else tries this example in 13.1+, the JS debugger is only enabled in Ultimate Edition.
http://devnet.jetbrains.com/message/5512395
Kind of similar to the first issue. I have the ultimate 13.1 with Build#IU-135.475 built on March 17 2014. But I can’ step into the js file as shown in the screenshot. But the sample prints out the hello-world as shared by Brad.
Thanks Brad for pointing an important missing component.
Will Nashorn support be added to WebStorm, too? *crosses fingers*
Nashorn debugging works great, but IDEA seems to ignore the nashorn javascript dialect. e.g. For Each statement is marked as error or Java.type is unrecognized.
Am I missing something?
I tried the steps and it works.
Does the debugging for Nashorn & JS code still work if I debug a Java application remotely? A typical case is my java code is running inside some kind of container.
the debugger stops at breakpoints in .js file, but does not stop at breakpoints in .ts files(typescript files). Does it support breakpoints in .ts file or I did something wrong?
I found an issue with the implementation:
I tested it on Windows, js-file-name can not be absolute path in engine.eval(“load(‘js-file-name’)”). Otherwise debugging does not work though the js code got executed.
Same problem appears on MacOS
Also the same issue found in multi module project even with relative path
Opened 2 issues
IDEA-126149 Nashorn debugging doesn’t work with absolute paths
IDEA-126148 Nashorn debugging doesn’t work with submodules
Was there any resolution to this? I can get the debugger in a simple single module practice but the exact same program and javascript was not debuggable in a multi-module project. Without that it is useless.
Pingback: Java 1.8 + JavaScript Engine Nashorn + Debugging javascript file - Umut's Weblog
The two above issues basically make the nashorn debugging support completely useless. If you have a multi module project, and who doesn’t in more than a quick test project, doesn’t work at all =(
This feature is great, but what if I want to preload script as string and then eval this? I know exactly what file it is – is ther any way how to tell Idea so I can debug such eval?
Is it working only with load(…) command in eval or are there any other options?
I encountered some of the same problems mentioned in the comments above. After some amount of experimentation, however, I was able to get things working satisfactorily. I wrote up some of my notes here:
Oops. Previous post didn’t include the URL. Try this: http://davidbuccola.blogspot.com/2015/02/debugging-nashorn-javascript-with.html
cannot view object of js, object become nashorn JO, need do more for this feuture:
function f(){
var a =1;
var b = 2;
a ++;
b ++;
var c = {result: a+b}; // * become JO, in netbeans it’s {result:4.0}*
print( c);
}
f();