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-file-progress

v3.0.1

Published

Eslint plugin to print file progress

Downloads

420,655

Readme

eslint-plugin-file-progress

Version Version Tests

Eslint plugin to print file progress

Getting Started

Installation

npm i -D eslint-plugin-file-progress
# or
yarn add --dev eslint-plugin-file-progress

Usage

// eslint.config.js

{
  name: 'progress',
  plugins: {
    progress
  },
  rules: {
    "progress/activate": 1
  },
  settings: {
    progress: {
      hide: false, // use this to hide the progress message, can be useful in CI
      hideFileName: false, // use this to hide the file name, would simply show "Linting..."
      successMessage: "Lint done..."
    }
  }
}

Or use the recommended config

// eslint.config.js
import progress from 'eslint-plugin-file-progress'

export default [
  progress.configs.recommended
]

or if you want to hide the progress message in CI

// eslint.config.js
import progress from 'eslint-plugin-file-progress'

export default [
  progress.configs['recommended-ci']
]

This configuration is similar to the recommended one, but it automatically detects CI environments by checking if the CI environment variable is set to true, and hides the progress message accordingly.

For CI's where CI is not set to true, you can use the settings.progress.hide option to hide the progress message.

Demo

Who likes a silent console ¯\_(ツ)_/¯

Progress

Only on CLI

Some eslint plugins for code editors may conflict with this plugin rule (or, in that context, a file progress is not relevant)

npx eslint . --plugin file-progress --rule 'file-progress/activate: 1'

Or, in your package.json's command:

{
  "scripts: [
-    "lint": "eslint ."
+    "lint": "eslint . --plugin file-progress --rule \"file-progress/activate: 1\""
  ]
}

Use file-progress/activate: 0 to disable the plugin. See https://eslint.org/docs/latest/user-guide/command-line-interface#specifying-rules-and-plugins for more details on how to use CLI