eslint-plugin-ignoreuglify
exclude uglified files from ESLint's linting
ESLint Ignore Uglify Plugin
This plugin automatically skips checking files that have been minified (compressed and obfuscated code). When you run ESLint to check your code for style and quality issues, this plugin quietly removes minified files from the queue, so you don't waste time linting code that's meant to be unreadable anyway.
The way it works is straightforward: the plugin looks at each file and checks if any single line is longer than 500 characters. If it finds one, it assumes the file has been minified and tells ESLint to ignore it. This is a simple heuristic—minified code tends to have extremely long lines because all the whitespace and line breaks have been removed—but it gets the job done for most cases.
You'd use this if you have a project where minified files sometimes end up in your source directory. For example, maybe you're distributing a library with pre-built, minified versions alongside your source code, or you accidentally committed a bundled file. Without this plugin, ESLint would complain about all the weird variable names and formatting in those minified files, filling your linting reports with noise. This plugin prevents that by filtering them out before ESLint even looks at them.
Setting it up takes just two steps: install the plugin alongside ESLint, then add it to your ESLint configuration file. After that, it runs automatically. The README notes that this is a pretty basic version—the 500-character-per-line rule is intentionally simple—so if you need more sophisticated detection, you might need to adjust or fork it. But for most projects that just want to avoid linting minified code, it's a quick and lightweight solution.