Yarn does not support setting npm_config env via CLI parameter like NPM · yarnpkg/yarn#4581

(5 评论) (25 反应) (0 负责人)JavaScript (41,514 star) (2,731 fork)batch import

cat-compatibilityhelp wanted

描述

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.

技术栈: javascriptnodejs
领域: clideveloper experience
议题类型: feature
难度: 3
预计时间: 3-5 days
活动状态: stale
清晰度: mostly clear
前置要求: Basic understanding of Yarn CLIFamiliarity with npm environment variables
新手友好度: 30
研究方向: The issue requests adding support for passing custom npm config environment variables via CLI parameters in Yarn, similar to npm's `npm run <name> my custom` which sets `npm config my custom=true`. Note that the 1.x line of Yarn is frozen, and development has moved to Yarn Berry (https://github.com/yarnpkg/berry). A contributor should first check if this feature already exists in Yarn Berry or has been discussed there. If not, they could propose the feature there, referencing this issue. The implementation would involve parsing CLI arguments with a custom prefix and setting corresponding environment variables for the script execution. Key files to examine would be the CLI argument parser and the script runner in the Yarn codebase.