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 🙏

© 2024 – Pkg Stats / Ryan Hefner

jscs-json-reporter

v1.0.1

Published

Saves JSCS results to a JSON file

Downloads

3

Readme

jscs-json-reporter npmVersion

Build Status Dependencies DevDependencies npm

A JSON reporter for node-jscs and grunt-jscs.

Getting started

Install using npm:

npm install jscs-json-reporter --save-dev

Usage

When using with node-jscs

Set the path to jscs-json-reporter. Command line example:

jscs app.js --reporter node_modules/jscs-json-reporter/jscs-json-reporter.js

Report will be written to jscs-report.json in current working directory.

When using with grunt-jscs

Configure jscs in Gruntfile.js so that reporter points to jscs-json-reporter.js and reporterOutput points to some JSON file.

jscs: {
    src: [
    	'path/to/files/*.js',
    	'another/path/to/files/**/*.js'
    ],
    options: {
    	maxErrors: null,
        reporter: require('jscs-json-reporter').path,
        reporterOutput: path.resolve('/path/to/jscs-report.json')
    }
}

Example

alt text

"explainedError" key contains a preformatted string with detailed error info.

When used inside HTML <pre></pre> tags it is displayed like this: alt text

Important!

Generated JSON file size might be very large depending on the number of errors. For instance, a file containing 4500 errors is around 2.85 MB.

License

Licensed under the MIT license. Copyright (c) 2015 Audrius Jakumavicius