Skip to content
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

Enhancement: SWC_DEBUG environment variable #234

Closed
lily-mara opened this issue Feb 18, 2019 · 3 comments
Closed

Enhancement: SWC_DEBUG environment variable #234

lily-mara opened this issue Feb 18, 2019 · 3 comments
Assignees
Milestone

Comments

@lily-mara
Copy link
Contributor

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.

@lily-mara
Copy link
Contributor Author

Or the env_logger crate could be used to control this behavior as well

@kdy1 kdy1 added this to the v1.0.19 milestone Feb 19, 2019
@kdy1
Copy link
Member

kdy1 commented Feb 19, 2019

I updated node-swc to emit the file name when SWC_DEBUG is 1 or true.

@kdy1 kdy1 closed this as completed Feb 19, 2019
@kdy1 kdy1 self-assigned this Feb 19, 2019
@swc-bot
Copy link
Collaborator

swc-bot commented Oct 30, 2022

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.

@swc-project swc-project locked as resolved and limited conversation to collaborators Oct 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

3 participants