Parse build output into a rich format we can display properly

[gaearon]

The build overlay still looks less rich than the runtime one:

It would be nice to actually parse this (if it matches known Babel and ESLint formats) and display a richer version with:

• Error message and file information in a runtime stack frame-like view
• Highlighted line that causes the issue

There would need to be tests verifying we don't regress if message format updates.

[gaearon]

cc @tharakawj

[tharakawj]

This seems to be an interesting idea. For lint errors, we might need to generate a code block with CodeFrame.

But I'm not sure how to test this. Anyway, I'll give it a try next week and we can think about testing later.

[stale[bot]]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 7 days if no further activity occurs.