Security News
GitHub Removes Malicious Pull Requests Targeting Open Source Repositories
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
gulp-jshint
Advanced tools
Package | gulp-jshint |
Description | JSHint plugin for gulp |
Node Version | >= 0.4 |
npm install jshint gulp-jshint --save-dev
NOTE: as of 2.0 jshint must be installed with gulp-jshint.
var jshint = require('gulp-jshint');
var gulp = require('gulp');
gulp.task('lint', function() {
return gulp.src('./lib/*.js')
.pipe(jshint())
.pipe(jshint.reporter('YOUR_REPORTER_HERE'));
});
Plugin options:
lookup
true
false
do not lookup .jshintrc
files. See the JSHint docs for more info.linter
Default is "jshint"
Either the name of a module to use for linting the code or a linting function itself. This enables using an alternate (but jshint compatible) linter like "jsxhint"
.
Here's an example of passing in a module name:
gulp.task('lint', function() {
return gulp.src('./lib/*.js')
.pipe(jshint({ linter: 'some-jshint-module' }))
.pipe(...);
});
Here's an example of passing in a linting function:
gulp.task('lint', function() {
return gulp.src('./lib/*.js')
// This is available for modules like jshint-jsx, which
// expose the normal jshint function as JSHINT and the
// jsxhint function as JSXHINT
.pipe(jshint({ linter: require('jshint-jsx').JSXHINT }))
.pipe(...);
});
You can pass in any other options and it passes them straight to JSHint. Look at their README for more info. You can also pass in the location of your jshintrc file as a string and it will load options from it.
For example, to load your configuration from your package.json
exclusively and avoid lookup overhead you can do:
var packageJSON = require('./package');
var jshintConfig = packageJSON.jshintConfig;
jshintConfig.lookup = false;
gulp.src('yo').pipe(jshint(jshintConfig));
Adds the following properties to the file object:
file.jshint.success = true; // or false
file.jshint.errorCount = 0; // number of errors returned by JSHint
file.jshint.results = []; // JSHint errors, see [http://jshint.com/docs/reporters/](http://jshint.com/docs/reporters/)
file.jshint.data = []; // JSHint returns details about implied globals, cyclomatic complexity, etc
file.jshint.opt = {}; // The options you passed to JSHint
You can choose any JSHint reporter when you call
stuff
.pipe(jshint())
.pipe(jshint.reporter('default'))
Let's use jshint-stylish as an example
var stylish = require('jshint-stylish');
stuff
.pipe(jshint())
.pipe(jshint.reporter(stylish))
stuff
.pipe(jshint())
.pipe(jshint.reporter('jshint-stylish'))
JSHint plugins have no good module format so I tried to support all of them I saw in the wild. Hopefully it worked, but if a JSHint plugin isn't working with this library feel free to open an issue.
Do you want the task to fail when a JSHint error happens? gulp-jshint includes a simple utility for this.
This example will log the errors using the stylish reporter, then fail if JSHint was not a success.
stuff
.pipe(jshint())
.pipe(jshint.reporter('jshint-stylish'))
.pipe(jshint.reporter('fail'))
Custom reporters don't interact with this module at all. jshint will add some attributes to the file object and you can add a custom reporter downstream.
var jshint = require('gulp-jshint');
var map = require('map-stream');
var myReporter = map(function (file, cb) {
if (!file.jshint.success) {
console.log('JSHINT fail in '+file.path);
file.jshint.results.forEach(function (err) {
if (err) {
console.log(' '+file.path + ': line ' + err.line + ', col ' + err.character + ', code ' + err.code + ', ' + err.reason);
}
});
}
cb(null, file);
});
gulp.task('lint', function() {
return gulp.src('./lib/*.js')
.pipe(jshint())
.pipe(myReporter);
});
Some reporters have options which, and you can pass them to jshint.reporter()
. Here is an example of using verbose mode with the default JSHint reporter.
gulp.task('lint', function() {
return gulp.src('./lib/*.js')
.pipe(jshint())
.pipe(jshint.reporter('default', { verbose: true }));
});
Tells JSHint to extract JavaScript from HTML files before linting (see JSHint CLI flags). Keep in mind that it doesn't override the file's content after extraction. This is your tool of choice to lint web components!
gulp.task('lintHTML', function() {
return gulp.src('./src/*.html')
// if flag is not defined default value is 'auto'
.pipe(jshint.extract('auto|always|never'))
.pipe(jshint())
.pipe(jshint.reporter('default'));
});
The MIT License (MIT)
Copyright (c) 2015 Spencer Alger
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
JSHint plugin for gulp
The npm package gulp-jshint receives a total of 62,103 weekly downloads. As such, gulp-jshint popularity was classified as popular.
We found that gulp-jshint demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.