-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JSCS errors getting swallowed somewhere #107
Comments
This sounds a little like #42 |
Did you change that in your .jscsrc or in gulp call? |
|
Hmm....i had similar issue, but putting maxErros inside .jscsrc fixed it (I was trying to pass it as part of gulp-jscs option before) |
I couldn't find any joy with it. As a workaround I added an npm build task, eg in
Also considering eslint as an "extreme workaround" but I've moved onto a different project for the moment. |
I have a gulp task like this:
Depending on when errors are encountered they do not seem to be reported. For example, if I change the glob pattern to
["zzz/**/*.js", "{aaa,bbb,ccc}/**/*.js"]
(in this example only the dir zzz contains errors), suddenly the reporter outputs errors.It seems like the reporter somehow gets "saturated" with messages so I tried changing the
maxErrors
config for jscs but this didn't make a difference.Installed versions:
The text was updated successfully, but these errors were encountered: