yarnpkg/yarn

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

Open

#4,581 opened on Sep 28, 2017

View on GitHub
 (5 comments) (25 reactions) (0 assignees)JavaScript (41,514 stars) (2,731 forks)batch import
cat-compatibilityhelp wanted

Description

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.

Contributor guide

Tech stack
javascriptnodejs
Domain
clideveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic understanding of Yarn CLIFamiliarity with npm environment variables
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
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.