yarnpkg/yarn

process.env.npm_config_global value does not match npm

Open

#3,526 opened on 2017年5月29日

GitHub で見る
 (2 comments) (1 reaction) (0 assignees)JavaScript (41,514 stars) (2,731 forks)batch import
cat-compatibilityhelp wantedneeds-discussiontriaged

説明

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

What is the current behavior? When installing a package with yarn, it incorrectly sets process.env.npm_config_global.

If the current behavior is a bug, please provide the steps to reproduce. I created a Sample Project with HEAD yielding a failing test case on CI. It fails when alfred-link checks if postinstall is running after being installed globally using process.env.npm_config_global

The project worked before committing the yarn.lock file as seen here

Refs: SamVerschueren/alfred-link#3

What is the expected behavior? Setting process.env.npm_config_global to match npm.

Please mention your node.js, yarn and operating system version.

# OS
❯ sw_vers -productVersion 
10.12.5
❯ node --version
v7.10.0
❯ yarn --version
0.24.6

Please let me know if I can provide any more information. Thanks for building a great tool 😍!

コントリビューターガイド