Whenever an error occurs on the Java side, the Error that is thrown on the Node side does not seem to contain any stacktrace from the Node code. This can make it quite challenging to determine where in the Node code the offending call to Java was made, and the steps that led up to it.
Is there a way that a few frames of the Node execution might be included in the stack/message of the Error that this package throws?
Or is there a way to register a wrapper to the call to Java so that custom `try/catch` behavior can be applied universally to all calls made from Node to Java? I could add or re-raise a customized Error from there.
Thanks everyone,
Chris
I've created an issue for this here:
https://github.com/joeferner/node-java/issues/535