You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some more context on this -- This happens when individual files were excluded from an earlier sass-lint pass, but still end up flowing through the pipe to .failOnError(). It seems like it would be pretty easy to either (a) 'skip' files if you don't see a .sassLint tracking property on them, or (b) throw a more meaningful error that would explain the cause of the issue to callers. I personally would lean towards (a) as I don't think there's a good reason for consumers to have to be aware of how gulp-sass-lint captures these details internally.
\node_modules\gulp-sass-lint\index.js:93
if (file.sassLint[0].errorCount > 0) {
^
TypeError: Cannot read property '0' of undefined
at DestroyableTransform._transform (\node_modules\gulp-sass-lint\index.js:93:22)
running latest on sass-lint and gulp-sass-lint.
The text was updated successfully, but these errors were encountered: