[Enhance]: Improving SWC's Error Recovery for more friendly experience

[GiveMe-A-Name]

Describe the feature

The try_with_handler should return a SwcError instead of anyhow!(msg), it's helper upper application such as deno, rspack can get more detail about error.
Swc have many kind error with invoke wasm plugin error, wasm plugin emit custom error, js parser error ...., So upper application need more detail to distinguish what the error kind.

Example

// crate  swc_error_reporter
pub struct Error {
    inner: Box<InnerError>
}

struct InnerError {
   kind: ErrorKind,
   message: Cow<str>,
   ....
}

impl Display for Error { .. }

fn try_with_handler(...) -> Result<T, Error> { ... }

// rspack/core

match swc_try_with_handler {
      Ok(program) => program,
      Err(error) => {
          match error.kind() {
             // do somethings for different errors
          }
      },
}

// node_binding

#[napi] 
fn transform_sync(...) -> Result<T> {
   swc_core::transform(...).map_err(|e: SwcError| anyhow!(e.to_string()))
}

Babel plugin or link to the feature description

No response

Additional context

No response

[kdy1]

I like the idea. I used anyhow::Error because swc was designed as a bridge for nodejs and rust, but it's used from the Rust side now.

[GiveMe-A-Name]

I like the idea. I used anyhow::Error because swc was designed as a bridge for nodejs and rust, but it's used from the Rust side now.

Yes. if we need pass error to nodejs, we also can use anyhow::Error, we can can anyhow!(SwcError.to_string()) in node_binding.

[swc-bot]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.