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

karma-jshint-preprocessor

v0.0.6

Published

A Karma plugin. Check Syntax of JavaScript using JSHint.

Downloads

682

Readme

karma-jshint-preprocessor

Code Climate Dependency Status Build Status

Preprocessor / Plugin for Karma to check JavaScript syntax on the fly.

NPM Package Stats

Installation

The easiest way is to keep karma-jshint-preprocessor as a devDependency in your package.json.

{
  "devDependencies": {
    "karma": "~0.10",
    "karma-jshint-preprocessor": "~0.1"
  }
}

You can simply do it by:

npm install karma-jshint-preprocessor --save-dev

Usage

In your karma.conf.js file, specify the files you want to have lint'ed in the preprocessor section like this.

...
preprocessors: {
  '*.js': ['jshint']
}
...

Optional jshintrc

Read an optional jshintrc property from the karma config to force a .jshintrc file to be used by jshint.

module.exports = function (config) {
  config.set({
    // ...
    jshintPreprocessor: {
      jshintrc: './.jshintrc'
    },
    // ...
  });
};

Thanks to Kl0tl for adding jshintrc path support.

JSHint configuration is read from a JSON formatted .jshintrc file within your project

Cancel build

Cancel the current build if a linting error has occurred. This can be useful on CI servers.

module.exports = function (config) {
  config.set({
    // ...
    jshintPreprocessor: {
      stopOnError: true
    },
    // ...
  });
};
Example .jshintrc file.
{
    "undef": true,
    "globals": {
        "angular": true
    }
}

View the full list of JSHint options.


For more information on Karma see the karma homepage.