Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
In Ofri Peretz’s npm resolution measurement, installing eslint-plugin-import alongside ESLint produced a lockfile with 205 package entries: 69 for the ESLint baseline and 136 more in the plugin’s resolved dependency tree. Those are author-reported results from a particular setup, not fixed package counts; the useful way to assess your own project is to inspect its lockfile and compare the combined dependency set you actually install.
What the 205-package count means
Peretz measured an empty project using npm install --package-lock-only. In that setup, npm resolved ESLint and its peer dependencies along with eslint-plugin-import. The reported 205 is the resulting package total, not 205 packages belonging exclusively to the plugin. Subtracting the author’s 69-package bare-ESLint baseline gives an incremental difference of 136.
These are counts of resolved package entries, including transitive dependencies, rather than a count of direct dependencies listed in a project’s manifest. As Peretz puts it, “Direct dependency count does not predict install weight.”
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 minuteThe author dates the original measurements to August 12, 2026, and reports that a September 4, 2026 recheck returned the same values. The figures are not an official ESLint statistic or an independent reproduction, and they should not be treated as universal across npm versions, lockfile states, or later package releases. Peretz’s article describes the measurement.
#1 Best Overall
How the reported plugin counts compare
For each plugin below, the total includes the 69-package ESLint baseline in Peretz’s reported setup. “Added” is the author’s difference over that baseline.
| Plugin | Resolved total | 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 |
All figures in the table are Ofri Peretz’s 2026 package-lock-only measurements, initially taken August 12 and reportedly unchanged on September 4. They compare individual plugin resolutions against the same bare-ESLint baseline; they are not guaranteed current counts.
Rank #2
Why plugin totals do not add up in a real project
Installing several plugins does not usually produce the sum of their separate resolved totals. Dependency trees can share packages, and npm can deduplicate those shared dependencies in the combined installation. In Peretz’s example with ESLint plus eslint-plugin-react, eslint-plugin-jsx-a11y, and eslint-plugin-import, the reported combined result was 228 packages—not the sum of the individual totals.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
That combined number is also specific to the author’s package set and resolution. To understand your project’s size, measure the packages resolved together for your actual configuration rather than adding separate plugin counts.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to count your project’s resolved packages
- Create a clean test project. Start with an empty directory and initialize an npm project so unrelated dependencies do not affect the result.
- Resolve the package set you want to measure. Use
npm install --package-lock-onlywith the same ESLint and plugin package names you intend to evaluate. For a baseline comparison, first resolve ESLint alone, then resolve ESLint with the plugin or plugins. - Count package entries in
package-lock.json. Compare the lockfile entry totals for the baseline and plugin setup. The difference is an incremental comparison for that particular resolution, not a universal plugin property. - Measure plugins together as well. Resolve the complete set used by your project and count that resulting lockfile. This captures overlap and deduplication that separate measurements miss.
- Repeat in the project’s real environment. Package releases and project conditions can change the resolved tree. Use the project’s own npm setup and lockfile when deciding what its installation includes.
The command shown is the procedure reported by Peretz; the resulting counts can change over time. Record when and where you ran the comparison, including the package set and npm environment, so the number has a clear scope.
Quick Recap
Rank #4
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.
