-
Notifications
You must be signed in to change notification settings - Fork 3.6k
feat: add support for optional env var replacements in .npmrc #8359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add support for optional env var replacements in .npmrc #8359
Conversation
I know linting checks for this but I also manually validated via https://devina.io/redos-checker |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a great feature! Just a couple nits
@aczekajski any update on this PR? thank you for your work on it |
@alexsch01 I completely forgot about the change suggestions waiting for my action, sorry. Gonna have a look at them soon! Thank you for the reminder ^^ |
Co-authored-by: Michael Smith <[email protected]>
Co-authored-by: Michael Smith <[email protected]>
Co-authored-by: Michael Smith <[email protected]>
@alexsch01 @owlstronaut I commited the suggested changes so I believe the PR is ready for review. |
This solves problem described in #8335 in a backwards-compatible way.
This PR adds possibility to have env var replacements in .npmrc configs written as
${VAR?}
which will cause them to get replaced with an empty string if the variable is not defined. Old behavior where undefined variables are left unreplaced is not changed.References
Fixes #8335