-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Yarn does not support setting npm_config env via CLI parameter like NPM #4581
Labels
Comments
If you submit a PR, why not? :) |
mc-zone
added a commit
to mc-zone/yarn
that referenced
this issue
Nov 6, 2018
mc-zone
added a commit
to mc-zone/yarn
that referenced
this issue
Nov 6, 2018
6 tasks
Still no progress? |
@jeffminsungkim AFAIK this feature has not been implemented. You are welcome to have a go at it. |
anyone working on this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In NPM's
run-scripts
, user could set custom NPM env (entry withnpm_config
prefix) via CLI parameter:which generate
npm_config_my_custom=true
for the executed script.Verifying it easily, I use
npm run env
with custom parameter:This feature is not present with yarn yet. I am wondering if the core team would consider implementing this feature at all.
The text was updated successfully, but these errors were encountered: