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-eslint

v7.0.0

Published

run ESLint as mocha tests

Downloads

45,036

Readme

mocha-eslint

Travis Build Status Dependency Status NPM version

A simple way to run ESLint in your Mocha tests without a task runner like Grunt or Gulp.

Inspired by mocha-jshint from Allan Ebdrup.

Installation

You can install into your Node.js project as a development dependency with:

npm install --save-dev mocha-eslint

mocha-eslint will install ESLint for itself, so you don't need to worry about adding it to your consuming module.

The same is not true for Mocha. You should already have Mocha installed in your consuming module.

Usage

After mocha-eslint is installed, you can use it by creating a test file for Mocha and requiring mocha-eslint like so:

var lint = require('mocha-eslint');

This will return a function with the signature:

lint(paths, options)

where paths is an array of paths from your project's top level directory (as of v0.1.2, you can also include glob patterns) and options has a single property formatter that can be assigned to the name of any of the ESLint formatters (stylish (the default), compact, checkstyle, jslint-xml, junit and tap) or the full path to a JavaScript file containing a custom formatter. If options is not included, the default "stylish" formatter will be used.

So, a full test file to run in Mocha might look like:

var lint = require('mocha-eslint');

// Array of paths to lint
// Note: a seperate Mocha test will be run for each path and each file which
// matches a glob pattern
var paths = [
  'bin',
  'lib',
  'tests/**/*Test.js',
  '!tests/NotATest.js', // negation also works
];

var options = {
  // Specify style of output
  formatter: 'compact',  // Defaults to `stylish`

  // Only display warnings if a test is failing
  alwaysWarn: false,  // Defaults to `true`, always show warnings

  // Increase the timeout of the test if linting takes to long
  timeout: 5000,  // Defaults to the global mocha `timeout` option

  // Increase the time until a test is marked as slow
  slow: 1000,  // Defaults to the global mocha `slow` option

  // Consider linting warnings as errors and return failure
  strict: true,  // Defaults to `false`, only notify the warnings

  // Specify the mocha context in which to run tests
  contextName: 'eslint',  // Defaults to `eslint`, but can be any string
};

// Run the tests
lint(paths, options);

Notes

This module does not make any decisions about which ESLint rules to run. Make sure your project has a .eslintrc file if you want ESLint to do anything.