Gar

```sh npm run snap -w smoke-tests ```

If this is a bug we intend to fix, updating the docs is not the correct approach.

This has been addressed by https://github.com/npm/cli/pull/7334

The package-lock is ignored on published modules. It only comes into use when interacting with the package directly, not as a dependency.

What would we display on npmjs.org for a package?

The readme in the tarball is not a significant source of extra bandwidth to be honest. The readme in the packument is. That's a separate issue and we have internal...

There is now an [implementation PR](https://github.com/npm/cli/pull/6801) up for this.

This has been brought up many times in the past and is essentially a registry feature not a cli feature. There is currently no way to "roll back" an already...

based on conversations at the last round table I think allowing it in the npmrc is exactly what some folks are going to want, so they can opt-into the mode...

Since npm already detects CI would it be a good idea to enable this loglevel in CI automatically?