eslint-plugin-file-progress
Advanced tools
Eslint plugin to print file progress
npm i -D eslint-plugin-file-progress
# or
yarn add --dev eslint-plugin-file-progress
// eslint.config.js
{
name: 'progress',
plugins: {
progress
},
rules: {
"progress/activate": 1
},
settings: {
progress: {
hide: false,
successMessage: "Lint done..."
}
}
}
Who likes a silent console ¯\_(ツ)_/¯
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
FAQs
Eslint plugin to print file progress
We found that eslint-plugin-file-progress demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.