This change is unfortunate, the JSValueConst is used to tell the programmer that the value is not consumed by the function call. The name is not perfect and a more explicit alternative is desirable, but removing the distinction between JSValue and JSValueConst is error-prone, it hides valuable information.

I'll be happy to bring it back if / when we come up with a better replacement! Right now it was just noise and some casting.