Github user bananer commented on the issue:
    @jeking3 This is a well-intended change but I think it is not implemented 
correctly and will break error handling for users.
    In some places in the compiler the input to `render_recv_throw` already is 
a proper `Error` (the JS exception class), e.g.
    This is not the case for other places:
    The proper way of doing this would be to inspect all usages of 
`render_recv_throw` to see if the argument needs to be wrapped in `new 
Error(…)`. Still then, this could break error handling that relies on these 
cases being strings.


Reply via email to