Gar

An alternative suggestion is to only do this in CI ```sh $ git diff diff --git a/lib/npm.js b/lib/npm.js index 0bdbcdb9e..f84aa04a9 100644 --- a/lib/npm.js +++ b/lib/npm.js @@ -5,6 +5,7 @@ const...

The very first three things npm logs, fwiw ```sh $ head ~/.npm/_logs/2022-11-21T21_40_51_609Z-debug-0.log 0 verbose cli /Users/wraithgar/.nvm/versions/node/v18.12.0/bin/node /Users/wraithgar/.nvm/versions/node/v18.12.0/bin/npm 1 info using [email protected] 2 info using [email protected] ```

Does this need to be for every command? It can easily be added to anything that installs packages w/o a flag and not be too intrusive imho ```sh $ git...

Isn't this what the `package.json` file is?

npm already stores that information in `package.json`, `package-lock.json` and `node_modules/.package-lock.json`. I don't know if adding it to a fourth location is needed, especially since the files in each `node_modules` subfolder...

Is this functionally any different than including all of your dependencies as bundled and running `npm pack`?

`npm pack` mirrors as exactly as possible building the `tgz` file that gets attached during `npm publish`. If there is a potential for having things `bundled` that are missing, this...

> > Right, but it still depends on the local state of the `node_modules` folder, no? Yep. And if that's a problem, then that's the problem to fix.

`npm view` is the best that npm can do in the absence of a registry having a route to query to get this information with the "name similarity" check baked...

That is a question to ask the npm registry. This RFC repo is for the [cli specifically](https://github.com/npm/rfcs#rfc-process). Once a route exists in any registry, implementing it in the cli would...