Gulp 使Browserify transform Hintify在出现错误时继续

我在和一起喝。捕捉错误的方法似乎类似于：

browserify({
    entries: 'app.js',
    transform: [
        // Some other transforms
        plugins.hintify
    ]
    // A bunch of other settings
}).bundle()
    // Error handling
    .on('error', function(error) {
        util.beep(); // Util is gulp-util
        util.log(error);
        this.emit('end');
    })
    .pipe(...)

这非常有效，每次我违反我的

jshint

我都会得到这样的结果：

Users/me/Sites/project/client/scripts/app.js: line 11, col 23, Missing semicolon.

然后构建停止

然而，即使我忘记了分号，我还是希望构建继续进行。现在，任何

jshint

错误都会停止处理构建。我喜欢检查我的代码是否达到标准，但是如果函数中有一个未使用的参数，它不应该阻止所有的东西。p>

---

帮助？

当前设置适用于我（配置sam as）：

---

用jshint

^1.12.0

你看到了吗？也许它是你想要的。我看到它有一个

maxerr

propertyyah，我曾经使用过类似的设置，我可以让它正常工作。但是，当我尝试使用Browserify转换-hintify时，我遇到了上面的问题。我不熟悉G Browserify，但可能描述了类似的设置？他们也在使用而不是。这基本上与您描述的设置相同，也是我到目前为止使用的设置。然而，我想知道这是否只在

hintify

中才可能实现……不幸的是，这是我所知道的。对不起，我帮不了什么忙

var jshint = require('gulp-jshint');
var notify = require('gulp-notify');
var stylish = require('jshint-stylish')
...
.pipe(jshint('.jshintrc'))
.pipe(jshint.reporter('jshint-stylish'))
//.pipe(jshint.reporter('fail')) // <- omit a fail reporter 
...

...
.pipe(jshint('.jshintrc'))
.pipe(jshint.reporter('jshint-stylish'))
.pipe(jshint.reporter('fail'))
.on('error', notify.onError({ message: 'JS hint fail'})) // <- pipe fail to notification
...

...
src\m\typings.js
  line 0   col 0   ES5 option is now set per default
  line 3   col 18  ['SUCCESS'] is better written in dot notation.
  line 4   col 18  ['FAILURE'] is better written in dot notation.
  line 5   col 18  ['UNSTABLE'] is better written in dot notation.
  line 6   col 18  ['NOT_BUILT'] is better written in dot notation.
  line 10  col 26  ['info'] is better written in dot notation.
  line 11  col 26  ['success'] is better written in dot notation.
  line 12  col 26  ['mark'] is better written in dot notation.
  line 13  col 26  ['warn'] is better written in dot notation.
  line 14  col 26  ['error'] is better written in dot notation.
  line 15  col 26  ['debug'] is better written in dot notation.
  line 16  col 26  ['none'] is better written in dot notation.
  line 18  col 1   Unnecessary semicolon.

  ‼  13 warnings

[10:08:32] src\m\typings.js

src\helper\scaffolding.helper.js
  line 0    col 0    ES5 option is now set per default
  line 65   col 61   Regular parameters cannot come after default parameters.
  line 82   col 79   Expected an assignment or function call and instead saw an expression.
  line 84   col 77   Regular parameters cannot come after default parameters.
  line 90   col 39   Expected an assignment or function call and instead saw an expression.
  line 91   col 21   Missing 'new' prefix when invoking a constructor.
  line 91   col 60   Expected an assignment or function call and instead saw an expression.
  line 105  col 46   Expected an assignment or function call and instead saw an expression.
  line 106  col 29   Missing 'new' prefix when invoking a constructor.
  line 106  col 103  Expected an assignment or function call and instead saw an expression.
  line 3    col 12   'require' is not defined.
  line 4    col 14   'require' is not defined.
  line 5    col 11   'require' is not defined.
  line 6    col 19   'require' is not defined.
  line 7    col 10   'require' is not defined.
  line 8    col 13   'require' is not defined.
  line 9    col 13   'require' is not defined.
  line 33   col 17   'none' is not defined.
  line 42   col 13   'color' is not defined.
  line 45   col 13   'color' is not defined.
  line 48   col 13   'color' is not defined.
  line 51   col 13   'color' is not defined.
  line 54   col 13   'color' is not defined.
  line 57   col 13   'color' is not defined.
  line 60   col 13   'color' is not defined.
  line 63   col 12   'color' is not defined.
  line 85   col 25   'process' is not defined.

  ×  2 errors
  ‼  25 warnings

[10:08:32] src\helper\scaffolding.helper.js

src\helper\scaffolding.server.js
  line 0   col 0    ES5 option is now set per default
  line 22  col 44   Expected an assignment or function call and instead saw an expression.
  line 23  col 25   Missing 'new' prefix when invoking a constructor.
  line 23  col 75   Expected an assignment or function call and instead saw an expression.
  line 25  col 43   Expected an assignment or function call and instead saw an expression.
  line 26  col 25   Missing 'new' prefix when invoking a constructor.
  line 26  col 117  Expected an assignment or function call and instead saw an expression.
  line 38  col 40   Expected an assignment or function call and instead saw an expression.
  line 39  col 21   Missing 'new' prefix when invoking a constructor.
  line 39  col 50   Expected an assignment or function call and instead saw an expression.
  line 74  col 43   Expected an assignment or function call and instead saw an expression.
  line 75  col 25   Missing 'new' prefix when invoking a constructor.
  line 75  col 96   Expected an assignment or function call and instead saw an expression.
  line 4   col 12   'require' is not defined.
  line 5   col 13   'require' is not defined.
  line 7   col 13   'require' is not defined.

  ‼  16 warnings

[10:08:32] src\helper\scaffolding.server.js

src\server\publish.js
  line 0   col 0   ES5 option is now set per default
  line 17  col 17  Missing 'new' prefix when invoking a constructor.
  line 17  col 54  Expected an assignment or function call and instead saw an expression.
  line 29  col 21  Missing 'new' prefix when invoking a constructor.
  line 29  col 44  Expected an assignment or function call and instead saw an expression.
  line 3   col 12  'require' is not defined.
  line 4   col 13  'require' is not defined.
  line 7   col 14  'require' is not defined.
  line 9   col 12  'require' is not defined.
  line 10  col 10  'require' is not defined.
  line 11  col 14  'require' is not defined.
  line 12  col 13  'require' is not defined.

  ‼  12 warnings
[10:08:32] gulp-notify: [Error running Gulp] JS hint fail
[10:08:32] src\server\publish.js
[10:08:32] Finished 'build' after 1.61 s