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

jshint-checkstyle-reporter

v0.0.5

Published

JSHint checkstyle file reporter

Downloads

6

Readme

JSHint checkstyle file reporter

Writes checkstyle output to a file. This can be used to report JSHint results to Jenkins.

Usage

Standard JSHint cli

# optional: specify a different filename, default: checkstyle.xml
export JSHINT_CHECKSTYLE_FILE="jshint.xml"
# run jshint
jshint --reporter node_modules/jshint-checkstyle-reporter *.js subfolder/*.js sub/subfolder.js

As of 08/20/2014 JSHint's --reporter checkstyle reporter always logs everything as level error resulting in <error severity="error" ... /> for every xml entry. I made this tool for that purpose, it translates the given issue code to the actual severity level resulting in proper logging.

Like so:

<error line="227" column="44" severity="error" message="Too many errors. (16% scanned)." source="jshint.E043" />
<error line="42" column="14" severity="warning" message="Missing semicolon." source="jshint.W033" />

This way Jenkins actually registers the different levels (error and warning)

The message codes are up to date as of 08/20/2014