[Change] Make deprecation notices less scary

npm v10.4.0

What I did

npm install

What I saw

$ npm i
npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
npm WARN deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm WARN deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported

What's happening

The default behavior of npm is to warn about every deprecated packages in the entire installation, regardless of how deep it is inside of the dependency tree. In this case, these packages are used by eslint, and therefore, I personally don't have the ability to make any changes.

And as the maintainer of ESLint, we've been getting inundated with complaints about this even though these packages work fine.

Proposal

I'd like to propose the following changes:

1. npm only shows an explicit deprecation warning for a package when install the package, specifically. So npm install eslint would show a deprecation warning for eslint but if I do npm install in my project that uses eslint, that would not report an explicit deprecation.
2. If I do npm install in my project and any of my direct dependencies are deprecated, output something along the lines of:

16 dependencies are deprecated
  run `npm deprecated` for details

No files, tests, or entry points are named. Start by reproducing the npm install output shown above and trace how npm reports deprecations for transitive and direct dependencies. Done means implementing the proposed warning behavior and summary command, with tests covering explicit installs and project installs.