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

eslinter

v3.2.1

Published

Simple wrapper around eslint with support for globs and cache, so files that not changed can be skipped, if previous run passed

Downloads

468

Readme

NPM Version Build Status

eslinter

Simple wrapper around eslint with support for globs and cache, so files that not changed can be skipped, if previous run passed

Motivation

Eslint is a nice tool but I wanted to be able to pass globs to validate and use a cache to speed up the validation process.

Features

  • This module add the ability to remember which files were processed. So the next execution will only consider those files that changed. In order to destroy the cache, just execute the command with the option --no-use-cache or --use-cache=false and the cache will be destroyed.
  • This module also accepts globs from the command line. Check the examples below

Install

npm i -g eslinter

Usage

Usage: eslinter [options] glob [glob1] [glob2]..[globN]

Options:
  -i, --cache-id String
      An identifier for the cache file to create. This is only needed if you want to run this task in
      parallel otherwise the next execution might get confusing results for reusing the same cache
      file.
  -f, --format String    the formatter to use to format the output of the tool. If none specified
                         this will use `eslint-friendly-formatter` - default:
                         eslint-friendly-formatter
  -u, --use-cache
      If true, this module will remember the `mtime` and `size` of the linted files that passed
      validation and only operate on the ones that changed. If false, the cache will be destroyed.
      Cache will only be kept between executions with the useCache flag set to true. - default: true
  -h, --help             Show this help
  -v, --version          Outputs the version number
  -q, --quiet            Show only the summary info - default: false
  --colored-output       Use colored output in logs
  -c, --config String
      Path to your `eslint` config, if not provided will try to use the `.eslintrc` file in your
      current working directory, if not found will use the one provided with this package. Check:
      http://eslint.org/docs/user-guide/configuring for more info about the configuration options.

Examples

# validate files, easy way
eslinter src/**/*.js specs/**/*.js

# skip the cache. The next execution without the flag will create a new cache
eslinter --no-use-cache src/**/*.js

# especify a custom formatter
eslinter -f 'stylish' src/**/*.js

# especify a custom formatter from node_modules
eslinter -f 'node_modules/eslint-path-formatter' src/**/*.js

Note

The cache is only kept if the executions of the eslinter command are done without the --no-use-cache or --use-cache=false flags. If any execution include this flag the cache will be destroyed and be created again from scratch the next execution without that flag.

Changelog