boxed

JS doesn't have any useful built-in way to deal with success/failure, other than exceptions. We use Boxed[1] for this: Result .fromExecution(() => schema.parse(input)) .mapOk(parsed_input => /* */) .mapError(parse_errors => /* */) which is an alright way to deal with things IMO. I would hazard a guess that `parse` is a function introduced long ago, and `safeParse` came afterwards. (Safe as in "do not throw an exception") [1]: https://github.com/swan-io/boxed

Agree that try/catch is verbose and not terribly ergonomic, but my solution has been to treat errors as values rather than exceptions, by default. It's much less painful to achieve this if you use a library with an implementation of a Result type, which I admit is a bit of a nuisance workaround, but worth it. I've recently been using: https://github.com/swan-io/boxed. By far the greatest benefit is being able to sanely implement a type-safe API. To me, it is utter madness throwing custom extensions of the Error class arbitrarily deep in the call-stack, and then having a catch handler somewhere up the top hoping that each error case is matched and correctly translated to the intended http response (at least this seems to be a common alternative).