Skip to content
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

Open
runlevel5 opened this issue Sep 28, 2017 · 5 comments · May be fixed by #6644
Open

Yarn does not support setting npm_config env via CLI parameter like NPM #4581

runlevel5 opened this issue Sep 28, 2017 · 5 comments · May be fixed by #6644

Comments

@runlevel5
Copy link

runlevel5 commented Sep 28, 2017

In NPM's run-scripts, user could set custom NPM env (entry with npm_config prefix) via CLI parameter:

npm run <name> --my_custom

which generate npm_config_my_custom=true for the executed script.

Verifying it easily, I use npm run env with custom parameter:

npm run env --report | grep "my_custom"

This feature is not present with yarn yet. I am wondering if the core team would consider implementing this feature at all.

@BYK
Copy link
Member

BYK commented Sep 29, 2017

If you submit a PR, why not? :)

@shellscape
Copy link

It's kind of bananas that after 4+ years Yarn still doesn't have compatibility for this. #6644 has been open for over 3 years without review to resolve this. @BYK the request was made for a PR and one has been linked to this. Let's get this super old compat bug fixed up.

@jeffminsungkim
Copy link

Still no progress?

@runlevel5
Copy link
Author

@jeffminsungkim AFAIK this feature has not been implemented. You are welcome to have a go at it.

@plu-briteris-rl
Copy link

anyone working on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants