yarnpkg/yarn

What is the equivalent to npm's NPM_CONFIG_REGISTRY environment variable?

Open

#2,091 opened on Nov 30, 2016

View on GitHub
 (6 comments) (13 reactions) (0 assignees)JavaScript (41,514 stars) (2,731 forks)batch import
cat-compatibilitycat-featuregood first issuehelp wantedtriaged

Description

My company's project currently makes use of private node modules stored in gemfury. In order to successfully fetch the private modules, we make use of npm's NPM_CONFIG_REGISTRY environment variable. We're trying to switch over to using yarn (v0.17.9) but it appears that yarn does not recognize NPM_CONFIG_REGISTRY. I went through the yarn source code to try and find some equivalent to NPM_CONFIG_REGISTRY, but, from my initial look, nothing stands out. Does yarn have such an equivalent environment variable?

Contributor guide

Tech stack
javascriptnodejs
Domain
developer experiencetooling
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.
half day
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.
clear
Prerequisites
Basic knowledge of YarnUnderstanding of environment variablesFamiliarity with npm configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
This issue requests an environment variable equivalent to npm's NPM CONFIG REGISTRY. A contributor should examine the yarn source code (particularly the configuration module) to see how environment variables are currently handled. They should search for existing references to registry configuration and possibly add a new environment variable like YARN CONFIG REGISTRY. Note that the yarn 1.x repository is frozen; feature development now happens on yarnpkg/berry, so the fix should target that repository.