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-plugin-log-filenames

v1.0.6

Published

ESLint plugin for logging the paths of all files being linted to the console

Downloads

8,531

Readme

eslint-plugin-log-filenames Build Status NPM Version

ESLint plugin for logging the paths of all linted files to the console

Why?

ESLint doesn't provide a summary of which or how many files have been linted. Thus, misconfiguration can easily lead to a falsely "clean" linting results just because not all intended files got checked.

By adding this plugin to an ESLint config, a list of all linted files will be output, regardless of actual linting errors.

How?

Add the plugin to your project

$ npm install --save eslint-plugin-log-filenames

Then include it in your ESLint configuration (e.g .eslintrc)

{
  "plugins": [
    "log-filenames"
  ],
  ...
}

or via CLI

eslint --plugin log-filenames

Logged file types are *.{js,jsx,es,es6,cjs,mjs,jsm,ts,tsx,html,vue}.
If you need more exotic extensions, simply add an overrides section to your .eslintrc, making the plugin log every file regardless of its extension:

{
  "plugins": [
    "log-filenames"
  ],
  "overrides": [
    {
      "files": "*.*",
      "processor": "log-filenames/.js"
    }
  ],
  ...
}

Important

If ESLint is run with the --format=checkstyle CLI option (as IntelliJ's ESLint integration does), logging filenames is skipped in order to not produce invalid checkstyle XML in the console.