Numeric wrapper classes coverted based on its values about graaljs HOT 2 CLOSED

Thank you for reporting this, we'll take a look into it shortly.
Tracked internally on GR 50804

from graaljs.

Is there a way to keep the numeric wrapper class?

Not when you are invoking a Java method that takes Object. When you need a particular primitive type, I suggest you to invoke a (helper) Java method that takes a parameter of the desired type. I understand that this can be clumsy but it is the safe approach.

Some background: JavaScript has just one number type (ignoring bigint). This type corresponds to Java double. That's why graal-js works with the numbers as if they were doubles. It is using various types (like int) internally but that's an implementation detail. The good news is that the internals of graal-js support long in a limited way. So, it was not that difficult to ensure that long is not converted to a different numeric type eagerly (as it was done in your test-case). In other words, your long-based test-case should work with the mentioned change.

I understand that it would be nice to be able to pass other numeric types (byte, short, float) in the same way. Unfortunately, that would require larger and more risky changes within graal-js. So, we are not pursuing this direction (for now). We may revisit this decision if we see some other compelling use-cases.

from graaljs.