yarnpkg/yarn

process.env.npm_config_global value does not match npm

Open

#3,526 建立於 2017年5月29日

在 GitHub 查看
 (2 留言) (1 反應) (0 負責人)JavaScript (41,514 star) (2,731 fork)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 😍!

貢獻者指南

技術棧
javascriptnodejs
領域
clitooling
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Basic knowledge of Node.js and environment variables
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
45
研究方向
The issue reports that yarn sets `process.env.npm config global` incorrectly. Examine yarn's source code, specifically where environment variables are set during package installation. Compare with npm's behavior. The linked test case in the sample project (https://github.com/nanoxd/yarn bug global flag) and reference to SamVerschueren/alfred link#3 may provide further context. Ensure that the env variable matches npm's value when installing globally.