You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.jsonregistry = "npm.pkg.github.com"
The text was updated successfully, but these errors were encountered:
Closes: npm/statusboard#417
If the file at `$NPM_CONFIG_Prefix/package.json` contains a
`publishConfig`, the key/value pairs will be printed along with the rest
of the output from `npm config ls`.
Closes: npm/statusboard#417
If the file at `$NPM_CONFIG_PREFIX/package.json` contains a
`publishConfig`, the key/value pairs will be printed along with the rest
of the output from `npm config ls`.
Summary
publishConfig
can be defined inpackage.json
& later used when runningnpm 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 thepublishConfig
configuration if it exists in the cwdpackage.json
(notably, there should be some meaningful distinction to explain & delineate this output similar to how we log user-level config)Example
The text was updated successfully, but these errors were encountered: