Common Issues and Their Fixes

There are a few common issues we've seen that are hard to track down/debug. Here are the solutions to those problems. Before trying any of these, please make sure you have Updated to the Latest Version of Gulp Sass.

Gulp Watch Stops Working On An Error

Problem: When using Gulp Sass's new .on('error', sass.logError) error handling, especially when using it in conjunction with gulp.watch, if an error occurs, any attempt to recompile Sass will not work.

Solution: Take a very close look at the Basic Usage example and note that the Gulp task stream is not returned in the function. Removing the return from the Gulp stream will fix the issue. Alternatively, Gulp Plumber can be utilized in conjunction with return-ing the Gulp stream.

Related Issues: #90 #90 (comment) #90 (comment)

Partials Sporadically Not Found

Problem: When compiling, unpredictably, seemingly without pattern, sometimes partials that are known to exist cannot be found by Sass, whereas other times everything compiles without issue.

Solution: Everyone who had reported this issue appears to be on a Windows machine using Sublime Text and had its atomic_save feature disabled. Everyone who added "atomic_save" : true to their user settings saw this error stop.

Related Issues: #235 #235 (comment)

Cannot Install Gulp Sass

Problem: When trying to install Gulp Sass, an error occurs and installation cannot be completed.

Solution: This is overwhelmingly a problem installing Node Sass. There are a large number of issues pertaining to installing Node Sass, please look through them to help resolve this for the specific platform being run.