-
-
Notifications
You must be signed in to change notification settings - Fork 433
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
Info string on stdout causes problem to --json webpack output #95
Comments
If you use the silent flag that info won't be written. I'm not sure using stderr would be correct since it's not an error. |
@jbrantly It's not uncommon to use Reference: https://github.com/npm/npmlog |
@blakeembrey Interesting. Maybe something to look at then. @alexdrel For the time being does the |
|
Why do you have to change the webpack config back and forth? Just leave the silent flag on. All it affects is that one message which you probably don't care much about once things are "set up". Re: stderr, I'm open to that. |
@jbrantly - I kinda like it :) - it shows ts version and I use to jump between nightly,1.6.2 and 1.7.2 (which I don't quite understand - is it official and how it made its way into sublime plugin). |
That's... actually a really good reason 😁 |
Fixed in v0.7.0. Thanks for reporting! |
Hi,
The ts-loader writes info string to stdout:
When building JSON module statistics it goes to the json file and has to be removed manually.
Of course it is a minor nuisance but it would be nice if it will be written to stderr instead of stdout.
Thanks
The text was updated successfully, but these errors were encountered: