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

v3.0.1

Published

export multiple formats of eslint

Downloads

201,155

Readme

eslint-output

npm version Build Status

Getting started

Install eslint-output using npm or your favorite node modules manager.

npm i --save-dev eslint-output

Getting started: Next Steps

  • Configure eslint using .eslintrc
  • Create an npm script in your package json eg. "eslint-output": "eslint-output"
  • Configure eslint-output with .eslintoutputrc placed at the root of your project's directory. See example below
  • Run npm run eslint-output or yarn run eslint-output. See below for command line options.

Example .eslintoutputrc

{
  "files": ["."],
  "formats": [
    {
      "name": "stylish",
      "output": "console"
    },
    {
      "name": "junit",
      "output": "file",
      "path": "tmp/junit.xml",
      "id": "myJunit"
    }
  ],
  "eslintConfig": {}
}
Command line options

| Option | Value | Description | | -------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ | | --quiet, -q | | Don't report warnings, only errors | | --max-warnings, -m | Int | Maximum number of warnings before the process returns an unsuccessful error code | | --format-overrides, -o | String(s) | Override key(s) in specific format array item(s), using format id.key=value.id field must be added to desired format item. |

Files to be checked can also be passed in the command, e.g.

npm run eslint-output src/**/*.js test/**/*.js

This will override the files array in .eslintoutputrc.

Multiple format overrides can be passed in one command, e.g.

npm run eslint-output -o gitlab.path="path/to/file.json" myJunit.output=console -- src/**/*.js

or even

npm run eslint-output -o gitlab.path="path/to/file.json" -q  -o myJunit.output=console -- src/**/*.js

Notes:

  • It is optional to also specify configs for the eslint CLI engine using the eslintConfig property. See https://eslint.org/docs/developer-guide/nodejs-api#eslint-class for the options. However, it is recommended that you use the .eslintrc.
  • File paths are relative to the current working directory.
  • Pull requests are welcome!

Breaking changes

  • Removed explicitly setting envs: ['browser', 'mocha'].