npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

gulp-jscodesniffer

v0.0.1

Published

Gulp plugin for jscodesniffer

Readme

gulp-jscodesniffer

Gulp plugin for the jscodesniffer project.

From the jscodesniffer docs:

JSCodeSniffer is a node.js application that checks JavaScript code style consistency according to a provided coding style, just like phpcs. One can define a custom coding style by using described below JSON notation or use one of predefined standards.

npm install gulp-jscodesniffer --save-dev

Options

standard

Optional | Default:EmptyString

A string defining a pre-made jscodesniffer coding standard. As of writing this only two pre-made standards exist, Idiomatic or Jquery. You can read more about them at the jscodesniffer repo.

rc

Optional | Default:EmptyObj

Path to a jscodesniffer JSON configuration file. Without a defined standard this can be used on its own as the only source of rules. When used together with a standard your rc rules will take precedent. Here's our example .jscsrc. Note that if you define neither a standard nor a rc then no style checking will occur.

reporters

Optional | Default:['default']

An array of reporters used to process jscodesniffer output. There are three supplied reporters, which are detailed below. To use a supplied reporter add its name to the reporters array. You can add your own custom reporter by adding it to the array as a function (have a look at the supplied reporters for help).

default

Prints out pleasantly formatted information about failures to the console.

beep

Rings your terminal bell if any failures occurred.

failer

By default this Gulp plugin will not fail its task if it encounters style breaches. Add this reporter to emit an error into the stream and fail the task.

Usage

var gulp = require('gulp');
var jscs = require('gulp-jscodesniffer');

gulp.task('jscs',function () {
    return gulp.src('src/**/*.js')
        .pipe(jscs({
            rc: '.jscsrc',
            standard: 'Idiomatic',
            reporters: ['default','beep']
        }));
});

Tests

Run the Mocha tests:

npm test

Run this project's gulpfile against its fixtures and .jscsrc.

npm run jscs