This repository was archived by the owner on Aug 11, 2022. It is now read-only.
Do replace environment in config files (like .npmrc) even for keys #18426
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.
Current .npmrc will keep keys with not replaced Environment variables. However values are replaced. So it may confuse somebody & has no option to solve this problem
.npmrc example
With env.vars:
NOW it will produce bellow options:
But expected options are:
Probably it is expected state & it would be very helpful when it will be merged for private registries which are using CI for publishing npm packages. For example: Then no more "
npm login | answer_input $AUTH_TOKEN ... # etc. constructions
" are necessary.