Adds a nice system for gulp tasks displaying their errors directly in the browser, rather than just in the console where they might be ignored/buried.
We already show breaking issues in the browser window – such as when compilation completely fails due to Sass or Webpack encountering an error – but this gives us the ability to display in-browser errors for events that would otherwise be difficult because the browser refreshes, such as:
JS/CSS linting finds issues
A recurring accessibility audit finds issues
This PR only adds in-browser notifications for ESLint issues, but will be easy to add to additional gulp tasks in the future.
Finishes #67
Adds a nice system for gulp tasks displaying their errors directly in the browser, rather than just in the console where they might be ignored/buried.
We already show breaking issues in the browser window – such as when compilation completely fails due to Sass or Webpack encountering an error – but this gives us the ability to display in-browser errors for events that would otherwise be difficult because the browser refreshes, such as:
This PR only adds in-browser notifications for ESLint issues, but will be easy to add to additional gulp tasks in the future.