Log gulp task failures to file regardless of UF_MODE

[Silic0nS0ldier]

There have been a few instances where a gulp task has failed and cannot be debugged due to lack of information. This is particularly annoying when issues only occur in a specific UF_MODE or only happen once (leaving the root cause unknown).

The solution here is to store all logged messages and dump them into a log file should things go wrong. Some work towards centralised logging has already been started. The hardest part of thing will be catching what gulp itself logs (we should however be able to provide our own logger), and forcing everything to log at maximum without everything also being dumped into the console.

[Silic0nS0ldier]

I'm thinking that getting this into 4.2 may be in our best interest as it will ensure that everything can be logged. The major refactor underpins the importance of this. So to get the ball rolling, some notes.

• Log location should match up with the rest of UserFrosting.
• Need to determine what the logging level should be.
• Is everything currently covered by the global log function? Are we controlling verbosity of anything that directly writes to console?

[Silic0nS0ldier]

Changing the output of execSync has been proving troublesome, however the way the source linked works means that you don't have to directly mess with it. This may provide a solution, provided it doesn't conflict with Gulp's logging system. https://github.com/monolithed/redirect-output/blob/master/index.ts

[Silic0nS0ldier]

Much to my irritation, there doesn't appear to be a way to capture all output, specifically if a child process (like using exec) is involved,

Related:

• Cover output of spawned processes that inherit stdio sindresorhus/hook-std#9
• Observe data emitted through stdout and stderr nodejs/node#8033

Everything emitted by gulp and us however emitted fine, which gives us rather decent coverage of our own tools. Will certainly help for debugging and support in certain scenarios.