Description

Change the title README > Verbosity to "npm loglevel", since the verbosity only applies to npm, not to Docker or to Node.js. "loglevel" is also a more easily recognizable term.

Remove the description of loglevel change from Oct 2017. Leave the descriptions of how to set the npm loglevel.

Use the same loglevel (info) in each of the examples.

Use node:lts as example image (node with no tag selects the less stable Current Node.js version).

Motivation and Context

The README > Verbosity describes a historical decision in Oct 2017 to revert to using the default npm log level, instead of overriding with the higher loglevel info.

The reasons for the decision no longer need to be explained and can be removed for a clearer description of how to use the npm loglevel.

The default npm loglevel is notice which includes also the levels warn and error. This has been the default loglevel going back also to the time when the decision was made not to override the default.

Testing Details

cd $(mktemp -d)
cat > Dockerfile <<EOT
FROM node:lts
ENV NPM_CONFIG_LOGLEVEL=info
RUN npm --version
EOT
docker build --progress plain -t test . --no-cache

docker run -e NPM_CONFIG_LOGLEVEL=info node:lts npm --version

docker run node:lts npm --loglevel=info --version

shows the following, or similar, output:

npm info using npm@11.13.0
npm info using node@v24.16.0
11.13.0
npm info ok

Types of changes

• Documentation
• Version change (Update, remove or add more Node.js versions)
• Variant change (Update, remove or add more variants, or versions of variants)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Other (none of the above)

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING.md document.
• All new and existing tests passed.