Similar to what we did for the wasm-binding code, we should implement changes to the node-bindings to map errors to extract out the internal error message from recrypt-rs and expose that to the caller. Currently the caller just gets a fairly unhelpful "neon error" style message.
Similar to what we did for the wasm-binding code, we should implement changes to the node-bindings to map errors to extract out the internal error message from recrypt-rs and expose that to the caller. Currently the caller just gets a fairly unhelpful "neon error" style message.