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

eslintify

v3.1.0

Published

Stream module for verifying JavaScript programs with ESLint.

Downloads

5,379

Readme

eslintify

Stream module for linting JavaScript programs.



Install

npm install eslintify

The major version number of eslintify is tied to eslint, so if you want to use eslint@3, install eslintify@3.


browserify

browserify your_file.js -t eslintify

"quiet" mode

Functionally equivalent to the ESLint CLI flag --quiet: it causes all warnings to be silently ignored. The default is for warnings to be outputted along with errors.

browserify your_file.js -t [ eslintify --quiet ]

If you only wish to suppress "ignored file" warnings, use the --quiet-ignored flag instead.


"ignored file" warnings

If you choose to exclude files via .eslintignore or elsewhere and the linter is run over them (due to them being in the globbing path), it will produce a warning. eslint@3 introduced a way for these unnecessary warnings to be suppressed; the implementation in this module is as follows:

browserify your_file.js -t [ eslintify --quiet-ignored ]

setting when to break the build

If you wish to get linting reports in the console but not break the build, use the passthrough flag like so:

browserify your_file.js -t [ eslintify --passthrough errors --passthrough warnings ]

You can customize this functionality to only allow errors to break the build (or warnings, if you want!):

browserify your_file.js -t [ eslintify --passthrough warnings ]

"continuous" mode (DEPRECATED)

NOTE: THIS IS DEPRECATED AND WILL BE REMOVED IN eslintify@4. Use the --passthrough flag.

If you wish to get linting reports in the console but not break the build, enable "continuous mode" like so:

browserify your_file.js -t [ eslintify --continuous ]

included files

If you wish to lint files with extensions other than *.js *.jsx *.es6, add extension options. The API mirrors how Browserify handles adding extra extensions:

via CLI

browserify your_file.js -t [ eslintify --extension html --extension haml ]

via JS

.transform({extensions: ['html', 'haml']}, eslintify)

other result formatters

Starting with eslintify 2.0, the default formatter is royriojas/eslint-friendly-formatter. You can opt to switch it out for your own choice by providing one of the eslint official formatter names or a path to a requireable node module.

via CLI

browserify your_file.js -t [ eslintify --formatter json ]

via JS

.transform({formatter: 'json'}, eslintify)

custom formatter via CLI

browserify your_file.js -t [ eslintify --formatter ./node_modules/eslint-path-formatter ]

custom formatter via JS

.transform({formatter: './node_modules/eslint-path-formatter'}, eslintify)