Summary

publishConfig can be defined in package.json & later used when running npm publish. Users may not be aware they have separate config defined for this operation making it confusing to debug or troubleshoot.

Exit Criteria

• npm config list should log the publishConfig configuration if it exists in the cwd package.json (notably, there should be some meaningful distinction to explain & delineate this output similar to how we log user-level config)
• ensure config/values are normalized & private information (ex. basic auth in a registry config) is redacted prior to logging

Example

; "publish" config from package.json
registry = "npm.pkg.github.com"