-
-
Notifications
You must be signed in to change notification settings - Fork 494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(resolver): print detailed error messages for oxc_resolver #4564
Comments
hi~ I need some help :), I try to deal with
But I found that oxc lacked such an implementation: like this:
Is that true? Or is there another solution? |
Feel free to add the From / Into trait in oxc_resolver as well, and link it with Otherwise give me your work-in-progress branch and I'll add the trait. |
I'll have a try |
I have successfully debugging |
I can make a quick release after your PR in oxc 😁 |
patch for rspack issue [#4564](web-infra-dev/rspack#4564)
patch for rspack issue [#4564](web-infra-dev/rspack#4564)
patch for rspack issue [#4564](web-infra-dev/rspack#4564)
System Info
None
Details
The current implementation doesn't cover all error messages thrown by oxc_resolver:
rspack/crates/rspack_core/src/resolver/resolver_impl.rs
Lines 406 to 433 in f3b27b9
Notice it only catches 2 errors and falls back to a generic error. oxc_resolver actually throws a lot more errors: https://github.com/web-infra-dev/oxc/blob/7d85492a03e34fec11e27eae42db28a7c3f12e16/crates/oxc_resolver/src/error.rs#L6
It would be nice to cover and print nice error messages for all of them.
Reproduce link
No response
Reproduce Steps
To get started, try Rspack with the
experiments.rspackFuture.new_resolver = true
configuration and then introduce any of the oxc_resolver errors in your setup.The text was updated successfully, but these errors were encountered: