[Bug] yarn global add ignores registry option

[bdwain]

Do you want to request a feature or report a bug?
report a bug

What is the current behavior?
yarn global add internal-pkg --registry "internal-url" ignores the registry option

If the current behavior is a bug, please provide the steps to reproduce.
I can't share my private registry, but I've had it working in projects for a while now just by using a .yarnrc file with registry "internal-url" in it. The same url is ignored if used an option for yarn global add.

What is the expected behavior?
yarn global add should respect the registry option

Please mention your node.js, yarn and operating system version.
node 8.9.0
yarn 1.3.2
OS X Sierra

It seems like the registry option works fine for yarn add. Just not yarn global add.

[guldskog]

@bdwain same issue for me. Any response or solutions?

[bdwain]

not really no. i just manually fix it when this happens

[joeljeske]

@torifat any chance of fixing yarn global to respect the common flags like --registry?

@bdwain what do you mean you "manually fix it"? I can't find a good way to install global packages from my internal registry.

[bdwain]

Oh sorry I mixed this up with another issue. I just use npm install -g

[joeljeske]

Ha! Ok, thanks for the info. Whatever gets the job done.

Yarn maintainers: seems like yarn global add is broken if the way to use it is to use npm instead..

[sodatea]

Workaround:

npm_config_registry=YOUR_NPM_REGISTRY_HERE yarn global add SOME_PACKAGE

[hellojukay]

@sodatea thank you, this works for me.

[Kingwl]

ping 👀