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
fix(nft): correctly annotate transpilation errors in nft bundler #1086
Conversation
Add customErrorInfo to errors happening during transpilation of esm with esbuild in the nft bundler
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! I left a super minor comment that we usually wouldn't care much about, but since you're new to the codebase I figured it's useful to align on those things.
Also, we tend to use the feedback ladder in PR reviews, hence the [dust]
prefix.
Co-authored-by: Eduardo Bouças <mail@eduardoboucas.com>
β± Benchmark resultsComparing with 61e5b72 largeDepsEsbuild: 6.3sβ¬οΈ 5.42% decrease vs. 61e5b72
Legend
largeDepsZisi: 44.2sβ¬οΈ 6.26% decrease vs. 61e5b72
Legend
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
π
Ah, a final comment about conventions: you're rightly using the fix:
prefix to signal a patch update, but there's no need to use the (nft)
namespace. We typically only do that for dependency updates (example), which are handled automatically by robots. π€
π Thanks for submitting a pull request! π
Summary
Add customErrorInfo to errors happening during transpilation of esm with esbuild in the nft bundler.
I had to loop the function name through to the actual
esbuild
call, to generate the error location properly.For us to review and ship your PR efficiently, please perform the following steps:
This ensures we can discuss the changes and get feedback from everyone that should be involved. If you`re fixing
a typo or something that`s on fire π₯ (e.g. incident related), you can skip this step.
passes our tests.