-
-
Notifications
You must be signed in to change notification settings - Fork 431
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
ts-loader should not log compilerDetailsLogMessage
when profiling
#488
Comments
PRs welcome! |
@sokra, @TheLarkInn, @jhnns It does not seem reasonable to create a white list of cases when a loader can print something out as webpack can add new features at any time. |
No, I don't think so. We would need to expose a logger on the loader context. That would be a reasonable change. Personally, I think the loader should only output something to the console if a debug flag is set. |
Thanks @jhnns for your input. |
I know that the webpack progress indicator logs to stderr and it correctly doesn't get included in the redirected output. |
Interesting, looks like this should be logging to stderr as well. https://github.com/TypeStrong/ts-loader#loginfotostdout-boolean-defaultfalse |
Having a 68 line logging module plus external colouring library seems to be an overkill for a total 5 logging invocations. Any reason not to simply use |
For version 3 of ts-loader we'll be changing the default log level to warn. Once that lands users will no longer be affected by this. #631 (my own "aha" moment came when I realised I was using ts-loader in |
Closed with 3.0 |
That's a good idea 👍. |
The following line fails to create a valid JSON because
compilerDetailsLogMessage
gets logged before the json.webpack --profile --json > stats.json
compilerDetailsLogMessage
should not be logged when printing webpack stats.The text was updated successfully, but these errors were encountered: