fix(config): redact proxy environment credentials#9774
Open
tianrking wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
npm config listdisplays proxy-related environment variablesRoot cause
The environment-variable section rendered values with
JSON.stringifydirectly, bypassing theredacthelper already used by regular config entries.Fixes #9773
Validation
node_modules\\.bin\\tap.cmd --no-coverage test\\lib\\commands\\config.jsnode . run eslint -- lib/commands/config.js test/lib/commands/config.jsgit diff --checknode . run testwas also run. Its unrelated Windows baseline failures are caused by Node v24.14.0 being below this checkout's supported v24.15.0 minimum (extra engine-warning stderr), missingtouch, and the suite's 100% global coverage gate.