You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if the Rust swc library aborts in a release build, there is no information given to the user about what caused it. I would like to propose that an environment variable SWC_DEBUG set to 1, or some other sentinel string, would cause swc to print out the name of the file that it is about to try to transform. Currently, when you want to track down the source of an abort, you need to modify the source to include this extra logging. It would be very convenient if this information was presented to the user without too much extra effort.
The text was updated successfully, but these errors were encountered:
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.
Currently, if the Rust swc library aborts in a release build, there is no information given to the user about what caused it. I would like to propose that an environment variable
SWC_DEBUG
set to1
, or some other sentinel string, would cause swc to print out the name of the file that it is about to try to transform. Currently, when you want to track down the source of an abort, you need to modify the source to include this extra logging. It would be very convenient if this information was presented to the user without too much extra effort.The text was updated successfully, but these errors were encountered: