yarnpkg/yarn

Yarn --production tries to resolve devDeps as well

Open

#3,630 建立於 2017年6月13日

在 GitHub 查看
 (55 留言) (48 反應) (0 負責人)JavaScript (41,514 star) (2,731 fork)batch import
cat-featurehelp wantedneeds-discussiontriaged

描述

Do you want to request a feature or report a bug? This is a bug, or unexpected behaviour.

What is the current behavior?

  1. Have a package.json which have devDependencies and one of them are private
  2. Run yarn --production
  3. Yarn tries to resolve all packages and fails, because have no access to private packages

To fix that I need additional workaround with authToken (the problem arises in docker build process).

What is the expected behavior? Yarn should only resolve production packages when --production flag exposed.

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

node -v
v8.1.0
yarn --version
0.24.6

貢獻者指南

技術棧
javascriptnodejs
領域
clibuild system
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic Yarn CLI usageUnderstanding of devDependencies vs dependencies
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
15
研究方向
Review the yarn 1.x codebase, specifically the resolver module that handles production flag (likely in src/resolvers/). Examine the logic that resolves dependencies and ensure devDependencies are skipped when production is set. Check the comments in the issue for any proposed fixes or workarounds. Note that the yarn 1.x repository is frozen; the fix may need to be ported to the berry (yarn 2.x) repository at https://github.com/yarnpkg/berry.