-
Notifications
You must be signed in to change notification settings - Fork 37
feat: --trace-warnings #53
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #53 +/- ##
=========================================
Coverage ? 99.60%
=========================================
Files ? 6
Lines ? 253
Branches ? 50
=========================================
Hits ? 252
Misses ? 1
Partials ? 0
Continue to review full report at Codecov.
|
@hyj1991 也瞅瞅,默认开的话,会不会有什么性能问题? |
一般来说不会有额外的性能问题,这个 flag 实际上就是开启后会在 |
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.
+1
|
--trace-warnings 先关闭, Experimental 特性还是允许应用使用的。 |
哦,不对,跟这个无关。。。忽略。 |
start ensure no stderr, so open --trace-warnings will helpful for debug
Checklist
npm test
passesAffected core subsystem(s)
Description of change