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

mocha-jsxhint

v0.0.10

Published

run JSXHint as mocha tests (forked from mocha-jshint)

Downloads

4

Readme

mocha-jshint

Run jshint as Mocha tests.

To install in your node.js project as devDependency, run this command, in the root of your project

npm install mocha-jshint --save-dev

usage

Mocha defaults to looking for your test specs in the test folder of your project. Add this file as test/jshint.spec.js in your project, with the following content:

require('mocha-jshint')();

That is it you are done.

To grep only the jshint test, just do

mocha --grep jshint

configuring jshint

In the root of your project you can add a .jshintignore file, where each line is a file or directory for jshint to ignore and not check for errors. (see this project for an example)

At the root of your project you can add a .jshintrc file, that specifies what options you want jshint to run with (see this project for an example)

You can also add a .jshintrc file to any subdirectory of your project, to override the .jshintrc settings in the root. For example in this project I allow some global variables in the test folder. Global variables that are set when I run mocha tests. Global variables that are only allowed to be used, in the .js files in the test folder

Why?

This module was created to:

  • Make adding jshint testing to a project using Mocha as easy as possible
  • Make it easy to piggyback on all the different Mocha reporters (dot, spec, teamcity etc) for jshint output
  • Make sure that you get a click-able link directly to the problem in WebStorm, when jshint fails
  • Make sure that there is no unnecessary noise in the test output