Thank you for your kind words and for sharing your findings! The tip about the dbtools/launch directory is particularly useful. I’ll look into it. I’m glad the formatter continues to work well for you across these tools and versions.

I had been looking for a way to do that (without success so far), and then came your excellent article & accompanying Github repository. Not only does this enable to have Javascript back in SQLcl, but also (after tinkering a bit) in good old SQL Developer Classic, including its latest incarnation (26.2), without the requirement of installing GraalVM (which is important these days because sadly, due to Java licensing issues, in many corporations it has become forbidden to download Oracle JDKs). It’s a huge relief that I can continue to use the Trivadis PL/SQL formatter (or should we call it the Salvisberg formatter?) without being stuck forever on SQL Developer (Classic) 23.1.1.

As regards the SQL Developer for VS Code extension, I have found that, if instead of landing the GraalJS jar files into the dbtools/sqlcl/lib directory, they are put directly into the dbtools/launch directory, then Javascript become available both in the embedded sqlcl and in SQL worksheets (tested on 26.2.0). Of course I have to start VS Code through a wrapper script to set the required system properties through JAVA_JDK_OPTIONS, in order to silence the various warnings.

And I fully agree with you: this is fine power-user hackery, but Oracle should definitely have Javascript built-in as it used to be.

Thanks again!

Best regards,