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
Log using process.stderr.write instead of console.error since this isn't an error #170
Comments
The fact that Gatsby treats it as error sounds like a bug in Gatsby. |
(disclaimer I'm one of the gatsby maintainers)
This is true, implementation wise in Node.js. I think it's worth to mention that I know that web isn't target for this package, but we are hoping to use same convention as web in gatsby to visually mark some messages as errors in terminal output - as shown in screenshot in the issue description (so it's easier for users to spot messages in output that could be pretty long in some cases).
We don't check what stream is used, just which console method is used - that's why we propose using I'm not super excited about hijacking |
As a result of c3b1df6#diff-168726dbe96b3ce427e7fedce31bb0bc, updates appear as errors for gatsby (and other projects that depend on
yurnalist
I think)However, I do understand the need to put this in
stderr
as opposed tostdout
, so how do we feel about replacingconsole.error
here with a call toprocess.stderr.write
?If this makes sense, we're happy to open a PR and get this patched! Thank you
The text was updated successfully, but these errors were encountered: