I believe that the debug and chalk libraries could greatly improve the console output.
Debug would make it easy to see where messages are coming from (what module or plugin) and possibly to filter them.
Chalk would make the non-debug output (info / warn / error) more readable and set it apart from other console.log statements that might be used in user-space debugging.
What do you think?
It can be cool! It's quite hard to read in gatsby console (it's better with redux-dev-tools :) )
The must have should be https://github.com/SamVerschueren/listr to have a really nice bootstrap xp 馃構 (but it's can be hard to had on current stack ^^)

And a second nice to have can be a system to inject errors/stacks directly into the layout of website (as ionic)

(but debug/chalk can be a really good start, some modules have already a debug/chalk stack)
Definitely want to do a ton to improve the UX of the terminal output. Focus during alpha is on core code but during betas will turn to this. @fabien0102 I think building custom error screens in the client would be 馃挴 We could be streaming redux updates to browser and do custom stuff there.
Lots of interesting possibilities!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed due to inactivity.
This still needs done :-|
Just to chime in here, we'll also want to consider XTerm compatible output (e.g. linux compatibility without weird, special characters) with whatever logging solution we bake in. I'd definitely like to make some improvements to the CLI logging as part of these changes, and getting improved logging for Preview kinda dovetails alongside this issue.
The requirements as I see them are basically a way to limit output (e.g. with log levels), but get that same output in certain phases, e.g. gatsby build --verbose. Additionally, I believe there was some "nice to have" of different formats, e.g. simple strings, json logging, etc. which we could do with something like [winston]: https://www.npmjs.com/package/winston
cc @thebigredgeek @rase- we'll need to work with the OSS side of things to figure out what logger/log format actually _works_, or whether we could sanitize the output somehow, too.
Old issues will be closed after 30 days of inactivity. This issue has been quiet for 20 days and is being marked as stale. Reply here or add the label "not stale" to keep this issue open!