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

eslint-test-generator

v1.0.5

Published

Will create test scripts based on eslint output. Basically developers can't ignore linting if it's integrated into ci

Downloads

56

Readme

eslint-test-generator

Will create test scripts based on eslint output. Basically developers can't ignore linting if it's integrated into ci. eslint-test-generator out of the box currently supports:

  • mocha
  • qunit

But can be easily extended by passing custom handlebars templates.

Usage

NPM

Example

The following is an example of how to use eslint-test-generator with Mocha:

import generator from 'eslint-test-generator';

const output = generator({
  template: 'mocha',
  paths: [
    'src/',
    'test/**/*.js'
  ],
  maxWarnings: 0
});

console.log(output); // generated JS source for tests using mocha

When the above is done src and test directories will be linted by eslint and the output would look something like this:

suite('lint all files', () => {
  test('src/a.js should lint', () => {
    assert.ok(true, 'test/test-src-to-lint/some-warnings.js should pass lint.');
  });

  test('src/b.js should lint', () => {
    assert.ok(false, 'test/test-src-to-lint/some-errors.js should pass lint.\n1:4 - Parsing error: Unexpected token ');
  });
});

API Documentation

The following options can be passed to eslint-test-generator:

  • template - Can be one of three things. A path to a handlebars template file or a handlebars template string or one of the following values:
    • 'mocha'
    • 'qunit'
  • paths - Either a glob String or Array an array of globs. eg:
    • src/
    • ['src/filesToLint/**.js', 'test/'']
    • etc.
  • maxWarnings - Optional (default: -1), equivalent to --max-warnings on eslint's CLI. -1 means there is no maximum.

License

MIT, see LICENSE.md for details.