The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →In Ofri Peretz’s August 12, 2026 measurement, installing eslint-plugin-import resolved 205 packages in an empty npm project. Bare ESLint accounted for 69, leaving 136 additional packages above that baseline. Those are dated, author-reported results—not fixed package counts—and the useful number for your own project is the dependency tree in its lockfile.
What the 205-package figure means
The 205 is the total resolved package count for the measured setup, including ESLint and its dependencies. npm automatically installs peer dependencies in the setup described by Peretz, so this total is not the plugin’s standalone footprint. Subtracting the 69-package bare-ESLint baseline gives the reported incremental count: 136 packages.
As an Amazon Associate I earn from qualifying purchases.
That distinction matters because the number of dependencies listed directly by a package does not show the size of the full resolved tree. Transitive dependencies—packages required by those direct dependencies—contribute to the total. As Peretz puts it, “Direct dependency count does not predict install weight.” Peretz’s article reports the measurements and method.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsHow the measured plugin counts compare
Peretz reports the following package-lock-only resolutions, measured one plugin at a time against a 69-package bare-ESLint baseline. The initial measurements were dated August 12, 2026; the author says a September 4, 2026 rerun returned the same values.
#1 Best Overall
| Plugin | Total resolved packages | Added over ESLint baseline |
|---|---|---|
eslint-plugin-import |
205 | 136 |
eslint-plugin-react |
204 | 135 |
eslint-plugin-jsx-a11y |
194 | 125 |
eslint-plugin-unicorn |
110 | 41 |
eslint-plugin-sonarjs |
83 | 14 |
eslint-plugin-n |
80 | 11 |
eslint-plugin-promise |
70 | 1 |
These counts are reported by the article’s author, not established as an official ESLint statistic or independently reproduced. They describe that measurement procedure and package resolution, not a guaranteed result for every npm version, project, or future date.
Why plugin totals cannot simply be added
Installing multiple plugins together does not necessarily add up to the sum of their separate resolved-tree totals. Their dependency trees can share packages, which npm deduplicates. In Peretz’s combined example with ESLint, eslint-plugin-react, eslint-plugin-jsx-a11y, and eslint-plugin-import, the reported result was 228 packages—not the sum of the individual totals.
Rank #2
For a realistic estimate, measure the package set your project installs together. Standalone plugin counts are useful for comparison, but they do not reveal the combined tree.
How to count the resolved packages in your project
Use a clean directory to compare one plugin with the bare-ESLint baseline. The following procedure uses npm to create lockfiles without downloading package contents:
-
Create an empty directory, move into it, and initialize a project with
npm init -y. -
Resolve the baseline by running
npm install --package-lock-only eslint. Count package entries in the resultingpackage-lock.json. -
In a separate empty directory, initialize another project and run
npm install --package-lock-only eslint eslint-plugin-import. Count the package entries in that lockfile.PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteSpecial offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Subtract the baseline count from the plugin project’s total to estimate the additional resolved packages for that exact setup.
-
To measure your actual configuration, resolve all the packages it uses together and count that lockfile’s package entries. Do not estimate the combined total by adding separate plugin results.
Keep the npm version and package versions consistent when comparing runs, and record the date. Package releases can change the resolution, so Peretz’s September 4 recheck does not establish that the same counts will hold later. The resulting count describes the lockfile resolution, not downloaded bytes, install time, or runtime performance.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
