`gulp` continues to run exported `styles` task even after a syntax error is logged to the command line

[rgadon107]

Issue summary

The gulp build tool fails to rebuild the style.css and style.min.css files in the developers child theme when either:

• a syntax error occurs in the SASS partial files; or
• a variable is not properly registered elsewhere (e.g. font-size, color).

The gulp watch and gulp styles tasks continue to work even after a syntax error is logged to the command line. Because the styles task takes up many lines on the command line, the syntax error is easily overlooked when the Terminal view is kept small.

PHPStorm renders a file error, which provided the tip off that the child theme's CSS was not being built from the SASS partial file.

Recommendation

When function sassToCSS() in '/wp-content/themes/developers/dev/gulpfile.js/styles.js' encounters a syntax error, execution of the function should stop, return a sound, and log the error. The exported gulp styles task should not run until the error is resolved.

[rgadon107]

@hellofromtonya Here's an example of a deliberate error; a padding property is added to a selector. A semicolon is deliberately left off after the value is entered. PHPStorm flags the file (and path/to/file) with an error (see squiggly lines).

On the Terminal command line inside PHPStorm, the gulp styles task runs. When the frame is expanded, the syntax error was logged and can be seen (see screenshot below).

However, there's no audible signal that the watch task flagged an error. I typically don't keep the Terminal tab in the IDE open large enough to catch an error message that might flash by.

The gulp styles task returns affirmative messages that the styles were rebuilt. In fact, they were not.

Once the syntax is fixed on line 46, the errors in the IDE resolve and the style.css file is updated.

In styles.js file ( wp-content/themes/developers/dev/gulpfile.js/styles.js ), can function sassToCss() provide an audible signal in the even of a syntax or build error? The gulp styles task should not run in the event of a logged error.